Explicitly warn that "Media read-only" will also lead to the GPS Location tags loss from all pictures!
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start in app/src/main/res/values/strings.xml at the permission prompt around line 1098, then inspect the Android client onboarding flow that displays it. Update the prompt so it explicitly warns that choosing Media read-only can remove GPS/Location tags before picture backup; done means the warning is shown in that choice flow and accurately reflects the reported behavior.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Upon installing the android client, user is asked whether they'd like to grant "Media read-only" or "Full access"
However, the question is extremely misleading, as it is not mentioned that choosing what seems as a safe value if one only wants to sync pictures ("Media read-only") it will lead to silent data loss by system removing Location/GPS tags from all pictures before they're backed up on Nextcloud server!
see e.g. https://github.com/nextcloud/android/issues/6248#issuecomment-1843178111 and all the data loss problems people are having.
Describe the solution you'd like
Explicitly warn the users that choosing "Read-only" will lead to permanent loss of Location tags from all the pictures that are "backup up" to the Nextcloud server.
Describe alternatives you've considered
-
Nextcloud client could alternatively perhaps always request location permission, so GPS Location EXIF tags won't get stripped. For example, I can share pictures to Wikimedia Commons app without GPS location being lost, so perhaps similar solution could work for Nextcloud client too.
-
Or, nextcloud client could explicitly ask users if they'd like to preserve Location tags on their pictures, and if so, refuse to proceed unless required permissions are granted or the users chooses they don't want Location preserved afterall.
- Dominant language
- Kotlin
- Stars
- 5.6k
- Forks
- 2k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 101
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/android
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
0. Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
0. Needs triage enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in nextcloud/android
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·
-
helsemelding-json-schema json-schema-core
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
contributor: external needs review
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100