
Hi everyone, I'm experiencing an issue with a clean self-hosted installation of Appwrite version 1.7.4. I previously used version 1.6.1, and if I remember correctly, the "Memberships privacy" option in Auth > Security didn’t exist back then.
With 1.7.4, I initially had trouble accessing the userName and userEmail fields of memberships, but after discovering the "Memberships privacy" setting and enabling both options, everything worked fine.
However, over the past two days, I’ve had this issue occur twice: suddenly, the server starts returning null for both userName and userEmail in the membership objects again. Both times, I was able to fix it by toggling the privacy options off and back on in Auth > Security > Memberships privacy, and after that, the server immediately started returning the values again.
It seems like Appwrite sporadically “forgets” this setting or stops applying it correctly. Since I didn’t change any code, this feels like it might be a bug in version 1.7.4?
Has anyone else experienced this?
Cheers!
Recommended threads
- Avoiding 409 user_already_exists When Mi...
We’ve migrated all our existing email+password users into Appwrite and now want to switch entirely to OAuth (Google & Apple) for authentication. Our plan is th...
- OAUTH2 doesn't works
https://github.com/202420505/APPWRITE-GOOGLE-AUTH Is my code wrong? I think this is also related to deeplinks
- Struggling with Sessions
Understanding check: createAnonymousSession() registers the session with the backend setSession() creates a cookie on the user’s computer(?) getSession(‘curr...
