You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please use the 👍 reaction to show that you are interested into the same feature.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
After removal of the "all files access" permission already configured Auto uploads fail/stop working silently.
This is a big issue since some users rely on Nextclouds Auto upload feature for backups. After upgrading the app to version 3.30.6 or later Auto uploads and therefore backups stopped working without an error. Only the Google Play build of the app is affected.
Further, automatic app updates may lead to this issue without any user interaction at all.
Describe the solution you'd like
Display a push notification right after app upgrade, if the user has any Auto upload pairs enabled.
Inform the user that
Auto uploads of files other than photos and videos are not working and won't be working with the Google Play Store build
the "Photos and videos permission" needs to be granted so that the auto upload of those files works again (but no other file types)
the location permission is required if the user wants to keep location metadata in their uploaded photos
Actively ask the user to grant the "Photos and videos permission" when they open the push notification
Actively ask the user to grant the "Location permission"
From my perspective this issue is so critical that it warrants a permanent notification until the users acknowledges that they understood the change, either by granting the permissions or by disabling auto uploads.
Describe alternatives you've considered
Find other ways to reach ALL app users with auto uploads enabled that doesn't require them to manually open the app.
Do nothing and let users discover on their own that their backups aren't working anymore.
Only ask for new permissions when the user opens the Auto upload settings manually (current behavior after app upgrade)
Additional context
Users are surprised and upset that auto uploads have stopped working. Several issues and comments on this topic:
- #14199
- #14330
- #14331
- #14333
- #14334 (comment)
The text was updated successfully, but these errors were encountered:
Looks good so far. I can see an informative message, however no notification to inform users who are not opening the app themselves. Added a comment to the PR as well
How to use GitHub
Is your feature request related to a problem? Please describe.
After removal of the "all files access" permission already configured Auto uploads fail/stop working silently.
This is a big issue since some users rely on Nextclouds Auto upload feature for backups. After upgrading the app to version 3.30.6 or later Auto uploads and therefore backups stopped working without an error. Only the Google Play build of the app is affected.
Further, automatic app updates may lead to this issue without any user interaction at all.
Describe the solution you'd like
Display a push notification right after app upgrade, if the user has any Auto upload pairs enabled.
From my perspective this issue is so critical that it warrants a permanent notification until the users acknowledges that they understood the change, either by granting the permissions or by disabling auto uploads.
Describe alternatives you've considered
Find other ways to reach ALL app users with auto uploads enabled that doesn't require them to manually open the app.
Do nothing and let users discover on their own that their backups aren't working anymore.
Only ask for new permissions when the user opens the Auto upload settings manually (current behavior after app upgrade)
Additional context
Users are surprised and upset that auto uploads have stopped working. Several issues and comments on this topic:
- #14199
- #14330
- #14331
- #14333
- #14334 (comment)
The text was updated successfully, but these errors were encountered: