josh
15
Okay, we think there’s a very high likelihood the problem is due to a deploy from 1:08 pm today. We’re reverting that deploy now, and expect it to be live in about ~7 minutes. We haven’t been able to reproduce the bug on our end yet, so I’d appreciate: a) confirmation that the reverting the code fixed it once it goes live (I’ll post again when it does), and b) any details you can send us (to support@bubble.io if it involves an app you don’t want to post on the forum) to help us reproduce so that we can identify the problem and re-deploy the offending code with the issue fixed
1 Like