Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exclude adjust_preferences.xml from backup? #415

Open
ubuntudroid opened this issue Jan 14, 2020 · 2 comments
Open

exclude adjust_preferences.xml from backup? #415

ubuntudroid opened this issue Jan 14, 2020 · 2 comments

Comments

@ubuntudroid
Copy link

ubuntudroid commented Jan 14, 2020

If android:allowBackup="true" is defined in the Android manifest (just like in all sample apps here) it might make sense to exclude adjust_preferences.xml from full backup by adding

<exclude
        domain="sharedpref"
        path="adjust_preferences.xml"/>

to the full backup content rules to ensure that the install is tracked. Or am I mistaken?

If this is correct this should be added to the setup instructions.

@ubuntudroid ubuntudroid changed the title exclude adjust preferences from backup? exclude adjust_preferences.xml from backup? Jan 14, 2020
@ubuntudroid
Copy link
Author

ubuntudroid commented Jan 14, 2020

Actually it would be even simpler if the adjust SDK would write all data not to be backed up into the no_backup folder (Context.getNoBackupFilesDir()). Then devs wouldn't have to mess around with exclusion rules and everything would automatically always stay in sync with SDK iterations.

@Iris3492
Copy link

Iris3492 commented Mar 2, 2024

Actually it would be even simpler if the adjust SDK would write all data not to be backed up into the no_backup folder (Context.getNoBackupFilesDir()). Then devs wouldn't have to mess around with exclusion rules and everything would automatically always stay in sync with SDK iterations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants