Android 12 users report app crash after sign-up (before message/user list screen)

Get Help
1

I’ve received reports from users on Android 12 that the app crashes immediately after opening. Sign-up completes successfully, but the app seems to crash before navigating to the message screen or user list screen.

I also have one similar crash report from an iOS user, and I’m currently confirming which iOS version they’re using.

Are there any known or recently reported issues on the Adalo side related to Android 12 (or specific components / lists / navigation) that could cause this kind of crash?

2

Hi @Yuki.O,

Is it with a recent published version for Android? After signup, where does the user directs in the app? Any screenshots?

Have you submitted a support ticket? : New Bug Form

Thank you and have a great day!

3

Yes.
It’s the latest published Android version. After signup, the user should be directed to the main screen, but the app crashes before the message or user list screen appears. The user says the app crashes immediately on launch, so they’re unable to take a screenshot.

4

Hi, in your app after login you have Admob Component, a Map or a QR Scanner? I experienced the same on old phones running Android 12. Solved by removing those components in the Home Screen.

1 Like
5

Hi @Eugen, thanks for sharing.
There is no AdMob, map, or QR scanner component on the home screen in my app. I’m still investigating the cause, and it’s not yet clear whether this is an Adalo-related issue. Since users are currently blocked by this crash, I’d really like to resolve it as quickly as possible.

6

I’ve received an update from the user. It seems the app crashes only when navigating to this specific page. On that screen, there are three switching buttons and a Lottie animation. Could these be too heavy or problematic for Android 12?

スクリーンショット 2025-12-21 8.27.45
スクリーンショット 2025-12-21 8.27.45241×557 16.4 KB

7

Thanks for the screenshot @Yuki.O ! I’ve faced few crashing issues with some components like Eugenio mentioned and in recent months when sizes (see here : Crash when using “Current Message” component inside Custom List after enabling new React Native version - #6 by Dilon) has been 0 where changing to 1 fixes which probably might came along with the new react native version. Check those carefully (hidden components too like inputs, countdowns, etc.. ) and let us know, thank you and have a great day! (If you could share the crash log from Google in a DM, that might help to identify the issue)

Edit : After you sent me the crash log from Google Play Console in a DM, what I can see is there should be a component (like a text component, input component,..) with the font size 0 in the screen and changing to 1 should fix and if not, please let here know

1 Like
8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.