GLBasic forum

Main forum => Bug Reports => Topic started by: MrPlow on 2017-Aug-24

Title: Android Crash Bugs
Post by: MrPlow on 2017-Aug-24
Hi Guys

Anyone know what this crash report could point to?

  native: pc 000000000034904e  /system/lib/libart.so (_ZN3art22CountStackDepthVisitor10VisitFrameEv+25)
  native: pc 000000000033d571  /system/lib/libart.so (_ZN3art12StackVisitor9WalkStackEb+224)
  native: pc 0000000000351e25  /system/lib/libart.so (_ZNK3art6Thread24CreateInternalStackTraceILb0EEEP8_jobjectRKNS_33ScopedObjectAccessAlreadyRunnableE+60)
  native: pc 00000000002dc8f9  /system/lib/libart.so (_ZN3artL32Throwable_nativeFillInStackTraceEP7_JNIEnvP7_jclass+20)
  native: pc 0000000002f7fc0d  /system/framework/arm/boot.oat

There are a lot of them for one particular app - what is libart.so for anyhow?

Thks
Title: Re: Android Crash Bugs
Post by: spacefractal on 2017-Aug-25
I'm should update using newer sdk, howovert that will break the ads system.... Not sure what happens yet without a debugging.... Something that is much much better on ios.
Title: Re: Android Crash Bugs
Post by: spacefractal on 2017-Aug-25
what im can see is im might have used a old version of the zipalign tool, which was still set to version 21.1.2, but should have been 25.0.2 of the build tools (or that is the newest version you can see in platform\android\android-sdk-windows\build-tools). Im might have updated to a a newer version, but not released it.

try using that file and put it in Compiler\platform\android\bin.

You can also try to set android:debuggable="true" to android:debuggable="false" in the manifest.xml.
Title: Re: Android Crash Bugs
Post by: MrPlow on 2017-Aug-27
Hi

Version is 19.1.0 or something for that folder