Any updates here?
Kind of the same situation here – I’m receiving more and more user complaints about this issue.
Updates on the solution and a clear timeframe would be greatly appreciated to help us manage the crisis on the user side.
Hi @fede.bubble,
Thank you for your reply.
We’ve received confirmation from Roody, Bubble team that they replicated the issue on their end and escalated it to the engineering team for further investigation (15 hours ago).
Do you have any updates on this?
Please let us know as soon as possible. 
Here’s a bit more context about the issue occurring with apps converted using the Air Native service (in the web view) – both iOS and Android apps are currently not functioning.
We’ve encountered an issue related to the code on Bubble’s platform. It seems that Bubble is blocking our old userAgent, which should still be working. This blockage is causing an error that impacts the page load within the webview.
This issue has been identified as the root cause of the problem users are experiencing, and we kindly request that this be addressed to restore proper functionality.
We appreciate your attention to this matter and look forward to your assistance in resolving it.
Here are the screenshots with errors related to old browsers:
Looking forward to your reply.
Regards,
Any update?
@fede.bubble this is now beyond a joke. If this was your application hosted by a 3rd party you would be seeking compensation from them after 24 hours of downtime. We are now well beyond 24 hours and the fact that we have had about 2 very generic communications from bubble is simply unacceptable.
You know the issue was caused by an update, so rollback the update to a previous version and then fix the issue before republishing your update??
I have been told from our very helpful team @ZeroqodeSupport that as a result of your issue the only workaround is to rebuild and republish everyone’s apps. This will mean days of waiting while they do the work and then however long before App stores publish the new apps. All of this downtime hurts our products SIGNIFICANTLY and the easy fix is to rollback your changes so that we don’t have to rebuild our apps.
It would also go a very long way to helping our confidence if you can move away from the generic response and tell us what is going on, what you are doing to fix this and more importantly…..how long it is expected to take.
Can you imagine what your business would do if your Bubble platform went down for a number of days??
Please just communicate!
I had to create a Progressier version of my app and ask all the users to install it instead of the official one. Not a great image for my company. Since this is just another failure of Bubble this week, some of my clients are walking away. For others I gave a refund.
It’s crazy that Bubble - besides not having automated tests before deploy - did not simply roll back to the previous version after 5 minutes from acknowledging the problem (it’s enough to open the browser’s console to any Bubble app to see that it’s throwing a 400 error, not something that requires 2 days of work of a 100m$ funded company).
The cherry on top is the insufficient communication and the green status page.
My customers are complaining about this, and some have even canceled their payments. Please resolve this quickly.
We’re all between a rock and a hard place here.
Please help with at least some ETA or clarity otherwise.
Any updates? This is seriously impacting our business.
UPDATE
The engineering time worked on a fix and they expect it to be live in the next couple of hours
SECOND UPDATE
Fix is live
Thank you. Can you please take note of the request to introduce an automated test that checks no wrong CSS are served with the future deploys? At least this type of issue is very much avoidable with automated tests and we really need Bubble to become a reliable tool.
@gilles fix will roll out to dedicated in the next scheduled deploy (I believe that’s in the morning)
Our App has been up and running on LG SmartTV’s for awhile and we have been testing and developing to support Samsung SmartTV. Everything is displaying
as black screens for both devices.
It appears to be connected to bubble internals.
Console.log
Uncaught TypeError: window.display_page is not a function
at dynamic.js:160:8
(anonymous) @ dynamic.js:160
JS code that has an issue
window._bubble_page_load_data.js_execution_timings.dynamic_js_end_execution = Date.now();
window.display_page(app,‘start’);