I've updated my code snippet
this one
should store the user in localstorage then navigate to dashboard
not working
but it's fine
I will try to find other way
oauth2 requires cookies and your browser may be blocking cookies if the appwrite cookie is not a 1st party cookie. This is where custom domains comes in: https://appwrite.io/docs/custom-domains
Hey Steven thank God you are here π
I have created A record for the appwrite but don't have a cname record
Is this a problem for cookie ?
Because as I can see after successful Google auth login there are no cookies in local storage
long term, in production, local storage should not be used
the point is the front end and the endpoint the front end uses needs to share the same base/registerable domain
Then instead of local storage what should be used ?
cookies and it should be done automatically if everything is set up correctly
for email login cookies are generating automatically
but for google login it is not generating
actually i didn't get what you said . . . . . π
so if your frotned app is on example.com, the api endpoint that your frontend app uses must be *.example.com/v1
Yes
Then what ?
you said you didn't understand. I just explained
nothing else...appwrite automatically tries to set session cookies and browsers should automatically handle the session cookies
Ok
thanks buddy
Recommended threads
- No server error on selfhosted appwrite
Please help me, my clients is ask what happen on their data? How can i make it up again?
- Upgrading selfhost version?
It is okay to upgrade version to higher one, of my current version is 1.7.4 to 1.8.1. Is that safe to do cause my clients already have data on that? Also is a...
- Streamlit UI and local DB
I want to use Appwrite for automation, like run watchdog service every morning 3 am. Anyone got suggestions, already explored github and documentation no luck. ...