JumpyJet Sample Crashes on Android Device When Built in Debug

Release Type: Official Release

Version: 4.1.0.1948

Platform(s): Android

Describe the bug
The JumpyJet sample will crash on an Android device after running for a period of time in Debug mode. While no exception is thrown, the following error appears in the log.

[SDLThread] type=1400 audit(0.0:1589): avc: denied { lock } for path="/system/usr/share/zoneinfo/tzdata" dev="mmcblk0p60" ino=6834 scontext=u:r:untrusted_app:s0:c150,c257,c512,c768 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

[SDLThread] type=1400 audit(0.0:1591): avc: denied { lock } for path="/system/usr/share/zoneinfo/tzdata" dev="mmcblk0p60" ino=6834 scontext=u:r:untrusted_app:s0:c150,c257,c512,c768 tcontext=u:object_r:system_file:s0 tclass=file permissive=0

[libc] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x72fec00000 in tid 1484 (SDLThread), pid 1442 (SDLActivity)

This issue has been reported by various users on the Stride Discord and may also be replicable in other Android projects. This issue cannot be reproduced in Release mode.

To Reproduce
Steps to reproduce the behavior:

1. Create a new JumpyJet project for Android with Stride 4.1.0.x
2. Build the sample for Android with the default Debug and Any CPU configuration
3. Deploy and run the sample on an Android device (it may take up to a minute to initialize)
4. Allow the sample to run on the device for up to a minute for the crash to occur

Note: You can play the game or simply leave it running at the Main Menu to reproduce this error

Start with the JumpyJet sample built for Android in Stride 4.1.0.x using the default Debug and Any CPU configuration, and run it on a device while collecting the SDLThread log. Compare the failing Debug run with Release mode, focusing on the zoneinfo access denial and SIGSEGV; done means the sample runs without crashing on the stated reproduction steps.