microsoft/react-native-code-push

Receiving No virtual method object()Lorg/json/e on app start

Closed this issue · 5 comments

pkpardeep482 commented

Hi, i am receiving this crash on my release build on app start. Debug builds are working fine. I am using react-native 0.67.4

"appcenter": "4.3.0",
"appcenter-analytics": "4.3.0",
"appcenter-crashes": "4.3.0",
"react-native-code-push": "7.0.5",

Fatal Exception: java.lang.NoSuchMethodError: No virtual method object()Lorg/json/e; in class Lorg/json/e; or its super classes (declaration of 'org.json.e' appears in /data/app/~~dXfc0orwEajJECAG2s1hEg==/com.discoverpilgrim-UwOxwAIQKiGoBUKhGkdoOg==/base.apk!classes4.dex)
at com.microsoft.appcenter.ingestion.models.json.DefaultLogSerializer.writeLog(DefaultLogSerializer.java:35)
at com.microsoft.appcenter.ingestion.models.json.DefaultLogSerializer.serializeLog(DefaultLogSerializer.java:58)
at com.microsoft.appcenter.persistence.DatabasePersistence.putLog(DatabasePersistence.java:269)
at com.microsoft.appcenter.channel.DefaultChannel.enqueue(DefaultChannel.java:679)
at com.microsoft.appcenter.AppCenter.sendStartServiceLog(AppCenter.java:1047)
at com.microsoft.appcenter.AppCenter.finishStartServices(AppCenter.java:1032)
at com.microsoft.appcenter.AppCenter.access$600(AppCenter.java:61)
at com.microsoft.appcenter.AppCenter$7.run(AppCenter.java:935)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:263)
at android.os.HandlerThread.run(HandlerThread.java:67)

Mahimsharma commented

+1. having the exact same issue

ajiehatajie commented

+1. having the exact same issue

Mahimsharma commented

"appcenter": "4.3.0",
"appcenter-analytics": "4.3.0",
"appcenter-crashes": "4.3.0",

@ajiehatajie Removing the above-mentioned dependencies solved the issue for me. They were of no use because we have Firebase Crashlytics and Analytics. The Code Push works fine as usual without these dependencies. I was not able to find the actual fix, but this workaround did the job!

  • 👍1
microsoft-github-policy-service commented

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

AnatolyPristensky commented

Closing due to absence of activity.