cloudinary_android
cloudinary_android copied to clipboard
Remove android:fullBackupContent from AndroidManifest.xml
I get a merge error with other libraries that also contains this.
Please remove this as the app should decide how to handle backup.
Hi @mikaelbartlett, can you please let us know with which library it conflicts?
Hi @roeeba
https://github.com/pusher/push-notifications-android/issues/89 here's the link to the other library.
Thanks, @mikaelbartlett. I'm assigning it to our mobile engineer to further investigate.
We run into similar issues where we get a lint error due AndroidManifest
not respecting android 12 changes.
/root/.gradle/caches/transforms-3/6a5afdf55df46ace7be55e9720e00da9/transformed/cloudinary-android-core-2.3.0/AndroidManifest.xml:11: Error: Missing <full-backup-content> resource [DataExtractionRules]
<application android:fullBackupContent="@xml/backup_config" />
~~~~~~~~~~~~~~~~~~
Explanation for issues of type "DataExtractionRules":
Before Android 12, the attributes android:allowBackup and
android:fullBackupContent were used to configure all forms of backup,
including cloud backups, device-to-device transfers and adb backup.
In Android 12 and higher, these attributes have been deprecated and will
only apply to cloud backups. You should instead use the attribute
android:dataExtractionRules, specifying an @xml resource that configures
which files to back up, for cloud backups and for device-to-device
transfers, separately. If your minSdkVersion supports older versions,
you'll still want to specify an android:fullBackupContent resource if the
default behavior is not right for your app.
https://developer.android.com/about/versions/12/backup-restore#xml-changes
1 errors, 0 warnings
FAILURE: Build failed with an exception.
Hi @waliahimanshu,
I just want to update you that this was fixed in the Android SDK 2.3.1 version. I will go ahead and close this for now. Do let us know if you have any issues.
Thanks