Why some Android users are seeing crashes after a phone update

Getting reports that your app suddenly crashes, gets stuck while opening, or no longer loads for a few users—even though you haven't touched the app? Here's the breakdown.

• Your app on the Play Store is exactly the same as the day you built it. This issue usually starts after a user's phone installs a newer Android update.
• Builds made before October 2025 included an older networking component that is no longer properly supported on certain newer Android versions, causing the app to fail during launch.
• It can seem random because it may affect any phone brand once the device is running a new enough Android version. It also feels sudden because the phone may have updated overnight—not the app. That's why only some of your users are affected.

Nothing changed in your app, and nothing changed on our end. Android changed underneath it.

Has BDK fixed this?

Yes. In October 2025, we removed the older component responsible for this issue from all new Android builds. New builds also include our latest Android performance and stability improvements.

How do I check whether my app is affected?

Open your app's Google Play listing and look at the version number under App info → Version. Then compare it with the build history on your BDK project page: if the version live on Play was built before October 2025, it carries the older component.

If you're not sure, message us on the chat with your project code and we'll check it for you.

What do I need to do?

Request a rebuild, then publish the new Android build as an update on Google Play.

1. Go to your BDK project page.
2. Open your project's Dashboard.
3. Request a rebuild.
4. Publish the new Android build to Google Play as usual.

Once the update is live, affected users simply need to update the app, and the crashes should stop.

What does a rebuild cost?

Rebuilds are flat $39 for a project—iOS and Android included, not $39 per platform.

I only need Android — does a rebuild change my iOS app too?

A rebuild produces a fresh build for both platforms, because your project is built as a single app for Android and iOS. That doesn't force your hand on iOS: publishing is a separate step you control. If Android is all you need right now, publish the Android build to Google Play and simply leave the iOS build unpublished. Your existing App Store version stays live and untouched.

Is my iOS app affected by this issue?

No. This is caused by a change in Android, and it affects Android builds only. Your iOS app will keep working exactly as it does today, whether or not you publish the new iOS build. The new iOS build may include performance improvements depending on the date your previous build.

Can this be fixed without a rebuild?

No. The affected component is built into the version currently published on Google Play. It can't be changed through Bubble or fixed remotely, and reinstalling the same old version won't solve the issue. A rebuild is required.

Should I rebuild even if only a few users are affected?

Ideally, yes—if your Android build was made before October 2025.

It may affect only a handful of users today, but that number can grow as more phones receive Android updates or users move to newer devices. Rebuilding now helps you get ahead of the issue.

Will I need a new Play Store listing?

No. You can publish the rebuild as a normal update to your existing listing. Your users, reviews, downloads, and app data will all remain exactly as they are.

Updated on: 07/28/2026