cancel
Showing results for 
Search instead for 
Did you mean: 

Software Development Kit for ST25 Tags and Dynamic Tags - Android integration

NickVimar
Associate

Hello,

I hope this is not a duplicate but I didn't find a similar issue.

I'm developing for my company an Android app using the STSW-ST25SDK001 - Software Development Kit for ST25 Tags and Dynamic Tags (https://www.st.com/en/embedded-software/stsw-st25sdk001.html).

To use your SDK i have to include two artifacts:

  • st25sdk-1.13.0.jar
  • st25_android_reader_interface-1.0.12-release.aar, specific for Android

I see that the AAR includes an "application" tag in its AndroidManifest.xml, even if it's only a library and does not provide an Application class:

<application
android:allowBackup="true"
android:label="@string/app_name"
android:supportsRtl="true" >
</application>

This cause Gradle to complain and fail build with the following error:

 

Manifest merger failed : Attribute application@allowBackup value=(false) from AndroidManifest.xml:7:9-36
is also present at [st25_android_reader_interface-1.0.12-release.aar] AndroidManifest.xml:10:9-35 value=(true).
Suggestion: add 'tools:replace="android:allowBackup"' to <application> element at AndroidManifest.xml:5:5-50:19 to override.
 
We can use "tools:replace" in our app manifest but it seems more of a workaround which makes the app build but sometimes still replaces the correct configuration as described here https://stackoverflow.com/a/36626818/3853058
 
I think the "application" part in the AAR Manifest should be removed, is it possible please?
 
Thanks
3 REPLIES 3
NickVimar
Associate

hell @all any feedback on this?

RuggyVimar
Associate

Hi! I’ve encountered the same manifest declaration. It’s not critical, but a cleaner AAR without the application tag would definitely help. Following this discussion for updates.

France Berthelot
ST Employee

Hello 

Thanks for the highlight, we will handle this on next release (probably mid of december)

BR

FB