应用在Android设备上崩溃,使用Unity编辑器构建的游戏2020.3.33 LTS

发布于 2025-01-23 07:58:55 字数 2143 浏览 0 评论 0原文

我正在从事过去两年的项目。我开始使用2019.4。几个月前,我的电脑由于热量而破裂,所以我不得不拿一台新电脑。我安装了Unity 2.4.5Hub和2020.3.28(2020.3.33)LTS发布以继续该项目。我拥有API 30 SDK,并支持Gradle以及JDK和NDK。

App Build在Editor 2019.4和App都可以在任何设备上运行良好。 现在,当我尝试在任何Android设备上运行时,它就会在Unity Splash屏幕上崩溃。我从Google控制台上提到了一些日志猫Bellow:

stack Trace

com.xyz的本地崩溃

。 过程:com.xyz.amgame,pid:19127 java.lang.error:*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ** **** 版本“ 2020.3.33F1(915A7AF8B0D5)',构建类型“发行”,脚本脚本后端'il2CPP',CPU'arm64-v8a' 构建指纹:'DOCOMO/SH-01L/SH-01L:9/S1240/02.00.05:用户/Release-Keys'

修订:'0''
Abi:'ARM64'
时间戳:2022-04-19 02:33:55-0700 PID:19127,TID:19560,名称:Unitymain>>> com.xyz.amgame<<<< UID:10274
信号11(sigsegv),代码1(segv_maperr),故障addr 0x7e31804ff0 X0 0000007E1FCF4EE8 X1 0000007E1CC20E20 X2 0000007E1CC20E20 X3 0000007E3180509C X4 0000007E1CC21100 X5 0000000000000004 x6 0000007E31808F59 x7 0800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000。 X8 0000000000000A79 X9 6DB6DB6DB6DB6DB7 X10 0000000000000038 x11 0000007E1D75B498 X12 0000000000002373 x13 0000000000000537 x14 0000000000000300 x15 aaaaaaaaaaaaaaaaaaaab X16 0000007ED06AF270 X17 0000007ED05BE430 X18 0000000000000000000001 x19 0000007EE1FD8B850 X20 0000007E31805088 X21 0000007E3180509D X22 0000000000000038 X23 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF X24 000000000000017F X25 0000000000000000BF X26 0000007E1FD8E218 X27 0000007E1D75B498 X28 0000007E1FDAE000 X29 0000007E31805020 SP 0000007E31805020 LR 0000007E1EA289A8 PC 0000007EE1EA28818 backtrace: #00 PC 00000000562818/DATA/App/com.xyz.amgame-gymaxwfe3awnpqfoqfoqwdg1q==/lib/arm64/arm64/libil2cpp.so(buildIdId:95f042f042fcd17ee217ee217ee217a642223aae5555555559e79eef 18

(本机方法) 在libil2cpp.0x5629a4(本机方法) 在libil2cpp.0x543790(本机方法) 在libil2cpp.0x515a78(本机方法) 在libil2cpp.0x516ac0(本机方法)

I am working on a project from last 2 years. I started working with 2019.4. Few months ago my PC broke down because of heat so i had to take a new one. I installed unity 2.4.5hub and 2020.3.28(later 2020.3.33) LTS releases to continue the project. I have API 30 SDK and supported gradle as well as JDK and NDK.

The app build were success with editor 2019.4 and APP were working fine with any devices.
The issue is now when i am trying to run on any android device it crashes just on unity splash screen. I got some log cat from google Console mentioned bellow:

Stack trace

Native crash of com.XYZ.AMGame

FATAL EXCEPTION: UnityMain
Process: com.XYZ.AMGame, PID: 19127
java.lang.Error: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Version '2020.3.33f1 (915a7af8b0d5)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'arm64-v8a'
Build fingerprint: 'DOCOMO/SH-01L/SH-01L:9/S1240/02.00.05:user/release-keys'

Revision: '0'
ABI: 'arm64'
Timestamp: 2022-04-19 02:33:55-0700
pid: 19127, tid: 19560, name: UnityMain >>> com.XYZ.AMGame<<<
uid: 10274
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7e31804ff0
x0 0000007e1fcf4ee8 x1 0000007e1cc20e20 x2 0000007e1cc20e20 x3 0000007e3180509c
x4 0000007e1cc21100 x5 0000000000000004 x6 0000007e31808f59 x7 0800000000000000
x8 0000000000000a79 x9 6db6db6db6db6db7 x10 0000000000000038 x11 0000007e1d75b498
x12 0000000000002373 x13 0000000000000537 x14 0000000000000300 x15 aaaaaaaaaaaaaaab
x16 0000007ed06af270 x17 0000007ed05be430 x18 0000000000000001 x19 0000007e1fd8b850
x20 0000007e31805088 x21 0000007e3180509d x22 0000000000000038 x23 ffffffffffffffff
x24 000000000000017f x25 00000000000000bf x26 0000007e1fd8e218 x27 0000007e1d75b498
x28 0000007e1fdae000 x29 0000007e31805020
sp 0000007e31805020 lr 0000007e1ea289a8 pc 0000007e1ea28818
backtrace:
#00 pc 0000000000562818 /data/app/com.XYZ.AMGame-gymaxWfE3AwNPqfOQwDg1Q==/lib/arm64/libil2cpp.so (BuildId: 95f042fcd17ee217a64223a559ce49e73fae8e1a)

at libil2cpp.0x562818(Native Method)
at libil2cpp.0x5629a4(Native Method)
at libil2cpp.0x543790(Native Method)
at libil2cpp.0x515a78(Native Method)
at libil2cpp.0x516ac0(Native Method)

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

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

发布评论

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

评论(1

緦唸λ蓇 2025-01-30 07:58:55

自从Unity 2020.3.26到2020.3.33以来,我已经开始(看起来像)同样的崩溃。
为ARM64建造(不包括ARMV7)可以修复它,但是我在发货游戏中需要ARMV7支持。
这是在APK构建中进行测试的;构建到AAB可能还可以修复它,但这将很难测试。

I've started getting (what looks like) this same crash since updating from Unity 2020.3.26 to 2020.3.33.
Building for ARM64 (excluding ARMv7) fixes it, but I need ARMv7 support in my shipped game.
This in an APK build for testing; building to an AAB might also fix it, but that's going to be harder to test.

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