need different deeplink

In the issue, you said:

so whenever the 2nd app logins the 1st apps session would be deleted

The cookie is deleted from the browser, but it should still also be in the 1st app and it should still work 🧐

the cookie is replaced the old session dosent exists

ohhhhhhhhhh wait...it's because you're using react native

Yes

but i dont think so if react native is the cause for this

yes because it's basically a web app and the cookies are shared. You'd have the same problem with 2 web apps using the same project

as far as i checked the browser replaces the cookies for the new one.. making the old cookie invalid

how are you getting around the callback deeplink problem?

as of now im just manually selecting the requried app

but the main problem was with multiple sessions for the same project in different apps

which i fixed by not setting the cookie for the default Oauth success

interesting...okay

you can also solve the cookie probem by using a different custom domain for each app

but thats a difficult solution...

for my app use cases i have to make 3 to 4 different apps for the same project

not setting the cookies for the default auth perfectly solves the issue for multiple sessions with same project

why?

need to configure the domain... then point it to the appwrite server.. then add it in the platform

also if the deeplink session cookies are stored in the browser then the web-app which is based on the same project will automatically login.. and if the user logouts of the web-app.. the session is again deleted from both web-app and android app

it might be a different context. im not sure

but it's a valid use case... I have web-based app and also react native android app... whenever i log in to the react native.. the web app is automatically login..

also is there any specific reason to set Cookies for the default Ouath link?

not if you use a custom domain

cookies are used for auth in general so that the browser automatically handles the session. for example, when using <img>

yeah thats right... but it makes no valid reason to set it on the default oauth... for my uncerstanding people using oauth will have a valid redirect... only for those who use it as a deeplink uses default oauth