os-issue-tracker icon indicating copy to clipboard operation
os-issue-tracker copied to clipboard

Call of Duty Warzone launches, but crashes during loading screen

Open FID02 opened this issue 1 year ago • 0 comments

Issue description

The game Call of Duty Warzone crashes during its loading screen, a few seconds after it is launched.
It does not show a message about a rooted or disallowed phone, but simply crashes. In the app log after the crash, there is no mention of root, integrity or safetynet. https://play.google.com/store/apps/details?id=com.activision.callofduty.warzone

Several users have reported this issue in the community chat rooms, but I cannot find that an issue has been filed before now.

I am unable to reproduce the issue on stock PixelOS, on a Pixel 6a.

Note that, on the Pixel 6a running stock, I had to install the game via Aurora Store, as the Play Store disallows the install because the Pixel 6a is not supported by the game. Not sure if this is relevant or impacts testing. On Pixel 8 running GrapheneOS, the game can be installed from the Play Store without issues or warnings.

Tested on:

Pixel 8. GrapheneOS 2024050300. Play Services 24.17.15.

Pixel 6a. PixelOS AP1A.240405.002. Play Services 24.16.16.

Workarounds tested

  • Allowed Play Store access to Android/obb folder prior to install

  • Enabled exploit protection compatibility mode for the app

  • Enabled secure app spawning, disabled exploit protection compatibility mode for the app, and then rebooted

App log taken after the crash

COD Warzone log 99026a4d561f.txt

Crash log

type: crash
osVersion: google/shiba/shiba:14/AP1A.240405.002.B1/2024050300:user/release-keys
package: com.activision.callofduty.warzone:1101
process: com.activision.callofduty.warzone
processUptime: 0 + 0 ms
installer: com.android.vending

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000013

backtrace:
      #00 pc 0000000002543cd8  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #01 pc 0000000002b7ca38  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #02 pc 0000000002b7f3c8  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #03 pc 00000000019475a8  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #04 pc 00000000013c1240  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #05 pc 0000000002545004  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #06 pc 0000000002543710  /data/app/~~odKa9m4dZvFelfGL37jz1A==/com.activision.callofduty.warzone-3LSZyYF3Ti_gBuHgxZbveQ==/split_config.arm64_v8a.apk!libgame.so (offset 0x6b000) (BuildId: dddcaacd76ca76d5c9e9a8951d8b35e6)
      #07 pc 00000000000d5e6c  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: ed92f960e1dd1590bc7d2b8573224779)
      #08 pc 0000000000069a64  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: ed92f960e1dd1590bc7d2b8573224779)

I can send system logs by DM if needed.

FID02 avatar May 05 '24 14:05 FID02