Maybe I spotted the reason for this error but I’m asking for confirmation.
I wrapped my Bubble app and my users use it on a wide variety of devices. Each time an unhandled error takes place I get an email with the error’s code and the error’s message.
For long time I’ve been receiving this error from some users and I never understood the cause so far. Apparently, in the cases I was aware of, it was a non-blocking error. The user was receiving no message ( I guess because I have a WF that triggers an email) but only experiencing a glitch. Looking at the logs they were not doing anything strange. Sometimes they were simply resuming the app from background.
What more, this error is quite undocumented. It doesn’t even have a proper code.
Today I maybe found the reason for it. One of my clients had this problem while trying to login when he was in front of me. He was using a very old iPad with iOS 12. Even after deleting the app (including it’s data) and reinstalling it, the problem persisted. The problem didn’t occur when using a more recent device.
Could it be that the reason for this error is a device that cannot manage a minimum of computing power/hasn’t a minimum available cache?
The weird detail is that the above client had been using the same device for more than a year. Maybe the cache of the device was full (is the cache of Safari shared with the cache of a wrapped app?).
If the above is the reason I could trigger a popup to the user asking him to clean the cache or get a better device.
Ciao Gianluca! I have been facing the same problem, but I don’t even think it’s to do with older devices.
I have a bubble app that i simply access through a mobile device (Pixel 7a in this case), and I get the same error on a workflow that otherwise works on desktop. Testing both desktop and mobile using Chrome browser.
If on the mobile Chrome application I open the bubble app website as a “Desktop Site” and run the workflow, then there is no error. If on the mobile site, the error persists.
Not sure if this helps, but I would also like to have a solution for this.
Hi @swms ,
after opening this thread, I started logging each time the error was taking place. I’m logging in particular the device model and the user agent. I’m pasting the data below. I guess the reason for the device is sometimes empty is because the user was using the regular browser instead of the wrapped app . If this interpretation is correct, it means that the error takes place also on a regular browser.
In general it seems that the error is happening on old/cheap devices but not always. I really have no clue
user
device model
user agent
occurences
User 1
(empty)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36
2
User 2
samsung SM-A505FN
Mozilla/5.0 (Linux; Android 11; SM-A505FN Build/RP1A.200720.012) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/122.0.6261.119 Mobile Safari/537.36
1
User 2
samsung SM-A505FN
Mozilla/5.0 (Linux; Android 11; SM-A505FN Build/RP1A.200720.012) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/123.0.6312.118 Mobile Safari/537.36
1
User 3
(empty)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36
2
User 6
HUAWEI COL-L29
Mozilla/5.0 (Linux; Android 10; COL-L29 Build/HUAWEICOL-L29) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/122.0.6261.119 Mobile Safari/537.36
2
User 7
(empty)
Mozilla/5.0 (iPad; CPU OS 12_5_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.2 Mobile/15E148 Safari/604.1
4
User 7
iPad4,8
Mozilla/5.0 (iPad; CPU OS 12_5_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
2
User 7
iPad4,8
Mozilla/5.0 (iPad; CPU OS 12_5_7 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
4
User 8
Xiaomi Mi A2 Lite
Mozilla/5.0 (Linux; Android 10; Mi A2 Lite Build/QKQ1.191002.002) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/122.0.6261.105 Mobile Safari/537.36
5
User 8
Xiaomi Mi A2 Lite
Mozilla/5.0 (Linux; Android 10; Mi A2 Lite Build/QKQ1.191002.002) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/123.0.6312.40 Mobile Safari/537.36
2
User 8
iPhone8,4
Mozilla/5.0 (iPhone; CPU iPhone OS 12_1_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/16D57
I understand some users with lower performance devices are experiencing difficulties to conclude Workflows. I believe you could go two ways:
1- Start using custom actions on the worflow page and trigger them on the user side, this could alleviate and reduce the device’s effort needed.
2- Use Backend API actions to execute the long demanding operations and return data to the user if needed.
Also, please keep in mind to use a clean and very light design. To achieve that, standardize elements and use them the same through your app.
The last thing to consider, regarding the UI weight is to create and use reusable elements and built in data options.
I don’t think we’re anywhere closer to determining the root cause of this issue. Would be great if bubble support lent a hand here.
In my case it certainly doesn’t have anything to do with older device or heavy workloads. The “mobile” (unwrapped) interface for my app is just a page set up so it displays nicely in Responsive mode on mobile screens. All the user does is enter some text and click a Submit button which creates a thing in the database with the user’s input, and then triggers a backend API workflow to create a bunch of data in the database based on that input.
Works perfectly on desktop, multiple browsers, as well as on mobile (i only tested on Android) when using Desktop Site mode in Chrome browser. So something must be happening when it’s in mobile site mode on Chrome.
I assume you all are using some third party to wrap your Bubble app. If so have you gotten in touch with that service provider? Bubble support will not offer any help if that is the case.
Yes, I’m using BDK and they guarantee that opening a Bubble app via their wrapping is exactly the same as opening it via a regular browser. What more, as per my logs, the problem takes place also when my users are not inside the wrapping but in standard browsers.
If you deduced that’s it’s a Bubble issue then your only option is to file a bug report with your findings at the moment. That’s what @mikeloc would suggest too though i think he’s on a hiatus.
In the meantime do check if any plugins that got updated affected your app. There was a recent post about Orchestra plugin producing similar issues since Zeroqode bought it over.
