Back
Running updateEmail results in user_target_already_exists exception
- 0
- Flutter
- Messaging
- Auth
- Cloud
Hello everyone!
I'm running the following as part of my app (Flutter), so on the client side:
TypeScript
'email@example.com', // email
'password' // password
);```
This results in an exception:
``user_target_already_exists``
I understand this exception has to do with push notifications, which I have set up in my app. But I don't understand why ``updateEmail`` triggers this. ``updateEmail`` has nothing to do with push notifications. Does anyone have an idea what's going on?
TL;DR
Issue: When running `updateEmail` on Flutter app, `user_target_already_exists` exception occurs, related to push notifications setup.
Solution: The `user_target_already_exists` exception may be caused by conflicting registration of the user for push notifications. Review the push notifications setup in the app to ensure that there are no duplicate registrations for the same user.Recommended threads
- CORS preflight returns 500 on Dart funct...
Hey everyone 👋 I’m running a Dart cloud function, Every time I respond to a preflight (OPTIONS) request, I get a 500 internal error, and the logs show: ```NoSu...
- Auto Updating Backend & Auth via Appwrit...
<@870607367597850624> Hey everyone 👋 I wanted to ask to ask for a friend, he’s asking if Appwrite be used in a similar way to Supabase when integrated with AI ...
- execution failed
When executing an appwrite function, I'm getting a 500 error, but I don't see it in executions. This issue appeared today. Here's the appwrite function ID: 68b4...