App crashed in Google Pre-launch report - PackageStateChangedService crash

Solar2D Android
#1

Using 3274 I just submitted a new build and it failed pre-launch testing on a Galaxy s7.  The crash report is

\*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* \*\*\* Build fingerprint: 'samsung/hero2ltexx/hero2lte:6.0.1/MMB29K/G935FXXU1APB6:user/release-keys' Revision: '9' ABI: 'arm' pid: 16717, tid: 17324, name: VungleAsyncMain \>\>\> com.spheregamestudios.designercity2 \<\<\< signal 11 (SIGSEGV), code 2 (SEGV\_ACCERR), fault addr 0x356a5944 r0 70b1d784 r1 13156ee0 r2 00262add r3 f12e2070 r4 00262add r5 13156ee0 r6 70b1cdd0 r7 713389d0 r8 1326b4f0 r9 d4213a00 sl dbac14e8 fp dbac145c ip f12e2070 sp dbac13e0 lr 747e570d pc f4600ae8 cpsr 00070030 backtrace: #00 pc 000eaae8 /system/lib/libart.so (art\_quick\_imt\_conflict\_trampoline+7) #01 pc 02f5470b /system/framework/arm/boot.oat (offset 0x2f26000)

Attached is the full logcat from Google (in the hope that it helps) but I believe this is the cause of the crash…

04-25 03:47:09.286: W/ActivityManager(3410): Native crash 04-25 03:47:09.286: W/ActivityManager(3410): Native crash: Segmentation fault 04-25 03:47:09.296: W/ActivityManager(3410): Scheduling restart of crashed service com.spheregamestudios.designercity2/shared.google.play.services.base.PackageStateChangedService in 1000ms
#2

This error happens fairly frequently the last time I checked. I would suggest you submit it again and it will probably not occur a second time. That being said hopefully it will be fixed soon. If you a search for that exact same error in the forums you will find multiple threads on the subject. I haven’t kept up to date on those threads, but maybe you can add your logs to the list.

#3

Hi agramonte… I know we are all suffering.  I am simply posting a full logcat here so Corona can hopefully use it to help fix the errors we are all seeing as this is with a very recent daily build.

#4

This error happens fairly frequently the last time I checked. I would suggest you submit it again and it will probably not occur a second time. That being said hopefully it will be fixed soon. If you a search for that exact same error in the forums you will find multiple threads on the subject. I haven’t kept up to date on those threads, but maybe you can add your logs to the list.

#5

Hi agramonte… I know we are all suffering.  I am simply posting a full logcat here so Corona can hopefully use it to help fix the errors we are all seeing as this is with a very recent daily build.