Java.io.IOException: Manifest string is not a valid json object or string

after running eas build, the build is completed but the standalone app keeps stopping in my device. i ran the codebase with npx expo start --no-dev minify, works perfectly. when i run the standalone app on expo go it shows the error java.io.IoException: Manifest string is not a valid JSONObject or JSONArray: OK

hi there! are you using eas build and eas update or can you explain more about your project?

i used expo build to build a standalone apk. i successfully install the apk on my device. but the app keeps crashing on my device.

can you try rebuilding? also, i suggest moving to EAS Build - we will be shutting down expo build at the end of the year because EAS Build is its successor

Sorry my bad. I mean i am using eas build

did you try rebuilding? can you share a link to your build page?

I have tried it several times

the build at the link provided crashes with the following error:

10-05 08:18:24.594  7522  7555 E ReactNativeJS: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
10-05 08:18:24.594  7522  7555 E ReactNativeJS:       This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
10-05 08:18:24.596  7522  7556 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
10-05 08:18:24.596  7522  7556 E AndroidRuntime: Process: com.stevepath.blockplotmobile, PID: 7522
10-05 08:18:24.596  7522  7556 E AndroidRuntime: com.facebook.react.common.JavascriptException: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
10-05 08:18:24.596  7522  7556 E AndroidRuntime:       This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., stack:
10-05 08:18:24.596  7522  7556 E AndroidRuntime: <unknown>@13:289
10-05 08:18:24.596  7522  7556 E AndroidRuntime: value@58:3231
10-05 08:18:24.596  7522  7556 E AndroidRuntime: <unknown>@58:758
10-05 08:18:24.596  7522  7556 E AndroidRuntime: value@58:2582
10-05 08:18:24.596  7522  7556 E AndroidRuntime: value@58:730
10-05 08:18:24.596  7522  7556 E AndroidRuntime: value@-1
10-05 08:18:24.596  7522  7556 E AndroidRuntime:
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:938)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:223)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
10-05 08:18:24.596  7522  7556 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:923)

more info on this error: fyi/no-registered-application.md at main · expo/fyi · GitHub
more info in this general troubleshooting guide: Troubleshooting build errors and crashes - Expo Documentation

i solved the problem thanks @brents for your analysis and resource

1 Like

Hello, @brent is there a way to force expo to install incompatible packages building build?

Hi @stevepath

It’s not a matter of forcing Expo to install them, but rather getting npm or yarn (depending on what you use) to install them. Expo just calls npm, yarn (or pnpm) to install the packages.

But could you explain what you’re trying to do? Perhaps you’re getting an error from npm about incompatible peer dependencies?

i have written my app. and it is working fine. i am usin react-native-svg and eact-native-qrcode-svg. but both versions are not compactible but everything is working fine. But if i try to build my app with eas because both packages are not compactible, the build fails. i am using expo sdk 47. so i can’t downgrade the version of react-native-svg. I am looking for a way to force eas to ignore the package incompactible during building my app

Can you please paste the error message here? Are you sure it doesn’t say something about incompatible peer dependencies and using --legacy-peer-deps?

If that’s it, you can get npm to use that option by e.g. doing this:

thanks this worked. but can you help to check what’s making this build Build Details — 144c650e-ce45-4d04-8955-726f3da6d6ab — blockplot-V1-mobile — Expo to crash on andriod

thanks in advance

hmmm… I got this by searching for “FATAL” in the output of adb logcat -d:

--------- beginning of crash
01-17 17:55:43.114  5316  5351 E AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
01-17 17:55:43.114  5316  5351 E AndroidRuntime: Process: com.stevepath.blockplotV1mobile, PID: 5316
01-17 17:55:43.114  5316  5351 E AndroidRuntime: com.facebook.react.common.JavascriptException: Invariant Violation: Tried to register two views with the same name RNCWebView, stack:
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@13:289
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@131:360
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1801:134
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1800:644
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1799:201
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1798:168
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1797:226
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1793:605
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1787:711
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1786:6810
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1777:1152
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@1671:2906
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: <unknown>@6:1504
01-17 17:55:43.114  5316  5351 E AndroidRuntime: h@2:1707
01-17 17:55:43.114  5316  5351 E AndroidRuntime: d@2:1080
01-17 17:55:43.114  5316  5351 E AndroidRuntime: global code@2009:3
01-17 17:55:43.114  5316  5351 E AndroidRuntime:
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at com.facebook.jni.NativeRunnable.run(Native Method)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at android.os.Handler.handleCallback(Handler.java:938)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:99)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:201)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:288)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
01-17 17:55:43.114  5316  5351 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:920)
[...]
01-17 17:55:43.189  5316  5351 I Process : Sending signal. PID: 5316 SIG: 9

If you look at the documentation that Brent linked you to you’ll see the first one mentions this:

  • Multiple versions of a JavaScript package that includes native dependencies. You may see an error like “Invariant violation: Tried to register two views with the same name …” if this is the case.

Since this is complaining about RNCWebView, see what you get if you run npm why react-native-webview. I’m not sure if that will point you in the right direction, but it’s worth a look.

Also, what are the contents of your dependencies and devDependencies sections in package.json?

Thanks @wodin. I checked that and i uninstalled the package with confliting version. Could you please this also for Build Details — 58f0dd63-7087-48a5-a076-cd76b3f4cc07 — blockplot-V1-mobile — Expo. It is also crashing

hello, can you all help me solve this problem? …Your project may not work correctly until you install the correct versions of the packages.
Install individual packages by running npx expo install @react-native-firebase/app@~15.4.0

Hi @stevepath

Please try running adb logcat -d in a terminal window right after the app crashes. You will need to have the phone connected to your computer via USB cable and enable USB debugging.

See point 1 under “Set up a device for development

You can save the output of adb logcat -d to a file like this:

adb logcat -d >logcat.txt

Then open logcat.txt and search for FATAL or beginning of crash to find the error.