We have the following setup:
We build and ship an Library for our clients. The SDK is obfuscated with DexGuard
That Library is also used in our application. Our application should use the same AAR file that is shipped also to the clients that is obfuscated.
Till version 2.3.* of Android plugin it was building the AAR file and reusing then that library for the app. From version 3.0 it does not seems to be the case. I have the feeling that it is using directly the files.
Is there a way to force the same process - to build the AAR and then to use it from the app?
Thanks and Kind Regards
Related
Is there possible add Crashlytics to the chromium android? This is easy with projects based on gradle with Android Studio https://firebase.google.com/docs/crashlytics/get-started?authuser=0&platform=android#java . But the chromium build uses ninja build tool - without gradle and Android Studio. So I do not understand how to add Crashlytics to the chromium.
I'm pretty sure that one can build NDK projects with Gradle and Ninja, so this claim might be a misconception of what Gradle is able to do and what it isn't able to. Likely you'll have to add crashlytics.h and libcrashlytics.so for native crash reporting.
There's also an external mini-chromium module contained.
Crashpad is the chief consumer of mini_chromium.
I have this Unity 5.4 project, and I build it separately for iOS and Android.
On the iOS side, life is rather easy. Unity generates an XCode project which I then use cocoapods to add 3rd party libraries to.
On the Android side, the Android Project that Unity "builds" (exports), is not a standard Android Studio project, and you need to import it, instead of just opening it.
This leads to some complications, beyond my grasp of how Android studio works.
I believe it all boils down to getting Gradle to include the 3rd party libraries into the build, but since the app does not start the regular way, things don't end up running.
Has anyone added 3rd party libraries to a Unity/Android Studio project? any pointers will be appreciated.
If the third party libraries are in aar/jar format, there is an option in the "inspector" tab to include them when Unity builds.
Usually you will be able to find .aar / .jar versions of the library you want on jCenter or Maven.
Another way is to see if the source code is hosted on Github, and build it into an .aar/.jar yourself in Android Studio
I am currently using Android Stuio Beta 0.8.1 an its working fine but I am having an issue with library projects are handled.
In Eclipse, I create an Android project which is my app project and another project which is my Library project. From my App project, I reference my Library Project and I can modify the library project and the changes are automatically built into the app project.
I am trying to do the same thing with Android studio but am having a problem.
The problem is I create my Library project in Android Studio and my App Project in Android Studio.
From my app project I go File > Import Module and point to my library project and it then copies all of the source code from my library project into my apps project structure.
From my app project I then project structure and select module dependency of the module I have just imported.
The problem is though, as it copies all of the source from my library project into my app project, if I modify the code that's imported into the app project structure, then the library project isn't updated, and if I update the library project code, the app referencing the library doesn't see the change.
My library is being referenced by multiple projects, and at the moment if I change, librar projects, the apps continue to use the old code, so I am having to copy/paste the source code into the apps project stucture and re-build.
Am I missing something basic or is it just Android Studio isn't really working too well witih libraries so copy/paste is my only option for the time being.
Because libraries must live within the main project, it's difficult to share them across projects. If that's your usage, the library should be its own project that you publish to maven locally. After that, you can declare it as a dependency similar to any other. Keep in mind that the version number of the library becomes important; when you make changes to the library, be sure to publish with a new version number.
I have a main Android project which references 4 other Android-Library projects in gradle. It compiles just fine and i can deploy it via gradle commandline, however I would like to debug my code using eclipse.
Whenever I load up the projects in Eclipse using the gradle integration plugin for Eclipse, eclipse won't even recognize them as library projects and instead treats them like normal android applications. Is this behavior normal or is something wrong with my gradle build script or does eclipse simply not support such a setup yet? Running/debugging the main application in eclipse just installs the individual libraries as regular applications which results in my main application not being able to find the specified classes.
My gradle build script is basically a c&p from Mike Gouline's sample project https://github.com/mgouline/android-samples with "apply: android" replaced with "apply: android-library" for my library projects.
Eclipse doesn't properly support Android Gradle projects. The Android plugin has a lot of specialized support for android-library modules that Eclipse's Gradle integration doesn't know about. For the time being, if you want full IDE support for Android/Gradle, Android Studio or IntelliJ with the Android plugin are your only choices.
We know the situation for people who are using the Gradle build system and want to use Eclipse isn't great; it's something we're thinking about, but we don't have anything definite on the roadmap yet.
I am working alongside with two other developers in an android application. In the application we use other third-party libraries like SlidingMenu.
In eclipse we should include the SlidingMenu project and point our application to use this project as library.
Now I want to automate the building of the application using Hudson(Jenkins) but I have no Idea how I will deal with the dependence libraries like SlidingMenu.
Any Ideas
So long as you can build your app on the command line (e.g. using the Ant or Gradle build systems for Android), then you can build your app in Jenkins.
For the Ant build system, all you need to do is place your dependency JARs in the "libs" directory.
Or if you're using library projects, the Eclipse plugin should have already added the required entries to your project.properties file.