Game crashing when downloaded from PlayStore

Hello,

I recently uploaded my game on the PlayStore and I face a weird issue. When I install my game via USB using the BAT install script all works fine but when I install it from the PlayStore, I see the splashcreen and the game crashes with this error report:

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'asus/WW_Phone/ASUS_X007D:6.0.1/MMB29M/13.0.4.76-20161121:/release-keys'
Revision: '0'
ABI: 'arm'
pid: 7989, tid: 8004, name: Thread-910  >>> com.linkpulsion.RollTheBall <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
    r0 00000000  r1 dd07cf08  r2 00004001  r3 00000001
    r4 e205bb44  r5 eb92e3c0  r6 e205bb3c  r7 dd07cf08
    r8 00000001  r9 dd187780  sl 0000003f  fp dd07cf00
    ip 00001f44  sp dd07cc08  lr dec536d4  pc dec53c48  cpsr 400d0010

backtrace:
    #00 pc 015b6c48  /data/app/com.linkpulsion.RollTheBall-1/lib/arm/libUE4.so (_ZN13FZipUnionFile12AddPatchFileE10TSharedPtrI18FFileHandleAndroidL7ESPMode0EE+32)
    #01 pc 015b66d0  /data/app/com.linkpulsion.RollTheBall-1/lib/arm/libUE4.so (_ZN20FAndroidPlatformFile8MountOBBEPKw+100)
    #02 pc 015b5494  /data/app/com.linkpulsion.RollTheBall-1/lib/arm/libUE4.so (_ZN20FAndroidPlatformFile10InitializeEP13IPlatformFilePKw+1452)
    #03 pc 01572b14  /data/app/com.linkpulsion.RollTheBall-1/lib/arm/libUE4.so (_Z11AndroidMainP11android_app+2708)
    #04 pc 0157638c  /data/app/com.linkpulsion.RollTheBall-1/lib/arm/libUE4.so (android_main+120)
    #05 pc 0158a018  /data/app/com.linkpulsion.RollTheBall-1/lib/arm/libUE4.so
    #06 pc 00041823  /system/lib/libc.so (_ZL15__pthread_startPv+30)
    #07 pc 00019285  /system/lib/libc.so (__start_thread+6)

For information: I uploaded both APK and OBB, the OBB verification on first start/update is disabled.

Cheers.

Cypaubr,

  • Is this happening when you install and launch your project outside of Play for testing?
  • Is this only happening on one device?
  • Could you please upload the full output logs from the device as a .txt file?

Thank you!

Hello ,

The error occurs only on the PlayStore downloaded version. If I install it from the BAT script it works fine.
It happened on all devices I tested with (3 with differenc proc. arch).
Here is the full log from the launch to the crash: [link text][1].

I also checked if the downloaded OBB was right with my file manager and all seems right.

Cheers.

126642-logcat.txt (10.2 KB)

Cypaubr,

I was able to download your game from the playstore and verified that it is working on a Nexus5 but it is not working on a Shield Tablet.

  • Are you able to get this to happen on any other project?
  • Is there anything specific that you packaged this project out with that you didn’t with another project?
  • Does this happen in 4.15 with your project? If you were to create a copy, package it out the same way and upload it to the playstore?

We need some comparison to try and narrow down what’s going on for this issue.

I can see in the logs that you provided that the screen is freezing for a certain amount of ms, which is what i’m seeing in my logs too however, I also see this within my logs:

02-20 13:15:17.965: W/WindowManager(696): Failed looking up window
02-20 13:15:17.965: W/WindowManager(696): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@6989646 does not exist
02-20 13:15:17.965: W/WindowManager(696): 	at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8783)
02-20 13:15:17.965: W/WindowManager(696): 	at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:8774)
02-20 13:15:17.965: W/WindowManager(696): 	at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1222)
02-20 13:15:17.965: W/WindowManager(696): 	at android.os.BinderProxy.sendDeathNotice(Binder.java:558)

Were the logs that you uploaded a a .txt file the full logs from monitor.bat?

Thanks!

Hey Cypaubr,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you!