Perpetual updating the app

jos2 · 2024-09-12T09:12:40.248Z

We have an native mobile app (ios and android) that loads our bubble webapp. That works fine on all devices except on the Pixel phones. When the native app shows the bubble page in the webview then it continuously shows the message “We just updated this page. Please refresh the page to get the latest version”. then it refresh the webview and the message is shown again, and again, it gets into an loop and it never stops… and we do no updates at all.

And sometimes, after closing and opening the app several times, it is showing the page whitout “update the app”. but then the whole page is not working at all, all javascripts (every conditions) are not working.

This only happens on Pixel phones.

is there anyone who has also experienced this? And has maybe an solution to fix this? I’ll also ask bubble is they know this issue.

jos2 · 2024-09-18T08:58:14.853Z

We identified the error in our case. The issue was with the user agent. The wrapper we use to load our Bubble app appended additional information to the user agent, including the device manufacturer. Since the app was running on a Pixel phone, the word ‘Google’ was added to the user agent, which caused an infinite ‘updating the app’ loop/crash. After removing the word ‘Google,’ the error was resolved, and the webpage became accessible again.

Additionally, when we manually added the word ‘Google’ to our web app in the browser, it caused the browser to crash. We also tested this on a Samsung phone, and adding the word ‘Google’ caused the app on that device to crash as well. It seems that Bubble don’t like the word ‘Google’ being present in the user agent.

We also saw that bubble loads modules, javascrip, html, css differently when the word “Google” is used in the user agent, why we don’t know and Bubble doesn’t want to answer this question.

georgecollier · 2024-09-18T09:07:35.528Z

jos2:

We also saw that bubble loads modules, javascrip, html, css differently when the word “Google” is used in the user agent, why we don’t know and Bubble doesn’t want to answer this question.

Probably because it thinks it’s a bot / crawler. Good on you for being able to narrow down that error… would be good to get an idea of how this can be avoided

jos2 · 2024-09-18T09:24:03.799Z

We didn’t think about the bot/crawler, but that could be the issue. I hope they will treat the Pixel phone like the others, as the user base for Pixel phones is growing.

We filled an bugreport but the team that is answering reports keep saying “We aren’t able to provide support for wrapped/native apps as mobile app development is not currently one of Bubble’s core features”. They doesn’t understand that this is an error on the bubble side. Maybe someone on the forum with inside connections can pass this to the right team.

georgecollier · 2024-09-18T09:25:28.172Z

jos2:

“We aren’t able to provide support for wrapped/native apps as mobile app development is not currently one of Bubble’s core features”.

Oh, well that’s fair enough. If it works on browser and not your PWA, then that’s not Bubble’s problem

jos2 · 2024-09-18T09:35:14.204Z

Yes, but because Bubble is loading the HTML, CSS, and JavaScript differently on Pixel phones, so we asked the Bubble team if removing the word ‘Google’ from the user agent would have any consequences. We’re wondering if the content is being loaded differently for a specific reason. And maybe they will experience this issue when they are developing the mobile version.

system · 2024-09-26T09:13:14.084Z

This topic was automatically closed after 14 days. New replies are no longer allowed.