[英]Crash reported in play console for incorrect app version
I am facing a strange issue as below:我面临一个奇怪的问题如下:
I have an very old version of my app say version 7.x on end user devices.我在最终用户设备上有一个非常旧的应用程序版本,比如 7.x 版。 Right now I have published version 16.X in production, not containing any code but just a empty hollow app(no code at all).
现在我已经在生产中发布了 16.X 版本,不包含任何代码,而只是一个空的空心应用程序(根本没有代码)。
But somehow when I published this new version to play store I am seeing crash with a stack-trace of my 7.X version logged against my new 16.X version.但不知何故,当我将这个新版本发布到 Play 商店时,我看到我的 7.X 版本的堆栈跟踪与我的新 16.X 版本记录的崩溃。 The 7.X version of my app is no longer available in my play console.
我的应用程序的 7.X 版本在我的游戏控制台中不再可用。
Stack Trace for issue is as below:问题的堆栈跟踪如下:
java.lang.RuntimeException:
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:4519)
at android.app.ActivityThread.access$1500 (ActivityThread.java:144)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1339)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:135)
at android.app.ActivityThread.main (ActivityThread.java:5219)
at java.lang.reflect.Method.invoke (Native Method)
at java.lang.reflect.Method.invoke (Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:693)
Caused by: java.lang.IllegalArgumentException:
at android.content.ContentResolver.bulkInsert (ContentResolver.java:1264)
at com.b.a.a.b.a (SourceFile:168)
at com.abc.pqr.database.e.e (SourceFile:251)
at com.abc..DiscoverApplication.a (SourceFile:93)
at com.abc..DiscoverApplication.onCreate (SourceFile:84)
at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1011)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:4516)
Is this a known issue in play console or there is some issue while upgrading my app from 7.X to 16.X ?这是游戏控制台中的已知问题还是将我的应用程序从 7.X 升级到 16.X 时出现问题?
Actually, the first thing why crash log for your first version?实际上,首先为什么要为您的第一个版本创建崩溃日志? if your old version updated with the latest one but what about who already not updated your app means possible cash also play store log crash because of old version user.
如果您的旧版本更新为最新版本,但谁还没有更新您的应用程序意味着可能现金也会因为旧版本用户而导致商店日志崩溃。
Also, possible cash is you have not any codding but sometimes memory leak problem generates crash when your app in background for too much time.此外,可能的现金是您没有任何编码,但有时当您的应用程序在后台运行时间过长时,内存泄漏问题会导致崩溃。
Batter thing is integrating some crash logs like firebase
or fabric
crash analytics which will give full information. Batter 正在集成一些崩溃日志,如
firebase
或fabric
崩溃分析,它们将提供完整的信息。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.