Do not require contacts permission / drop that requirement as it scares users
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, java
- Domain
- authentication, mobile
Research direction
Start by reviewing the current Android-SingleSignOn permission handling and the related issue #49, along with the linked AntennaPod discussions. Determine whether the contacts permission can be removed without breaking sign-in; done means the integration no longer requires that permission and the affected behavior is verified.
Written by the indexing model from the issue text.
Description
How to use GitHub
- 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.
Feature request
Which Nextcloud Version are you currently using: 29
Is your feature request related to a problem? Please describe.
I tried to convince app maintainers to use this app, like in https://github.com/AntennaPod/AntennaPod/issues/7281
Unfortunately, the reply in https://github.com/AntennaPod/AntennaPod/issues/7281#issuecomment-2213066460 was:
Signing in with the app requires adding the "read contacts" permission to AntennaPod. Users were concerned about that, so we decided against using it. See https://github.com/AntennaPod/AntennaPod/issues/6088
They have thus decided against the integration of this lib, which is sad.
Describe the solution you'd like
Can you somehow just get rid of this permission? Even if it is optional, some users apparently dig there and complain because of that…
Describe alternatives you've considered
I know none…
Obviously not using the lib, but that is sad.
Additional context
May be solved(?) in or is at least related to https://github.com/nextcloud/Android-SingleSignOn/issues/49
- Dominant language
- Java
- Stars
- 74
- Forks
- 36
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 15
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-SingleSignOn
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/Android-SingleSignOn#1081 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nextcloud/Android-SingleSignOn#563 · 2 comments · 1 reaction ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nextcloud/Android-SingleSignOn#894 · 1 reaction ·
-
0. Needs triage bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nextcloud/Android-SingleSignOn#859 · 3 comments ·
-
0. Needs triage enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in nextcloud/Android-SingleSignOn
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1152 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jenkinsci/blueocean-plugin#5417 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·