-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Unity 2021 + Android API 30 Smoke test crash #719
Comments
I've tried if the app crashes with just plain build, without Sentry package included and indeed it does, so this has nothing to do with Sentry: https://github.com/getsentry/sentry-unity/runs/6475554309?check_suite_focus=true |
Unity 2020 Android API 30 build is rather flaky recently too: https://github.com/getsentry/sentry-unity/runs/6817497012?check_suite_focus=true |
Before anything I think it's a good start to make those logs more readable. Logcat has a limit of text that can be output per line, so the event is getting cut on the log
I propose a solution for this case by formatting the json and splitting each line of it into a ne log, examle:
What do you thinks think? |
That would apply to logs like when we're printing the whole event? |
I've recently tried enabling this and it still fails. I think, considering I've previously tried running the same app without Sentry included at all, we can assume it's a Unity issue and close this. I'll leave a comment in the code pointing to this issue for explanation and if we want to pursue this further at some time down the road. Latest run in CI: https://github.com/getsentry/sentry-unity/actions/runs/3302480440/jobs/5449627380 error10-22 08:34:42.848 2325 2349 E CRASH : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 10-22 08:34:42.849 2325 2349 E CRASH : Version '2022.1.20f1 (01d83b40d570)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'x86_64' 10-22 08:34:42.849 2325 2349 E CRASH : Build fingerprint: 'Android/sdk_phone_x86_64/generic_x86_64:11/RSR1.210722.012/7758210:userdebug/test-keys' 10-22 08:34:42.849 2325 2349 E CRASH : Revision: '0' 10-22 08:34:42.849 2325 2349 E CRASH : ABI: 'x86_64' 10-22 08:34:42.849 2325 2349 E CRASH : Timestamp: 2022-10-22 08:34:42+0000 10-22 08:34:42.849 2325 2349 E CRASH : pid: 2325, tid: 2349, name: UnityMain >>> com.DefaultCompany.IntegrationTest <<< 10-22 08:34:42.849 2325 2349 E CRASH : uid: 10130 10-22 08:34:42.849 2325 2349 E CRASH : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x880000 10-22 08:34:42.849 2325 2349 E CRASH : rax 0000000000880000 rbx 00007053f0b3ad90 rcx 0000000000000000 rdx 0000000000010000 10-22 08:34:42.849 2325 2349 E CRASH : r8 00007053f0000000 r9 0000000000000006 r10 00000000004c5158 r11 00000000000000e3 10-22 08:34:42.850 2325 2349 E CRASH : r12 00007053f0a71188 r13 000070547f5f0fc6 r14 0000000000000000 r15 0000000000010000 10-22 08:34:42.850 2325 2349 E CRASH : rdi 0000000000880000 rsi 0000000000000000 10-22 08:34:42.850 2325 2349 E CRASH : rbp 00007053f0b3ac10 rsp 000070547c11a878 rip 00007057698d567a 10-22 08:34:42.850 2325 2349 E CRASH : backtrace: 10-22 08:34:42.850 2325 2349 E CRASH : #00 pc 000000000005067a /apex/com.android.runtime/lib64/bionic/libc.so (gwp_asan::compression::pack(unsigned long const*, unsigned long, unsigned char*, unsigned long)+122) (BuildId: 3707c39fc397eeaa328142d90b50a973) 10-22 08:34:42.850 2325 2349 E CRASH : #01 pc 0000000000098b27 [anon:.bss] 10-22 08:34:42.850 2382 2382 W app_process: Unexpected CPU variant for X86 using defaults: x86_64 |
After splitting the Android smoke test build into a separate job and running it via the integration-test scripts (i.e. create empty project, build, add unity, build, test) in PR #686, the "smoke-test" part of the test now consistently crashes the app in CI (not reproducible locally yet) when run a Unity 2021 build on Android API 30 x86 emulator - for example, see this run: https://github.com/getsentry/sentry-unity/runs/6227149023?check_suite_focus=true
For now the test has been disabled to unblock the PR, because it is not deemed to be caused by the changes in the PR but to be an existing issue, because that PR doesn't change anything about the actual package, just the test execution.
Note: I've also tried to update the CI so that it doesn't do the first build without sentry, to make sure the error isn't caused by the second build and it isn't - that app still crashes even with a single build, with unity included from the beginning.
The text was updated successfully, but these errors were encountered: