Android library AAR packing resource incorrectly

Content Index :

Android library AAR packing resource incorrectly
Android resource IDs are being incorrectly assigned
Packing an android library on a JAR that uses JNI
refer to android library project xml resource in application xml resource
Why the Active Android Library reports this error = Before Android 4.1, ... would have incorrectly overridden the packag
Avoid packing .jar into Android Library (.aar)

Android library AAR packing resource incorrectly

Tag : android , By : Pip

Date : January 12 2021, 09:11 PM

This might help you I have a libary I wrote years ago and I've very gradually modualrised it and deployed to jfrog , The structure of the AAR is correct, the structure should be:

res/
    values/
        <stuff here>
    layout/
        <stuff here>
    drawable/
        <stuff here>
classes.jar
public.txt
R.txt
AndroidManifest.xml

res/
    values/
        <stuff here>
    layout/
        <stuff here>
    drawable/
        <stuff here>
values/
layout/
drawable/
classes.jar
public.txt
R.txt
AndroidManifest.xml

// don't forget src/main/AndroidManifest.xml: <manifest package="com.test" />
buildscript {
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.4.2'
    }
}

apply plugin: 'com.android.application'

android {
    compileSdkVersion 28
    buildToolsVersion "28.0.3"

    defaultConfig {
        minSdkVersion 14
        targetSdkVersion 28
    }
}

repositories {
    mavenLocal() // for consuming vectoroid local `gradlew install`
    google() // for AAPT2
}

dependencies {
    implementation 'uk.co.sentinelweb:vectoroid-android-draw:0.1.3'
    // TODO uncomment to make it assemble correctly
//    implementation 'uk.co.sentinelweb:vectoroid-android-views:0.1.3'
}

    implementation project(':vectoroid-android-views')
    implementation project(':vectoroid-android-base')

    implementation 'uk.co.sentinelweb:vectoroid-android-views:0.1.3'
    implementation 'uk.co.sentinelweb:vectoroid-android-base:0.1.3'

Comments

No Comments Right Now !

Boards Message :

You Must Login Or Sign Up to Add Your Comments .

Share :

Tags :

Android library AAR packing resource incorrectly , Android , library , packing , resource , incorrectly ,

Android resource IDs are being incorrectly assigned

Tag : android , By : PsyberMonkey

Date : March 29 2020, 07:55 AM

I wish this helpful for you Use ant clean install instead of just ant install.
Java inlines constants like the R.id values into generated bytecode, and sometimes your classes are not being recompiled, even though they need to be. Ideally, ant install would handle this properly; until it does, ant clean install is your friend.

Packing an android library on a JAR that uses JNI

Tag : android , By : user185939

Date : March 29 2020, 07:55 AM

Does that help I don't know if you need support any longer.
You don't need any scripts when you added the Android library project to your Android project.

refer to android library project xml resource in application xml resource

Tag : android , By : baylisscg

Date : March 29 2020, 07:55 AM

wish of those help OK, found the problem!
In Eclipse, in my Project Properties -> Java Build Path -> "Projects" 'tab' I had the library project added.

Why the Active Android Library reports this error = Before Android 4.1, ... would have incorrectly overridden the packag

Tag : java , By : Cosmin

Date : March 29 2020, 07:55 AM

To fix the issue you can do I don't see any code related to your error. Did you share the code where the issue happens? Are you testing on a KitKat or previous device? KitKat and older have issues with Vector Graphics and you have to enable Vector Support as well as handle the vectorSupport tag on src on all images. So I have to assume you have drawable vectors in your project and have put these in the wrong folder or have not properly handled them based on that error, but without more details, that is only a speculation.
Keep in mind folders like no-dpi didn't exist in KitKat days as well as memory issues happen like crazy if not managed very meticulously.