
I’m using Google Sign-In in my bare React-native app and verifying the user's email through Google OAuth. After verifying the token server-side, I create the user using the node-appwrite SDK. However, even though the email is already verified via Google, the user shows as "Unverified" in the Appwrite Dashboard and requires manual verification.
Request: Please add a way to set emailVerification: true while creating a user via the node-appwrite, since the email is already trusted.
This would greatly help when integrating with third-party OAuth providers like Google or Apple in bare react-native projects, where email verification is already done upstream.
Thank you for your amazing work on Appwrite!

my own one is getting Verified directly

i'm using react-native-appwrite

actually react-native-appwrite is expo based. and that is not working in bare react-native project.

alright if you are doing it server side so i don't see any issues for verifying the account manually using the server

My approach – I use @react-native-google-signin/google-signin in my React Native app to get the Google account idToken, which I then send to my Node.js backend. There, I use google-auth-library to verify whether the idToken actually came from Google. If it's verified, I extract the email ID from the idToken and create a user and JWT in Appwrite using that email. that why it does not getting Verified directly. Then, I send the Appwrite JWT back to the React Native app and store it in AsyncStorage.

Recommended threads
- Svelte App Whitelist
https://appwrite.io/docs/quick-starts/sveltekit Based on the example from the docs, how woul'd I go about adding a "whitelist" that checks if the user has a sp...
- User (role: guests) missing scope (accou...
is this an expected behavior?
- Login server-side action (NextJS) not cr...
(for <@186656408450629633>) hello, so I created this login function: ```ts export async function logIn(email: string, password: string) { const account = new ...
