I have had no problems building and running Corona Enterprise sample projects or our company project from the command line. I have had no problems following the Corona Enterprise Android Quickstart guide. I have had no problems with building and running non-Corona Android applications in Android Studio. However, I have had major issues getting even the Corona Enterprise Sample projects to build and run successfully in Android Studio.
I was wondering if there is more up-to-date information on integrating Corona Enterprise into the Android Studio build process, so that Android Studio can be set up to build and run Corona applications for Android. Having searched the forums, I found that Android Studio is briefly mentioned in this thread as something that will possibly be supported more in the future, but nothing more.
Any further information on this? As Android Studio is now past 1.0, I thought perhaps many others may also be wondering.
Sharing some specifics would be good at this point. So, Android Studio uses the Gradle build system. I know that the Corona project library should be included and/or referenced in Gradle in a way that is analogous, but obviously different, from the conversations found here and here. I suspect not doing this portion correctly is my current sticking point.
Any insight that you may be able to share as to best practices on how this is done for Corona libraries or applications involving Corona Enterprise would be helpful. Perhaps the people you know that use Android Studio can help provide answers as well.
We are also trying to run the Enterprise Template app in Android Studio. I know it must be possible to translate the template to an Android Studio structure using Gradle, but I am not experienced enough with Gradle to get it to work. It would really help if someone could point us in the right direction!
Engineering said that apparently the Google build process is pretty complex and that they don’t make this easy. We pretty much use either ant or Eclipse in house. We have very little experience with Android Studio and really don’t feel we can help with this. Maybe the community can help with this.
We are very interested in Corona Enterprise running in Android Studio as well. We want to make a plugin that uses a library built in Android Studio. Converting that library to Eclipse will be difficult and seems like the wrong way to go.
Sharing some specifics would be good at this point. So, Android Studio uses the Gradle build system. I know that the Corona project library should be included and/or referenced in Gradle in a way that is analogous, but obviously different, from the conversations found here and here. I suspect not doing this portion correctly is my current sticking point.
Any insight that you may be able to share as to best practices on how this is done for Corona libraries or applications involving Corona Enterprise would be helpful. Perhaps the people you know that use Android Studio can help provide answers as well.
We are also trying to run the Enterprise Template app in Android Studio. I know it must be possible to translate the template to an Android Studio structure using Gradle, but I am not experienced enough with Gradle to get it to work. It would really help if someone could point us in the right direction!
Engineering said that apparently the Google build process is pretty complex and that they don’t make this easy. We pretty much use either ant or Eclipse in house. We have very little experience with Android Studio and really don’t feel we can help with this. Maybe the community can help with this.
We’ve made some progress on this recently. I have the template application building in Android Studio 1.2.1.1 by porting the original custom Ant tasks from build.xml. I’m not experienced with Gradle at all, so it’s not very pretty and doesn’t work with all the Android plugin features (product flavors specifically), but it does compile and run.
The difficulty was getting the custom tasks to hook into the predefined Android Gradle plugin build tasks in the right places. In the end I’ve started replacing the signature on the final APK because I couldn’t find a way to run the CertifyBuild.sh script without invalidating the signature added automatically by the default build tasks.