Skip to main content
jaywingate
New Participant
June 7, 2023

Android SDK 12l causing crashing for development builds

Recently I've been trying to update my project's android api from 29 to 32, so it can comply with the new requirements for Quest 2.

After the update attempting to launch a non-distribution build causes the following crash during the initial splash screen:

 

Spoiler
06-07 16:16:54.995 29239 29239 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
06-07 16:16:54.995 29239 29239 F DEBUG : Cause: null pointer dereference
06-07 16:16:54.995 29239 29239 F DEBUG : x0 0000007c83885ab0 x1 0000007c8a6094c0 x2 0000007c8a6092e4 x3 0000007c8a6092f0
06-07 16:16:54.995 29239 29239 F DEBUG : x4 0000000000000001 x5 0000000000000001 x6 0000007da5d9b280 x7 0000000000000001
06-07 16:16:54.995 29239 29239 F DEBUG : x8 0000000000000000 x9 e5d9a1578e8c507b x10 000000000000722d x11 000000000000722d
06-07 16:16:54.995 29239 29239 F DEBUG : x12 000000000004c000 x13 0f9160e40d945523 x14 0000000000000001 x15 0000000000000000
06-07 16:16:54.995 29239 29239 F DEBUG : x16 0000007c83799190 x17 0000007d8b7140c0 x18 0000007c89dc0000 x19 0000007c83885aa0
06-07 16:16:54.995 29239 29239 F DEBUG : x20 0000007c83885ab0 x21 0000007c83858130 x22 0000007c8b034a80 x23 0000000000000000
06-07 16:16:54.995 29239 29239 F DEBUG : x24 0000007c8a6094c0 x25 0000000000000030 x26 0000007c838580e8 x27 0000007c8a60e000
06-07 16:16:54.995 29239 29239 F DEBUG : x28 0000000000000038 x29 0000007c8a609390
06-07 16:16:54.995 29239 29239 F DEBUG : lr 0000007c7dc5a9c8 sp 0000007c8a609130 pc 0000007c7dc5d43c pst 0000000060001000
06-07 16:16:54.995 29239 29239 F DEBUG : backtrace:
06-07 16:16:54.995 29239 29239 F DEBUG : #00 pc 000000000965a43c /data/app/~~57KirAbmQeqCJ5_LgmuvEQ==/com.***.******-0BMYONjMB5VHuThMvsiV3A==/lib/arm64/libUE4.so (FZipUnionFile::AddPatchFile(TSharedPtr<FFileHandleAndroid, (ESPMode)1>)+64) (BuildId: fdcad66b69c55c6a31b6a1875b4d0d0e2d07a926)
06-07 16:16:54.995 29239 29239 F DEBUG : #01 pc 00000000096579c4 /data/app/~~57KirAbmQeqCJ5_LgmuvEQ==/com.***.******-0BMYONjMB5VHuThMvsiV3A==/lib/arm64/libUE4.so (FAndroidPlatformFile::Initialize(IPlatformFile*, char16_t const*)+3812) (BuildId: fdcad66b69c55c6a31b6a1875b4d0d0e2d07a926)
06-07 16:16:54.995 29239 29239 F DEBUG : #02 pc 00000000079c35b4 /data/app/~~57KirAbmQeqCJ5_LgmuvEQ==/com.***.******-0BMYONjMB5VHuThMvsiV3A==/lib/arm64/libUE4.so (AndroidMain(android_app*)+3244) (BuildId: fdcad66b69c55c6a31b6a1875b4d0d0e2d07a926)
06-07 16:16:54.995 29239 29239 F DEBUG : #03 pc 00000000079d3ac0 /data/app/~~57KirAbmQeqCJ5_LgmuvEQ==/com.***.******-0BMYONjMB5VHuThMvsiV3A==/lib/arm64/libUE4.so (android_main+148) (BuildId: fdcad66b69c55c6a31b6a1875b4d0d0e2d07a926)
06-07 16:16:54.995 29239 29239 F DEBUG : #04 pc 00000000079fedec /data/app/~~57KirAbmQeqCJ5_LgmuvEQ==/com.***.******-0BMYONjMB5VHuThMvsiV3A==/lib/arm64/libUE4.so (BuildId: fdcad66b69c55c6a31b6a1875b4d0d0e2d07a926)
06-07 16:16:54.995 29239 29239 F DEBUG : #05 pc 00000000000dddec /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+132) (BuildId: d7676abcaa144b1eeebd8fdc21061019)
06-07 16:16:54.995 29239 29239 F DEBUG : #06 pc 000000000008a02c /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: d7676abcaa144b1eeebd8fdc21061019)
06-07 16:16:55.019 29183 29229 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 29229 (GameThread), pid 29183 (*****)
06-07 16:16:55.021 1096 1221 I BootReceiver: Copying /data/tombstones/tombstone_12 to DropBox (SYSTEM_TOMBSTONE)

 

Initially I thought this was down to lack of permissions. MANAGE_EXTERNAL_STORAGE was added in api 30 without which access to $Storage/obb, where non-distribution obbs are stored on device, would have been denied. However adding this to the extra permissions and ensuring it has been requested on game start has not fixed the issue. Below are the android packaging settings. 

I also tried editing the automation script to have the obbs appear in the $storage/android/obb folder, while this did fix the initial crashing it lead to other side effects (such as no logs being recorded and instability) & ultimately feels like a step in the wrong direction.

Has there been anyone else run into this issue? If so did you find a solution? 
Any suggestions or troubleshooting thoughts would be deeply appreciated.

    This topic has been closed for replies.

    6 replies

    rorythomson713025
    New Participant
    June 8, 2023

    Having the same issue myself, but had to park it to prioritize something else. 

    I don't remember if I attempted a distribution build, but my non-distribution builds were hitting an assert and failing to load the obb file also. Can you confirm that your distribution builds are working as expected and that it's just the development ones that have this issue?

    jaywingateAuthor
    New Participant
    June 8, 2023

    Glad to hear it's not just effecting our project! On further inspection allowing distribution did not fix the issue, does appear to be a general issue with non-shipping builds.

    We've found a temporary work around by editing the build scripts. The edits mentioned in the post made to AndroidPlatform.Automation to add "Android/" before the obb directory to the install bat files work for avoiding the crash. I figure this was not an issue before due to looser permissions in api 10 and earlier. 
    The piece that was missed for re-enabling logging was found here , UEDeployAndroid.cs will disallow External files if you are not distribution, removing this check appears to allow logs and saves to occur in the correct places for non distribution builds.
      trandana
      New Participant
      August 12, 2023

      Curious which line in particular you had to change in order to avoid the crash? We are having the same issue on 4.27.
      I see inside AndroidPlatform.Automation:
      private const string TargetAndroidLocation = "obb/";

      Is that the line where you changed to "Android/obb/"?
      My attempts avoid the crash now, but get an infinite loading screen

      Thanks!

      mohamedsamy150253
      New Participant
      August 22, 2023

      Hello I fix 32 crashing with ue4.27?

      JayDead1
      Participant
      August 29, 2023

      I've experienced a similar issue on the Oculus 4.27 fork.

      Used to quickly build test versions using the project launcher to check things on my Quest, but now when I do, it I wont get further than the splash screen.

       

      The steps that caused this misery:

      Target SDK 29->32

      Extra Tags for UE4 GameActivity added:   android:exported="true"

       

      I really hope there's a solution for this issue as it's making my testing much more cumbersome. Cheers!

      CritterHP5
      CritterHP5
      Inspiring
      December 13, 2023

      I was using the launcher version of 4.27 and was experiencing crash on launch (three white dots) with development and shipping builds. For some reason turning on "Package Game Data inside APK" prevented it from crashing.

      Also, I possibly had a similar issue once with a different project where in Shipping/Distribution builds it kept crashing exactly after the 4th or 5th relaunch and I discovered that if I used the oculus build it did not crash on relaunch.

      Terms & ConditionsAccessibility statement