com.tns.NativeScriptException - MetaData cannot be opened.

[shiv19]

Been seeing this crash report at an alarming rate lately

java.lang.RuntimeException: 
  at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6214)
  at android.app.ActivityThread.access$1200 (ActivityThread.java:236)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1784)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:214)
  at android.app.ActivityThread.main (ActivityThread.java:7037)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:494)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:965)
Caused by: com.tns.NativeScriptException: 
  at com.tns.Runtime.initNativeScript (Native Method)
  at com.tns.Runtime.init (Runtime.java:627)
  at com.tns.Runtime.init (Runtime.java:601)
  at com.tns.Runtime.initRuntime (Runtime.java:591)
  at com.tns.Runtime.initializeRuntimeWithConfiguration (Runtime.java:566)
  at com.tns.RuntimeHelper.initRuntime (RuntimeHelper.java:163)
  at com.tns.NativeScriptApplication.onCreate (NativeScriptApplication.java:20)
  at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1154)
  at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6209)

[farfromrefug]

Duplicate of this issue i think NativeScript/NativeScript#8037 and it should contain a fix too

[shiv19]

@farfromrefug what I reported is different from what @maxorlovsky reported here.

[farfromrefug]

@shiv19 ok sorry looked at the last message! Sorry

[maxorlovsky]

deleted mine, to not confuse anyone else

[Jmchemama]

I have same issue.

[anmaitrannguyen]

I have the same issues. The crash rate is at alarm rate.

[vtrifonov]

Do you use crashlytics or something similar, so that we can get more information about the exception as the message is missing here and we don't know what is the exact error?

[anmaitrannguyen]

We does have Crashlytics. But these crash does not display on Crashlytics, these crash is new, after we upgrade the app from Nativescript 6.1.2 to Nativescript 6.3.0. Only appear on Google Play Console. Some of our user report the app crash at the first time after upgrade, but working fine after that. Not sure this can give us any hint.
java.lang.RuntimeException: at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6276) at android.app.ActivityThread.access$1200 (ActivityThread.java:238) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1794) at android.os.Handler.dispatchMessage (Handler.java:106) at android.os.Looper.loop (Looper.java:214) at android.app.ActivityThread.main (ActivityThread.java:7099) at java.lang.reflect.Method.invoke (Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:494) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:965) Caused by: com.tns.NativeScriptException: at com.tns.Runtime.initNativeScript (Native Method) at com.tns.Runtime.init (Runtime.java:627) at com.tns.Runtime.init (Runtime.java:601) at com.tns.Runtime.initRuntime (Runtime.java:591) at com.tns.Runtime.initializeRuntimeWithConfiguration (Runtime.java:566) at com.tns.RuntimeHelper.initRuntime (RuntimeHelper.java:163) at com.tns.NativeScriptApplication.onCreate (NativeScriptApplication.java:19) at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1158) at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6271)

[jpierront]

Exactly the same for me.
It seems that it appeared when switching to NativeScript 6.2. (But I didn't change only that dependency with this update)
This seems to happen only on Android 9 and 10.

[jessorlisa]

Was anyone able to solve that?

[7ammer]

Getting the same error stack after updating last week. 6,491 reports so far! 😬

Our project jumped from:
"tns-core-modules": "^6.0.0" to "^6.5.1",
"tns-android": "6.0.0" to "6.5.0"
"tns-ios": "6.0.1" to "6.5.0"

Crashalytics is not reporting these errors. In-fact the crash rate on Crashlytics went down!

[7ammer]

Perhaps it maybe helpful if we provided more detailed info on our projects?

• "tns --version": "6.5.0"
• "tns-core-modules": "6.5.1"
• framework: "vue"
• tns-ios: "6.5.0"
• tns-android: "6.5.0"

"dependencies": {
  "@vue/devtools": "^5.0.6",
  "nativescript-advanced-webview": "^3.0.2",
  "nativescript-animated-circle": "^1.2.0",
  "nativescript-datetimepicker": "^1.2.1",
  "nativescript-dev-appium": "^6.1.3",
  "nativescript-local-notifications": "^4.1.5",
  "nativescript-localstorage": "^2.0.0",
  "nativescript-permissions": "^1.2.3",
  "nativescript-plugin-firebase": "^10.3.0",
  "nativescript-social-share": "^1.5.2",
  "nativescript-socketio": "^3.2.1",
  "nativescript-statusbar": "^5.0.0",
  "nativescript-toasty": "^3.0.0-alpha.2",
  "nativescript-vue": "^2.6.0",
  "nativescript-vue-devtools": "^1.2.0",
  "nativescript-webview-interface": "^1.4.3",
  "tns-core-modules": "^6.5.1",
  "url-parse": "^1.4.7",
  "util-inspect": "^0.1.8"
},
"devDependencies": {
  "@babel/core": "^7.0.0",
  "@babel/preset-env": "^7.0.0",
  "@types/chai": "~4.1.7",
  "@types/mocha": "~5.2.5",
  "@types/node": "^12.12.16",
  "babel-loader": "^8.0.2",
  "chai": "~4.1.2",
  "mocha": "~5.2.0",
  "mocha-junit-reporter": "~1.18.0",
  "mocha-multi": "~1.0.1",
  "mochawesome": "~3.1.2",
  "nativescript-dev-webpack": "^1.0.0",
  "nativescript-vue-template-compiler": "^2.5.0",
  "nativescript-worker-loader": "^0.11.0",
  "node-sass": "^4.9.2",
  "tns-platform-declarations": "^6.0.0",
  "typescript": "^3.2.4",
  "vue": "^2.5.22",
  "vue-loader": "^15.4.0"
}

[NathanaelA]

@anmaitrannguyen - can you 100% confirm the issue started when you jumped from 6.1.2 (Do you know which specific versions of core modules & runtime in the 6.1.2 set you used before it started crashing)

Nailing down the exact point it started is critical in trying to figure out what change could have caused this issue, since the log is non-existent.

---

I assume based on this issue and the other issue in the runtime that nobody has been able to duplicate it locally; just clients and seeing your error count on the nice dashboard.

One possible idea on how to duplicate it locally;

1. Deinstall the app on your android 9/10 phone. (Make sure you are on Android 9 or 10!)
2. Install the Prior version RELEASE (working) version (what you uploaded to Google!)
3. Install the new version (again what you uploaded to Google!)
   (It would be much better for your test if you re-use what you originally uploaded to Google; because tooling changes the APK, if you rebuild your 6.1 version using the 6.5 tooling your app could be slightly different)

You might need to Install doing a sideload and double clicking on APK you manually uploaded to your phone, DO NOT USE ADB to install, you can use ADB to copy it to the phone; but lets try and make this as close to what would happen with a client and make the phone do all the work.

If using sideload method doesn't work to duplicate it, deinstall the app; create a beta test of your app; upload GOOD version, have phone join the beta test; and download it. Then do another beta with the "broken" version so that you phone downloads and installs it from Google; rinse and repeat a few times to see if you can cause the error to occur on your device.

---

Specific questions we need to answer:

1. Which specific version of Android Runtime and Core was the issue introduced
2. Are any/all apps using Workers?

---

If some of you can try releasing a new "minor" fix of your app using:

• Android 6.2.0 w/ Core 6.2.0 (Earliest 6.2)
• Android 6.2.0 w/ Core 6.2.3 (Latest 6.2)
• Android 6.1.0 w/ Core 6.1.0 (Earliest 6.1)
• Android 6.1.2 w/ Core 6.1.2 (Latest 6.1)

If we can isolate the version of the change, we can figure out what change was introduced and then figure out why it is causing the crash...

[NathanaelA]

@jessorlisa @jpierront @7ammer @shiv19 @anmaitrannguyen @Jmchemama @saschaarthur

Ok, I've started a spreadsheet; it would be very helpful if you can all fill in the details for your app here:
https://docs.google.com/spreadsheets/d/1qU-H3Kp-OGCmRffvfw4IejSDwpf5Un7bq-sR8XoL_X8/edit?usp=sharing

And if any of you can do testing of your app with 6.1 and/or 6.2 to see if we can narrow down where the issue occurred that would also be super!