Splash Screen Issue After Deployment

I’ve deployed my mobile app for Internal Testing. Sill, the app can’t pass the splash screen. It works perfectly in version test and BubbleGO

Anybody who successfully deployed their app on Google Play Store, please guide me.
What I did:
1- Deployed on Bubble as [Release Status - Completed, Deploy Track - Internal, Build Type - New Built]
2- Uploaded the .aab file received from Bubble in Internal Testing and published it.

image

Having exact same issue since afternoon yesterday. Worked perfectly prior. And works on every other platform: iOS in Preview, BubbleGo, and TestFlight, and in Android on Preview and BubbleGo. Still not working. And now my Android builds are failing in the editor. Im stuck.

I got a message from a support tech yesterday saying my app got impacted by a mobile engine change. So I suspect it’s related, but I havent gotten a response since.

@nick.carroll Please guide
The app is stuck on splash screen. I’ve deployed the built multiple times today, still the app crashes before opening the index page. How to debug this?

My Guess its that they are working on something, hopefully to speed thing up on Android side. I hope that is the case. Give them a moment a try again later

Still happening for me too. I have a support ticket with them and have given them some info to try to diagnose.

They asked me to check my Play Console for error logs if any. You can follow the directions at this link: View crashes and application not responding errors - Play Console Help.

I did check and there’s nothing noted, no crashes or ANRs. Curious if you can check to see if you have any.

@openraf great advice from @jomo25. Please file a bug report with as much info as possible, including any crash data in the google play developer console - this will help us figure out whats going on faster

I’ve raised the bug report with the ANR log. Waiting for the solution…
Asked GPT to understand the ANR log - apparently the crash at the splash screen typically happens due to misconfiguration, missing permissions, or initialization errors.
Then I’ve rechecked all the Google play/cloud console files, values, keystore and created a new deployment. Still no success.

We are seeing a few other reports of this as well - team is actively looking into it right now

As an update, a fix was pushed which addressed the problem I was having and now my app is working! I dont know if the fix will address others having similar issues, but it might? I deployed a new build (major to be safe), and not an OTA.

1 Like