πŸ”Troubleshooting

In this section, you can find guides that can help troubleshoot any Natively-related issue.

Push Notification doesn't work in the Android/iOS app

The first thing you must go through this checklist:

In-App Purchases doesn’t work in the Android/iOS app

The first thing you must go through this checklist:

I have a problem with a different Native feature

If you are faced with a problem related to a different native feature, go through this checklist:

FAQ

This usually happens when the plugin can't find the element it needs to trigger the action. Here are a few things to check:

  • Visibility: Make sure the element associated with the action is placed on the page and is visible.

  • Element Location: Don't place the element inside another element that might be hidden when you need to use the action (like a floating group, popup, focus group, or repeating group).

  • Required Fields: Ensure all the required fields for the action are filled in. If you're using dynamic data, double-check that the values are not empty.

My app was rejected by App Store / Google Play

Often some apps are got rejected by App Store or Google Play. It's normal.

First, you need to read the reason for the rejection message and apply the action steps.

Many rejections from Apple/Google teams are related to inaccurate descriptions. It might be related to unclear permission texts, In-App purchases product descriptions, or event application descriptions in a store. Here you can find a few useful links that can help you fix the problem:

After I close the app and then open it, data in RG are not updated (Chat case)

Unfortunately, we cannot handle this since it's a bubble socket issue. Check this thread on the bubble forum.

I'm seeing an error when I try to rebuild my app - new agreement is missing

Go to your App Store Connect and follow the instructions provided in the yellow banner at the top of the page.

I'm seeing an error when I try to rebuild my app - app version

This error appears when the app version in your Natively dashboard is lower then the app version in your App Store Connect > TestFlight. Or if the current version in your TestFlight is closed for new builds. If the app's version in TestFlight is 1.0.0, please provide version 1.0.1 (or higher) for a new build in your Natively dashboard. You can find more about app versioning in this article: https://semver.org/

Why am I seeing an error when I try to add my iOS credentials?

This error appears when some of the data you've provided is invalid or mismatched. The most common reasons for this are:

  • The AuthKey either has an incorrect role (it must be App Manager), has been revoked, or is not associated with the provided Issuer ID.

  • The Bundle ID you entered does not exist or is not associated with the Apple account the AuthKey is for.

  • The Bundle ID is not correctly linked to the App Store App ID you provided.

Follow our guide on how to provide iOS credentials for a new app here: iOS App

My app opens a new tab of the internal browser on launch

This can occur when the website's actual domain doesn't match the App URL you provided in the Natively dashboard.

For example, if you set your App URL as https://subdomain.domain.com, but the website redirects to https://example.com upon opening, the app will recognize https://example.com as an external website. Since this domain isn't the one you initially specified as your App URL, it will open in a new tab within the app.

To resolve this, update the App URL in your Natively dashboard to reflect the actual domain your website uses. After saving this change, rebuild your app.

Those already cover:

  • Push Notifications not working

  • Deeplinks not working

  • In-App Purchases not working

  • Generic β€œdifferent native feature not working”

  • Errors with Natively plugin actions

  • App rejected by App Store / Google Play

  • Data not refreshing after reopening app

  • Build errors (new agreement missing, app version)

  • iOS credentials error

  • App opens new tab of internal browser on launch


Extended Troubleshooting FAQ (Additional Issues)

Social Authentication

Apple Sign In doesn’t work

  • Ensure Social Auth is enabled in Natively settings.

  • Rebuild your app after enabling.

  • Confirm your Apple Services ID and Bundle ID match.

  • Make sure Universal Links (deeplinks) are configured.

  • On iOS 17+, use the latest Natively SDK β€” older builds may break.

Google Sign In doesn’t work

  • Use Natively’s Social Auth plugin instead of Bubble’s default Google plugin.

  • Check your Google Cloud Console: Redirect URIs must include your app’s scheme.

  • Rebuild the app after enabling Social Auth.

Facebook Login doesn’t work

  • Ensure your app is set up in Facebook Developer Console with your Bundle ID.

  • Add your redirect URI under Valid OAuth Redirects.

  • Rebuild your app after enabling Social Auth.


AdMob

Ads don’t display in my app

  • AdMob does not work in Preview apps. You must build your app to test.

  • Ensure you’ve followed the AdMob setup guide.

  • Confirm your Ad Unit IDs are correct.

  • Test using Google’s test ads before switching to production ads.

  • Allow up to 24 hours for new ads to propagate.


Analytics

Facebook / AppsFlyer analytics events not showing

  • Ensure the correct SDK is enabled in your Natively app settings.

  • Verify that you’ve added the right App ID and keys in Facebook / AppsFlyer dashboards.

  • Rebuild after enabling analytics.

  • Allow up to 24h for events to appear.


Publishing and Build Issues

My iOS build count decreased after a failed build

Build counts are deducted for all attempts, even failed ones. If the failure was due to a Natively issue, contact support to restore credits.

Play Console shows a warning about 16 KB memory page sizes (mandatory in 2026)

This is a Google compliance requirement. BuildNatively already has an update for this new requirement. Make a new build and submit it to Google.

App rejected for missing Privacy Policy

  • Both Apple and Google require a Privacy Policy link.

  • Add your Privacy Policy URL in Natively β†’ Settings.

  • Make sure the URL is public and accessible.


App Behavior and UX

My app shows outdated data after backgrounding

  • Add workflows to refresh repeating groups or run β€œDo every X seconds”.

  • Use β€œOn page load” β†’ Refresh data.

  • Store state in local storage and re-fetch on app resume.

On iOS, tapping input fields zooms in

This is expected iOS behavior. Use a font size of at least 16px to avoid zooming.

Android back button closes the app instead of going back

This is the default system behavior. You can customize back button handling in app settings.

My app refreshes when scrolling up on Android

Disable the β€œPull to refresh” option under Appearance β†’ Style or per page.

My app crashes when opening an external app or URL

  • Update to the latest SDK and rebuild.

  • Confirm that the external URL scheme or intent is valid.

My app is stuck on a white screen at startup

  • Ensure your app’s initial URL is set correctly in Natively.

  • Verify your website loads in Safari/Chrome first.

  • Check if the error only occurs when users are logged in (SPA issue).


App Assets

I can’t upload my app icon or splash screen

My app icon looks blurry or stretched

  • Upload a high-resolution 1024Γ—1024 PNG.

  • Avoid transparency or rounded corners β€” app stores add their own masks.


Platform Limitations

Which features don’t work in the Preview app?

Not supported in Preview:

  • Push notifications

  • Deeplinks

  • In-app purchases

  • Social Authentication

  • AdMob

  • Analytics (Facebook, AppsFlyer)

  • HealthKit

  • Background geolocation

Does my app clear cookies when closed?

No. Cookies persist to keep users logged in.

Can I build for Firestick, Roku, or Android TV?

No. Natively currently only supports iOS and Android mobile apps.

Does Natively support offline mode or service workers?

No. Natively apps require an internet connection. Offline mode is not supported.


If you still have any issues, contact us on support chat or by email at [email protected]

Last updated

Was this helpful?