Crash caused by an error in AndroidManifest.xml

There is blocking issue in thunkable platform, please help.
I opened a new ticket on github

It is very urgent because it generates crash in android apps that use admob.

Sorry if I use also this channel, I do this with hope that someone can fix this very soon.

In the following u can see the description of the bug.



Since today the Thunkable platform encode the ~ symbol with %7E in Android Manifest in the meta-data

This causes a crash anytime I open my app.

It is a very urgent issue because I cannot deliver the app to my customers.


Does this affect:
Drag and Drop UI - Android

Steps to Reproduce

  1. Insert Android Admob App ID in project settings (app id normally contains symbol ~)
  2. Build and download the APK
  3. Open the app

Expected Behavior

No crash expected

Actual Behavior

What actually happens?
The App crashes immediately every time

Project Link


The issue is located in the android manifest

ADB debugger shows this
java.lang.RuntimeException: Unable to get provider java.lang.IllegalStateException:
02-09 12:36:18.362 28630 28630 E AndroidRuntime:
02-09 12:36:18.362 28630 28630 E AndroidRuntime: ******************************************************************************
02-09 12:36:18.362 28630 28630 E AndroidRuntime: * Invalid application ID. Follow instructions here: *
02-09 12:36:18.362 28630 28630 E AndroidRuntime: * *
02-09 12:36:18.362 28630 28630 E AndroidRuntime: * to find your app ID. *
02-09 12:36:18.362 28630 28630 E AndroidRuntime: ******************************************************************************

Hey @dani19130a

We just pushed an update to live. Please try building your app again! Sorry for the issue here!

1 Like

Hey @jared
Yes, it works, many thanks to solve it so quickly!

1 Like


Since a couple of days, my app is crashing when leaving or closing specifics screens (below code). Works fine in WEB, iOS and Android Live testing app, but after building, I just can not get it working as usual (no code changes). The issue, is only on the installed version from APK on same phones have been always testing on.



what may be common is the web viewer url being assigned to “” which have been on de code long time ago with no problem.

It is something related to Android apk build server? Any one else having this issue?



Are you still. experiencing this today?

What if you publish without using a blank URL.

For example using just https://


When I first added webviewer with html code, (month ago) I needed to clean up URL to avoid crash and worked like that with no issues. I can try with http:// only but, unless something changed on apk building service, won’t be different.

Also it is working fine when running on thunkable live testing app on Android and iOS and compiled iOS.

José M Pandare

I also got the bellow error on last two or three apk requests:

Error: Command failed: cd /thunkable/androidBuildServer/…/thunkableCompanion/android/; ./gradlew AssembleRelease :warning: Cannot resolve the path to “@react-native-community/cli” package. :warning: Cannot resolve the path to “@react-native-community/cli” package. error node_modules/@firebase/database/dist/index.esm2017.js: Call retries were exceeded. FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ‘:app:bundleReleaseJsAndAssets’. > Process ‘command ‘node’’ finished with non-zero exit value 1 * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at BUILD FAILED in 5m 51s

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