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

[Bug] App looses access to backup folders, thus finds no backups #855

Open
hatelamers opened this issue Mar 23, 2024 · 1 comment
Open

Comments

@hatelamers
Copy link

Description
After configuring a backup folder and performing backups of some apps, at first everything seems ok: backups are listed and can be restored. However, after a while of device inactivity, the app cannot find any of the backups.

Steps To Reproduce

  1. Select a backup folder
  2. Backup one or two apps
  3. Backups are seen in the app list
  4. Close Neo Backup (even force close from settings)
  5. Open Neo Backup
  6. Backups are stil listed and restorable
  7. Close Neo Backup or switch to different app
  8. Leave the device alone for ~30 min
  9. Open Neo Backup
  10. All backups are missing (but clearly exist in the files system)

Expected behavior
Backups remain accessible in the app as long as they are not deleted by the user or the retention rule.

System Information(please complete the following information):

  • Device: Lenovo Tab M11
  • Android Version: 13
  • ROM: Stock rooted with Magisk
  • App's Version: 8.3.6

Additional Notes
Nothing I tried, fixed the issue:

  • created the backup folder from within Neo Backup, in file manager app or in adb shell
  • used internal storage, primary SDCard, secondary SDCard, USB stick
  • switced allowShadowDefault and shadowRoot on and off

The behavior remains the same: after a while all backups disappear.

@hatelamers
Copy link
Author

Additional info

I managed to assemble a working setup: external USB hub with an USB stick, of course this is not a solution.

Several other apps using content: URL to access files have similar problems on this device. Apparently it is kind of Lenovo's "feature", all "internal" FS handles (and their permissions) acquierd via Content Manager API get ivalidated after a period of inactivity and have to be requested again. Apps using file: URL or native OS API are not affected.

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

1 participant