There is one more way, add application class in your library project: /** * Base class for those who need to maintain global application state. */ public class LibApp extends Application { /** Instance of the current application. */ private static LibApp instance; /** * Constructor. */ public LibApp() { instance = this; } /** … Read more
As mentioned in comments below and another answer, the original answer here doesn’t work with Gradle 3+. Per the docs, something like the following should work: Using the Variant API to manipulate variant outputs is broken with the new plugin. It still works for simple tasks, such as changing the APK name during build time, … Read more
I am currently working on an Android application which streams radio. I use native decoder library which is called aacdecoder. Everything was fine till app gets crash error on some Android devices. It was really annoying. Because app was perfectly plays radio streams almost all devices but Samsung S6 and S6 Edge. Crash report says … Read more
In your module’s build.gradle file (not the root project, if you use modules!), simply replace: apply plugin: ‘com.android.application’ // or, if you’re on an old version apply plugin: ‘android’ // note: this one is deprecated …with: apply plugin: ‘com.android.library’ // or, if you’re on an old version apply plugin: ‘android-library’ // note: this one is … Read more
I found the source of the problem! It turns out that “with the new library feature, you don’t specify the Android projects you depend on in the Java Build Path section of the Properties. You do it in the Android section of the Properties“. So all I had to do is go the Application Project’s … Read more
Sorry, I’m late and the question has already an accepted answer, but yes, you can download and execute external libraries. Here is the way I did: I was wondering whether this was feasible so I wrote the following class: package org.shlublu.android.sandbox; import android.util.Log; public class MyClass { public MyClass() { Log.d(MyClass.class.getName(), “MyClass: constructor called.”); } … Read more
This is the closest that you can get: Step #1: Create a regular Android library project, and get it working. Step #2: Copy that Android library project into another directory. Step #3: Create a JAR from the compiled Java classes from the original Android library project, and put that JAR in the libs/ directory of … Read more
With Android Studio 1.1 and having also the gradle version at 1.1 it is possible: Library android { publishNonDefault true } App dependencies { releaseCompile project(path: ‘:library’, configuration: ‘release’) debugCompile project(path: ‘:library’, configuration: ‘debug’) } Complete documentation can be found here http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication EDIT: The issue has just been marked as fixed for the Android Studio … Read more
I spent some time play with my own project, and I am able to replicate your problem and get exactly the same exception stack trace when trying to run my main project, so I think this could be the cause: Just like what I thought, it is all about how you reference your Android library … Read more
The simplest way is to make MyProject a multi project with the Logger project as a subproject. settings.gradle in MyProject directory: include “:logger” project(“:logger”).projectDir = file(“../logger”) In the build.gradle of MyProject you can now reference this lib as a project: dependencies { compile ‘com.android.support:gridlayout-v7:18.0.0’ compile ‘com.android.support:appcompat-v7:18.0.0’ compile project(“:logger”) }