Adding to the thread in that I have this problem as well. Does anyone know if dndbeyond is looking into it at all? I imagine that if this is happening for all safari users, it would hamper the use of this site substantially.
Greetings all. Yesterday I had created a new thread on this topic without properly searching for an existing thread. Posting to follow potential updates here.
Note to Product/Development persons monitoring these threads, I respectfully ask that some consideration be given to notifying subscribers that problems with the production platform at least be acknowledged. It would just feel better to know that someone is looking into this.
A mod did say it was reported over to the dev team on one of the many threads this issue's been reported. That said, I think it would behoove D&D Beyond when bugs like this, where a significant number of users (Safari users) are experience a "blackout"), hit to give some sort of update, ideally a pinned topic till resolved, that not only dev has notice but it's being worked on. Heck my electric utility is more diligent in providing info during blackouts, and they're notorious for their opaqueness. From past experience I'm aware the dev team are diligent, but I'm seeing a lot of "post counts: 1s" so you're talking about members who don't usually engage on the forums and have yet to be exposed to "competent but quiet" dev ops.
Since this bug hit (and for me it happened literally moments after I manually accepted a Safari update) I haven't obviously been able to use D&D Beyond outside this forum. Ironically, this morning I then get a "why haven't you been using D&D Beyond?" survey in my email this morning. I think it was just a random coincidence, or this bug even has DDB aware of it through its usage metrics.
Rollback Post to RevisionRollBack
Jander Sunstar is the thinking person's Drizzt, fight me.
A mod did say it was reported over to the dev team on one of the many threads this issue's been reported. That said, I think it would behoove D&D Beyond when bugs like this, where a significant number of users (Safari users) are experience a "blackout"), hit to give some sort of update, ideally a pinned topic till resolved, that not only dev has notice but it's being worked on. Heck my electric utility is more diligent in providing info during blackouts, and they're notorious for their opaqueness. From past experience I'm aware the dev team are diligent, but I'm seeing a lot of "post counts: 1s" so you're talking about members who don't usually engage on the forums and have yet to be exposed to "competent but quiet" dev ops.
Since this bug hit (and for me it happened literally moments after I manually accepted a Safari update) I haven't obviously been able to use D&D Beyond outside this forum. Ironically, this morning I then get a "why haven't you been using D&D Beyond?" survey in my email this morning. I think it was just a random coincidence, or this bug even has DDB aware of it through its usage metrics.
I don't use Safari and am not affected by this bug and I'm on DDB nearly every day, and I got that email survey ("The heck?" I said when I saw it.)
As for not hearing from the devs, this happened right after the weekend started. It seems to be an issue with how a particular browser processes the site so not a simple "outage" in access to web code files and assets (which a non-dev staff member might be able to fix or at least verify), meaning the devs themselves will need to figure out what changed in how Safari works. They should be on it for certain tomorrow; at least they'd better be.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
A mod did say it was reported over to the dev team on one of the many threads this issue's been reported. That said, I think it would behoove D&D Beyond when bugs like this, where a significant number of users (Safari users) are experience a "blackout"), hit to give some sort of update, ideally a pinned topic till resolved, that not only dev has notice but it's being worked on. Heck my electric utility is more diligent in providing info during blackouts, and they're notorious for their opaqueness. From past experience I'm aware the dev team are diligent, but I'm seeing a lot of "post counts: 1s" so you're talking about members who don't usually engage on the forums and have yet to be exposed to "competent but quiet" dev ops.
Since this bug hit (and for me it happened literally moments after I manually accepted a Safari update) I haven't obviously been able to use D&D Beyond outside this forum. Ironically, this morning I then get a "why haven't you been using D&D Beyond?" survey in my email this morning. I think it was just a random coincidence, or this bug even has DDB aware of it through its usage metrics.
I don't use Safari and am not affected by this bug and I'm on DDB nearly every day, and I got that email survey ("The heck?" I said when I saw it.)
As for not hearing from the devs, this happened right after the weekend started. It seems to be an issue with how a particular browser processes the site so not a simple "outage" in access to web code files and assets (which a non-dev staff member might be able to fix or at least verify), meaning the devs themselves will need to figure out what changed in how Safari works. They should be on it for certain tomorrow; at least they'd better be.
It’s not a change in how Safari works, Safari 15 was working just fine up until a couple of days ago. Something has changed at DDB, I haven’t updated Safari 15 since it was released.
I don't know that the issue was caused by the Safari updated to version 15.0. That update was on September 20, and I did not start having the problem until October 1. And looking at the dates posts were added here, it looks like we all started having the problem about the same time.
Firefox is ignoring the same 403 errors on those files, then there are some webgl errors and things but the character page works (slowly but that's my laptop I think).
Until I try to do a die roll then the page becomes unresponsive. I've not tried these with Firefox before so there might not be a link.
Adding to the thread in that I have this problem as well. Does anyone know if dndbeyond is looking into it at all? I imagine that if this is happening for all safari users, it would hamper the use of this site substantially.
I can use Chrome but not Safari on MacOS 11.6
Also having this issue after the mac os update!
Greetings all. Yesterday I had created a new thread on this topic without properly searching for an existing thread. Posting to follow potential updates here.
Note to Product/Development persons monitoring these threads, I respectfully ask that some consideration be given to notifying subscribers that problems with the production platform at least be acknowledged. It would just feel better to know that someone is looking into this.
Thank you all.
Same here. Works on Chrome, not on Safari. multiple reload attempts, and then fail.
A mod did say it was reported over to the dev team on one of the many threads this issue's been reported. That said, I think it would behoove D&D Beyond when bugs like this, where a significant number of users (Safari users) are experience a "blackout"), hit to give some sort of update, ideally a pinned topic till resolved, that not only dev has notice but it's being worked on. Heck my electric utility is more diligent in providing info during blackouts, and they're notorious for their opaqueness. From past experience I'm aware the dev team are diligent, but I'm seeing a lot of "post counts: 1s" so you're talking about members who don't usually engage on the forums and have yet to be exposed to "competent but quiet" dev ops.
Since this bug hit (and for me it happened literally moments after I manually accepted a Safari update) I haven't obviously been able to use D&D Beyond outside this forum. Ironically, this morning I then get a "why haven't you been using D&D Beyond?" survey in my email this morning. I think it was just a random coincidence, or this bug even has DDB aware of it through its usage metrics.
Jander Sunstar is the thinking person's Drizzt, fight me.
I don't use Safari and am not affected by this bug and I'm on DDB nearly every day, and I got that email survey ("The heck?" I said when I saw it.)
As for not hearing from the devs, this happened right after the weekend started. It seems to be an issue with how a particular browser processes the site so not a simple "outage" in access to web code files and assets (which a non-dev staff member might be able to fix or at least verify), meaning the devs themselves will need to figure out what changed in how Safari works. They should be on it for certain tomorrow; at least they'd better be.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
The issue with the site exists in Chrome too, chrome is just ignoring the errors because it natively has a higher threshold for errors by default.
It’s not a change in how Safari works, Safari 15 was working just fine up until a couple of days ago. Something has changed at DDB, I haven’t updated Safari 15 since it was released.
Same here. Anyone got update ?
I tried the Safari 15.1 developer preview and it didn't help. So I'm stuck unable to use the character sheets at all until this is fixed.
chrome is the only one working for me currently
+1
+1
+1
I don't know that the issue was caused by the Safari updated to version 15.0. That update was on September 20, and I did not start having the problem until October 1. And looking at the dates posts were added here, it looks like we all started having the problem about the same time.
I first noticed Sat Oct 2. About 9pm eastern. I have no problems on my mobile using safari, just my desktop..,
It seems to be fixed now guys
I can't use safari.
Firefox is ignoring the same 403 errors on those files, then there are some webgl errors and things but the character page works (slowly but that's my laptop I think).
Until I try to do a die roll then the page becomes unresponsive. I've not tried these with Firefox before so there might not be a link.
According to a DDB staff post, this issue is resolved. And my one test, not statistically valid I know, shows this to be true.