I’m curious if other people are having regular and consistent issues with viewing sourcebooks on mobile browsers. On Safari this is generally in the form of “a problem has repeatedly occurred” error while scrolling (and sometimes just sitting there). Before you ask, I’ve done ALL of the things (clear cache etc etc etc). I’ve also installed other browsers and immediately run into the same or similar issues. Turning off JavaScript immediately solves the problem. But without it, there’s a lot u can’t do. I have opened a ticket to little effect . Thoughts? Anyone else? Works fine on PC browser.
Posting for extra visibility. It sure would be nice if anyone from dndbeyond would respond to these posts with an update, these issues seem endemic to those using mobile browsers
Based on the behavior, I feel like it’s some sort of CSS-related problem. In my more conspiracy minded moments, I feel like they’re trying to push me to their app. The trouble shooting steps ask you to install it and report some sort of info from it.
I’m curious if other people are having regular and consistent issues with viewing sourcebooks on mobile browsers. On Safari this is generally in the form of “a problem has repeatedly occurred” error while scrolling (and sometimes just sitting there). Before you ask, I’ve done ALL of the things (clear cache etc etc etc). I’ve also installed other browsers and immediately run into the same or similar issues. Turning off JavaScript immediately solves the problem. But without it, there’s a lot u can’t do. I have opened a ticket to little effect . Thoughts? Anyone else? Works fine on PC browser.
Bump for visibility. I don’t think I’m the only one if the support team has customized troubleshooting instructions
Same issue that has made viewing sourcebooks impossible on mobile. Worked fine until a few months.
Posting for extra visibility. It sure would be nice if anyone from dndbeyond would respond to these posts with an update, these issues seem endemic to those using mobile browsers
When I saw “Cajun Robinhood” I immediately pictured the Mamou Mardi Gras riders. Probably not what you were going for, but man it works!
Yeah this issue started showing up mid-December and there are several posts about it but no acknowledgement from the dev team
Based on the behavior, I feel like it’s some sort of CSS-related problem. In my more conspiracy minded moments, I feel like they’re trying to push me to their app. The trouble shooting steps ask you to install it and report some sort of info from it.
I looked at it on desktop and react.js is throwing errors so it's the more likely culprit.
This is why I’m not a web dev. Thanks for the info
This finally appears to be resolved
For the moment. We’ll see if it holds. Thanks for the heads up