Every time i press edit overlay it says aw snap something went wrong
When I try to change the content thing it says something went wrong and asks me to refresh browser or clear the cache. i have done that but nothing changes.
19 Replies
@SigmaSlayer56 what's your Twitch username?
Twitch Buba69x
I was making an overlay and when I went to delete a content item it said something went wrong and that I have to clear my cache or reload site, I did that and nothing changes, pls help
For the “overlay not found” issue, please make sure you’re signed in before editing your overlay.
The content item bug is common with IE/Edge browsers. Does it still happen with Chrome? Do you remember which content item type you tried deleting?
I have made sure that I am signed in when I’m creating/editing an overlay, and yes it still happens with chrome
It happens when I edit a layer and then I go to delete a text group e.g. recent followers or recent subs
When I press delete that first picture that I sent you shows up
👀
What does that mean
It means I'm looking into it 😅
My bad
@SigmaSlayer56 Deleting texts groups is working for me
For you is it happening with a specific overlay or layer?
Also, which browser are you using?
I could send a video (btw slow mode is making it take ages to send the message). Also now every time I go into an overlay that I have previously edited, it always shows the aw snap message. I am also using chrome as my browser. Also it is not with any specific layer, it happens to every layer.
Ah sorry, I reduced the slow mode to 5 seconds
It lost access to your Twitch so, please sign out and sign back in with Twitch.
It seems to be signing me out all of the time for some reason
Hmm your account seems to be working for me
Ah OK I see the error now
Slow mode is still 5 mins i think. That’s good that you found it, are you looking into it now?
Yeah I'm not sure what's going on. I set it to 5 seconds, but Discord hasn't updated it yet 🤷
Ah I have to set the slow mode per post 🤦
This issue should be resolved within the hour
@SigmaSlayer56 The issue is resolved for me. Can you refresh and confirm?
I can confirm it is fixed