Crashlytics cocos2dx 3.7 + Android Studio

TheDevil · August 7, 2015, 9:44am

Hi,
I have a project that I have created with cocos2dx 3.7 and compiled it for Android Studio from the command line using the cocos command. I am able to deploy this project on the phone via Android Studio using the Run Command. I was trying to add Crashlytics for crash reporting to my project using Android Studio but i ran into many problems. When I installed the Crashlytics plugin and tried adding it to my project, it said that it could not find any Andoird Module. After changing the buidl.gradle files (I have almost zero knowledge how Gradle Works so please bear with me) I managed to include the Crashlytics files and compile the project using the cocos command line, but now when i ran the project, it crashed on the device saying that it could not find the libcocos2d.so file.
I also tried doing it in an eclipse project, but again i have to use the command line for compiling the project and then Eclipse would create problems as the file R.java was modified externally.

Has anyone integrated this or any other 3rd party sdk into their cocos2dx project in Android studio successfully?If yes, then a tutorial would be very welcome!
Also has anyone been able to build and compile the project from inside Android Studio after they added ndk support to the lastest Android Studio?

dakiki · August 8, 2015, 12:18pm

I reported this issue to crashlytics a week ago, and we are actively working on finding the issue.

TheDevil · August 8, 2015, 12:51pm

That’s good to hear! Looking forward to the solution. Have you managed to integrate any other third party sdk successfully(like google play services, Facebook and other various ad sdks).

chumbyfuzz · August 8, 2015, 3:50pm

I’ve been struggling even just to get the template project to run on my device using “cocos run”. Can you list the steps you took ?

TheDevil · August 8, 2015, 6:24pm

I just created a new project using the cocos new command. After that as mentioned here Cocos2d-x v 3.7 at point number 8 just run the command
cocos run/compile -p android --android-studio
from the console. After that, you can either run using the cocos run command like
cocos run -p android
or just import the project in Android Studio, sync the project and press run. It will run the project on the device or the emulator.
Hope this helps.

dakiki · August 8, 2015, 7:48pm

I had no issue with gpg (integrated it 6 months ago), still working fine (except for the buggy framework itself… so many issues, and now that g+ will be abandoned I don’t think google will fix their bugs).
Didn’t try facebook yet, I was hoping to use SdkBox so I don’t have to do the integration myself

TheDevil · August 10, 2015, 4:44am

I hope SDK box is as easy to integrate as they make it sound

dakiki · August 10, 2015, 10:18am

I will try as soon as IAP support purchase validation. I’ll add both facebook and IAP at the same time.

TheDevil · August 11, 2015, 6:18am

let me know how that works out! also if you figure out the issue with Crashlytics let me know about that too!

dakiki · August 11, 2015, 8:01am

They are still trying to understand the issue.
Hope it will be solved quickly

TheDevil · September 1, 2015, 7:23am

hey any update on this from them?

energyy · September 8, 2015, 10:48am

Hi,

I was able successfully integrate crashlytics thru eclipse for 3.7, but it was big pain

Probably it should work also with Android Studio.

Regarding that part:> it crashed on the device saying that it could not find the libcocos2d.so file.

I had same issue, because crashlytics had prebuild libraries for all kind processors (armeabi, x86…), so it’s trying to check also for each prebuild library specific cocos2d.so.

What I did, I manually deleted not used libs from crashlitcs, left only armabi and also pointed in Application.mk to compile project only for armabi…

Have a try… planning today to integrate Android Studio + Cocos2d-x 3.8 + Crashlytics

pandemosth · September 15, 2015, 12:18pm

Hi, any update on Crashlytics integration? The Fabric plugin doesnt work for me, I’ve been through manual steps to add crashlytics to gradle but getting:

java.lang.IllegalArgumentException: Crashlytics found an invalid API key: null.

Thanks!

dakiki · September 15, 2015, 3:41pm

Sorry, no answer.
I think they banned me for asking for an update every couple days

I’ll try to ask them once again, but your error seems to be something else, it looks like you misconfigured your key somehow.

energyy · September 15, 2015, 7:47pm

Key is stored in Android manifest and if not project.properties file, so it’s you config issue for now.

pandemosth · September 15, 2015, 9:44pm

Thanks. I’ve got the key in the manifest and also copied a fabric.properties from another project (for the same organisation so same api secret). Can you give more detail on what you think should go in project.properties?

energyy · September 16, 2015, 3:43pm

Double checked project, so regarding key no changes in project.properties but in fabric.properties:

#Contains API Secret used to validate your application. Commit to internal source control; avoid making secret public.
#Sat Jul 11 18:49:24 EEST 2015
apiSecret=MY_KEY
androidBaseManifest=AndroidManifest.xml
enableNDK=true
androidNdkOut=obj
androidNdkLibsOut=libs
externalCSymUpload=true

pandemosth · September 17, 2015, 1:11am

Thanks @energyy

I’ve been able to get the Fabric (Crashlytics) plugin working with the cocos2d-x project in Android Studio. The problem it was having was that it parses the module’s .iml file to determine source and resource paths. The iml is an internal project manifest generated by Android Studio from the build.gradle file. This contained references to default paths like ‘src/main/java’, ‘src/main/res’… and it was visible in the crashlytics plugin log that it couldnt resolve these non-existent paths and so was giving up (and just bumping me out to the login screen again).

Not sure exactly why these paths are appearing in the .iml file, but it does appear to be caused by how Android Studio is interpreting the gradle file, because here is the fix:

In the app’s build.grade (that is generated by the cocos tool with --android-studio flag) the sourceSets config looks like this:

 sourceSets.main {
     java.srcDir "src"
     res.srcDir "res"
     jniLibs.srcDir "libs"
     manifest.srcFile "AndroidManifest.xml"
     assets.srcDir "assets"
 }

Change this to:

sourceSets.main {
    java.srcDirs = ["src"]
    res.srcDirs = ["res"]
    jniLibs.srcDir "libs"
    manifest.srcFile "AndroidManifest.xml"
    assets.srcDirs = ["assets"]
}

And the default non-existent paths are no longer present in the .iml and the Crashlytics plugin is able to work happily with the project. Hope this helps others struggling with the same integration.

Cocos team, may be worth investigating a bit further as there could be other side effects of the invalid paths in the .iml file?

Cheers

energyy · September 17, 2015, 6:32am

That cool, will try to use with android studio also. Btw have you integrated crashlytic with ndk support? It’s very usseful when it goest to c++ code crash.

pandemosth · September 17, 2015, 12:44pm

Yeah, I’ve added the ndk config but havent seen it in action yet. Have used Crashlytics for a while on other projects, its a great service.