BUG: "An error occurred, please try again" After Google Sign-In
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Is there an existing issue for this?
- I have searched the existing issues
What happened?
📌 Issue Overview
When a user(patient) clicks "Continue with Google", they first receive a green pop-up message:
✅ "Signed in as FirstName LastName"
This indicates that Google Sign-In was successful.
However, immediately afterward, they receive a red pop-up message:
❌ "An error occurred, please try again."
After debugging, we discovered that the root cause of this error was the patient table missing in Supabase deployment.
🔍 Steps to Reproduce
- Open the Flutter Patient app.
- Click "Continue with Google".
- Observe the green pop-up confirming successful sign-in.
- Observe the red pop-up with the error message.
- Check the Flutter logs for the Supabase relation "public.patient" does not exist error.
🎯 Expected Behavior
- After signing in with Google, a user should be redirected to the appropriate screen (home or personal details).
- No error should be shown if authentication is successful.
- If a new user signs in for the first time, their patient record should be created automatically.
🚨 Actual Behavior
- User clicks "Continue with Google".
- Google authentication succeeds (green pop-up).
- The app attempts to check if the user exists in the patient table.
- API call fails because the patient table does not exist in Supabase.
- A generic error is shown (red pop-up: "An error occurred, please try again").
The Flutter logs show the following error:
I/flutter (21358): Error checking patient existence:
PostgrestException(message: {"code":"42P01","details":null,"hint":null,"message":"relation \"public.patient\" does not exist"},
code: 404, details: Not Found, hint: null)
🔹 This confirms that Supabase is rejecting queries because the patient table is missing.
💡 Suggested Improvements
Automatically Create the patient Table via Supabase Migrations.
Record
- I agree to follow this project's Code of Conduct
- I want to work on this issue
- Lingua principale
- Dart
- Stelle
- 30
- Fork
- 49
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di AOSSIE-Org/NeuroTrack
-
fix(therapist): Method marked @override does not override any inherited methodForse già presa @Muneerali199 l’ha presa 252 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
AOSSIE-Org/NeuroTrack#198 ·
-
fix: Don't use BuildContext across async gaps (use_build_context_synchronously)Forse già presa @Muneerali199 l’ha presa 252 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
AOSSIE-Org/NeuroTrack#197 ·
-
fix(patient): Remove unused and duplicate imports across patient appForse già presa @Muneerali199 l’ha presa 252 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
AOSSIE-Org/NeuroTrack#195 ·
-
BUG: Therapy details save button has no loading guard, allowing duplicate submissions that inflate patient regression reportsForse già presa @Varadraj75 l’ha presa 215 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 68/100
AOSSIE-Org/NeuroTrack#221 ·
-
BUG: Appointment booking ignores selected time slot, every appointment saved at midnight to SupabaseForse già presa @Varadraj75 l’ha presa 220 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
AOSSIE-Org/NeuroTrack#219 ·
Tutte le issue di AOSSIE-Org/NeuroTrack
Issue simili
-
Drop the decision-issue rule from ARCHITECTURE.mdForse già presa @abianche l’ha presa oggi. Apertachore
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 61/100
I maintainer di solito rispondono entro 1 giorno
-
duration: tiny priority: low type: bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
duobaseio/forui#1249 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Off-by-one error in CharacterRange.length excludes end characters ('z', 'Z', '9', 'ÿ')Forse già presa @TimelordLeo l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
I maintainer di solito rispondono entro 2 giorni
-
[Bug] Missing Simplified Chinese translation for 'balance' and 'lowest' balancer outbound namesApertabug from-telegram platform:android version:v5.9.15
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
hiddify/hiddify-app#2655 ·
I maintainer di solito rispondono entro 1 giorno