How to Keep Placeholders in an AAR's Manifest?

Question

I'm building an AAR library for Android and need to include a ContentProvider in the library's manifest, as such:

<provider
    android:name="sdk.example.Preferences"
    android:authorities="${applicationId}.preferences"
    android:exported="false"
    />

The problem is that when the AAR is built, ${applicationId} is replaced by the AAR's package. What I want is for the manifest of the final AAR to keep ${applicationId} so that it can be replaced with the main application's package when it itself is built. Any idea how to do this?

Currently I'm editing the AAR manually to achieve this, but want to find a better solution

score 0 · Answer 1 · edited May 23 '17 at 12:16

0

Well - the first approach that comes to mind is to use a resource for the authority name, but this is not possible - Using @string for android:authorities in a ContentProvider.

There is however a Maven job that replaces the authority, but I have no idea how it behaves when AAR libraries are involved - Android Manifest with @String reference - specifically android:authorities.

Please report your solution.

edited May 23 '17 at 12:16

Community

1
1

answered Oct 05 '15 at 18:59

Vaiden

15,728
7
61
91

Yes, as stated in the first link. Did you try the Maven job approach (2nd link)? – Vaiden Oct 06 '15 at 07:42

score 0 · Accepted Answer · answered May 16 '16 at 23:08

0

This is now done automatically in Android Studio 2.0

answered May 16 '16 at 23:08

Cigogne Eveillée

2,178
22
36

How to Keep Placeholders in an AAR's Manifest?

2 Answers2

Linked