-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
java.lang.RuntimeException / Caused by: com.tns.NativeScriptException: #8550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This comment was marked as abuse.
This comment was marked as abuse.
Any further ideas how to track it down? |
Can you list out which plugins are you using in your project? |
|
I'm trying to debug which can cause this error. From my view, the App is crashing on this line:
The dexThumb, dexDir, classLoader and nativeLibDir can be the issues here. I will checking what can cause the crash. |
if theres anything i can support you with let me know, we have an highly crashing build on production with this bug.. |
I currently have 8,041 reports from the last 14 days :L I think this is the same issue:
|
Hey @NathanaelA, |
This comment was marked as abuse.
This comment was marked as abuse.
Hi @NathanaelA, thank you for actioning this. I appreciate it! I jumped from 6.0.0 to 6.5.1 |
Hi @NathanWalker ,
The line in vendor.js:1:355308 The line at bundle.js:85 This crash happen when we try to upgrade these package: We have the Samsung Galaxy A50, the device in the crash list, tried to reproduce this issues, but so far still not get the crash. There must be a special condition to make this crash appear. |
This comment was marked as abuse.
This comment was marked as abuse.
Issue: no --nolazy flag Edit: |
Was is related? |
Hello, Hard to say.. what i figured our so far is that "com.tns.NativeScriptException" is a generic exception for 'everything'. There could be plenty of reasons for this. More information you could gather about your case (if you have one) with the "adb log | logcat" console. So far we disabled everything which is kind of unstable atm:
Plenty of our errors were coming from NativeScript/android#1546 which is solved now. But sadly we still have some of this "com.tns.NativeScriptException" left, but the rate itself dropped a lot (<1%, compared to before) without all of this features, so i can only suggest you do do the same for the moment. |
Uh oh!
There was an error while loading. Please reload this page.
Hello,
We have plenty of app crash reports from google play console like this:
Sadly it looks like our code is not even running at this point of time and the framework is not starting up. Our devices are not crashing at all.
How can we trace this down / debug it?
Nativescript 6.4.1
We removed aab builds already, because we had here linking errors: NativeScript/nativescript-dev-webpack#1135
Our app is well tested (on our devices) and we already released it to our customers and we fighting with a lot of framework bugs it seems, which really leads to bad reviews..
The text was updated successfully, but these errors were encountered: