SDKBOX crash after update

I update sdkbox and all packages with console “sdkbox update”
But now i have crash my app on device =(

Here is ndk-stack trace of crash:

********** Crash dump: **********
Build fingerprint: ‘lge/p1_global_com/p1:6.0/MRA58K/16293194481ff:user/release-keys’
pid: 21994, tid: 21994, name: .fishing_deluxe >>> com.pagenetsoft.fishing_deluxe <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Stack frame #00 pc 00041bf8 /system/lib/ (tgkill+12)
Stack frame #01 pc 000400a1 /system/lib/ (pthread_kill+32)
Stack frame #02 pc 0001c88f /system/lib/ (raise+10)
Stack frame #03 pc 00019a41 /system/lib/ (__libc_android_abort+34)
Stack frame #04 pc 000175fc /system/lib/ (abort+4)
Stack frame #05 pc 0031f6ed /system/lib/ (_ZN3art7Runtime5AbortEv+212)
Stack frame #06 pc 000f3ac9 /system/lib/ (_ZN3art10LogMessageD2Ev+2092)
Stack frame #07 pc 000f02f7 /system/lib/ (_ZN3art7BarrierD2Ev+182)
Stack frame #08 pc 00346025 /system/lib/ (_ZN3art10ThreadList4DumpERNSt3__113basic_ostreamIcNS1_11char_traitsIcEEEE+144)
Stack frame #09 pc 0031f7a9 /system/lib/ (_ZN3art7Runtime5AbortEv+400)
Stack frame #10 pc 000f3ac9 /system/lib/ (_ZN3art10LogMessageD2Ev+2092)
Stack frame #11 pc 001d3b63 /system/lib/ (_ZN3art22IndirectReferenceTable17AbortIfNoCheckJNIEv+62)
Stack frame #12 pc 0033c4e3 /system/lib/ (_ZNK3art6Thread13DecodeJObjectEP8_jobject+342)
Stack frame #13 pc 00281cc1 /system/lib/ (_ZN3art3JNI12NewGlobalRefEP7_JNIEnvP8_jobject+200)
Stack frame #14 pc 00778779 /data/app/com.pagenetsoft.fishing_deluxe-1/lib/arm/ (_ZN7_JNIEnv12NewGlobalRefEP8_jobject+6): Routine _JNIEnv::NewGlobalRef(_jobject*) at /usr/local/Cellar/android-ndk/r10e/platforms/android-9/arch-arm/usr/include/jni.h:564
Stack frame #15 pc 007788f3 /data/app/com.pagenetsoft.fishing_deluxe-1/lib/arm/ (ZN6sdkbox8JNIUtils10initializeEP7_JavaVMP7_JNIEnvP8_jobjectS6_S6+54): Routine sdkbox::JNIUtils::initialize(_JavaVM*, _JNIEnv*, _jobject*, _jobject*, _jobject*) at /Volumes/extend/jenkins/sdkbox/release/csc/protocols/
Stack frame #16 pc 0077899f /data/app/com.pagenetsoft.fishing_deluxe-1/lib/arm/ (Java_com_sdkbox_plugin_SDKBox_nativeInit+46): Routine Java_com_sdkbox_plugin_SDKBox_nativeInit at /Volumes/extend/jenkins/sdkbox/release/csc/protocols/
Stack frame #17 pc 00c7aeb9 /data/app/com.pagenetsoft.fishing_deluxe-1/oat/arm/base.odex (offset 0x72a000)

have u cleaned obj libs folders?

Can you upload the following files?


Have u cleaned obj libs folders?

as energyy mention.

I update with command

$ cd cpp
$ sdkbox update
$ cocos run -p android

works fine :wink:

Do you mean dir?

Sorry, my fault =(

I can’t update with “sdkbox update” (i think it is because i start project on linux, but now works ob windows)
than I update all packages manually, but forget to update .jars in cocos/platform folder.

Sorry for posting in the same thread, but since I got a similar problem, I decided to post here instead of starting a new thread (if the solution applies). I’ve updated to v2.3.13.2 (via sdkbox update) (previously was 2.3.11) and everything works fine, except the Google Play Games plugin. When I build my game for release and try to login with google, I get a crash and this is the dump from the adb logcat (saved as .cpp as .txt files are not allowed for upload) logcat.cpp (48.5 KB)

All the other plugins work correctly - facebook, onesignal, chartboost, adcolony, etc. and I’ve double checked to see if I haven’t changed the client id, but it is the same as before v2.3.13.2 and if I try the project with the older version (I have a backup of it) the login works. I’ve also deleted intermediate compiled obj files, but this doesn’t help either.

E/GamesNativeSDK: Exception in com/google/android/gms/games/Games.getGamesServerAuthCode: java.lang.IllegalArgumentException: Please provide a valid serverClientId.

have u set correct game app id in your app for google play services?

Yes I have, I’ve checked multiple times and these are the manifest and res/strings.xml files for the old version and new version (2.1 KB) (2.1 KB)

I’ve diffed them and they are practically the same. I don’t know where else the ID could be used so that it would be wrong - the JS plugin initialization doesn’t ask for it and with the previous build it worked - if you can’t reproduce the issue and we can’t fix it, maybe the only option is to revert to my backup for this specific plugin.