Android 签名应用程序崩溃。签署前已工作

发布于 2024-12-13 14:23:45 字数 1698 浏览 0 评论 0原文

正如标题所示,我最近签署了我的应用程序,但发现一旦我签署了我的应用程序,它就变得无法使用。在我签字之前一直工作得很好,从来没有遇到过这样的问题。然后,一旦统一闪屏显示完毕,它就开始自杀(可能在这期间我不太确定)。 即使我制作了一个调试签名版本,它也会做同样的事情......在 Unity 闪屏期间自杀。 我对 logcat 非常缺乏经验,但这些是在登录参考/启动我的应用程序时发现的唯一错误。

注意:使用Unity Android。

任何帮助将不胜感激,因为这两天我的头撞在桌子上。 提前致谢。

11-06 00:57:52.585 E/Unity   (31921): Error joining threads: 3
11-06 00:57:52.585 E/Unity   (31921):  
11-06 00:57:52.585 E/Unity   (31921): (Filename: /Applications/buildAgent/work/842f9557127e852/Runtime/Threads/Thread.cpp Line: 367)
11-06 00:57:52.585 E/Unity   (31921): 
11-06 00:57:52.815 I/DEBUG   (30096): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-06 00:57:52.815 I/DEBUG   (30096): Build fingerprint: 'samsung/GT-I9100/GT-I9100:2.3.3/GINGERBREAD/XWKG1:user/release-keys'




11-06 00:57:59.130 E/lights  ( 2698): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 57
11-06 00:57:59.150 E/lights  ( 2698): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 54
11-06 00:57:59.150 E/InputDispatcher( 2698): channel '4083e180 com.BraydenWale.NoFlyZone/com.unity3d.player.UnityPlayerActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x8
11-06 00:57:59.150 E/InputDispatcher( 2698): channel '4083e180 com.BraydenWale.NoFlyZone/com.unity3d.player.UnityPlayerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
11-06 00:57:59.150 I/ActivityManager( 2698): Process com.BraydenWale.NoFlyZone (pid 31921) has died.
11-06 00:57:59.150 I/WindowManager( 2698): WIN DEATH: Window{40854bf0 SurfaceView paused=false}
11-06 00:57:59.155 D/Zygote  ( 2587): Process 31921 terminated by signal (11)

as the title says i've recently signed my app but found once i signed my app that it then became unusable. Worked perfectly fine up until i signed it, never had a single issue like this. Then it started killing itself as soon as the unity splashscreen finished displaying(possibly during it i'm not too sure).
Even if i make a debug signed version it does the same thing...killing itself during the Unity splashscreen.
I'm very in-experienced with logcat but these were the only errors to be found within the log in reference/around launching my app.

Note: Using Unity Android.

Any help would be appreciated as it's been two days of bashing my head against a desk.
Thanks in advance.

11-06 00:57:52.585 E/Unity   (31921): Error joining threads: 3
11-06 00:57:52.585 E/Unity   (31921):  
11-06 00:57:52.585 E/Unity   (31921): (Filename: /Applications/buildAgent/work/842f9557127e852/Runtime/Threads/Thread.cpp Line: 367)
11-06 00:57:52.585 E/Unity   (31921): 
11-06 00:57:52.815 I/DEBUG   (30096): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-06 00:57:52.815 I/DEBUG   (30096): Build fingerprint: 'samsung/GT-I9100/GT-I9100:2.3.3/GINGERBREAD/XWKG1:user/release-keys'




11-06 00:57:59.130 E/lights  ( 2698): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 57
11-06 00:57:59.150 E/lights  ( 2698): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 54
11-06 00:57:59.150 E/InputDispatcher( 2698): channel '4083e180 com.BraydenWale.NoFlyZone/com.unity3d.player.UnityPlayerActivity (server)' ~ Consumer closed input channel or an error occurred.  events=0x8
11-06 00:57:59.150 E/InputDispatcher( 2698): channel '4083e180 com.BraydenWale.NoFlyZone/com.unity3d.player.UnityPlayerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
11-06 00:57:59.150 I/ActivityManager( 2698): Process com.BraydenWale.NoFlyZone (pid 31921) has died.
11-06 00:57:59.150 I/WindowManager( 2698): WIN DEATH: Window{40854bf0 SurfaceView paused=false}
11-06 00:57:59.155 D/Zygote  ( 2587): Process 31921 terminated by signal (11)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

情话墙 2024-12-20 14:23:45

您是否使用 proguard 来混淆您的代码?签名的应用程序在构建过程中会自动混淆,但未签名的调试应用程序不会。某些代码不应被混淆,例如本机代码引用的代码。

这是有关 progaurd 的文档的链接,希望对您有所帮助。

Did you use proguard to obfuscates your code? Signed app is obfuscated automatically during the building process but unsigned debug app won't. Some code should not be obfuscated, such as those referenced by native code.

Here is the link to the documentation about progaurd, hope it helps.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文