user-feedback: add iOS Home Screen PWA auth troubleshooting guidance
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- supabase
- Domain
- authentication, documentation, mobile-dev
Research direction
Start in SKILL.md under the Supabase Documentation section. Add the password sign-in and recovery links plus the specified iOS Home Screen PWA troubleshooting note, including the OTP plan and email-template distinction. Done means the guidance covers persistent in-app sign-in and browser-opened recovery behavior.
Written by the indexing model from the issue text.
Description
What happened
Task: Build a Supabase-authenticated PWA that remains signed in when launched from the iOS Home Screen.
Skill said: The skill routed correctly to Supabase Auth documentation, but it did not mention that an iOS Home Screen web app can have storage and browsing context behavior separate from Safari, or that email OTP behavior depends on the configured email template.
Expected: Add a short troubleshooting note recommending an in-app email/password flow with recovery links as a robust fallback for iOS Home Screen PWAs, explain that OTP is available on the Free plan, and distinguish Magic Link/OTP template configuration from plan availability.
Source
File: SKILL.md
Section: Supabase Documentation
Fix suggestion
Link to the password sign-in and password recovery documentation, and add an iOS PWA note: establish the persistent session by signing in inside the installed Home Screen app; use the browser-opened recovery page only to set the password.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
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 supabase/agent-skills
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
supabase/agent-skills#586 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#585 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
supabase/agent-skills#583 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
supabase/agent-skills#582 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#581 ·
All issues in supabase/agent-skills
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100