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
- Impossible to get USER after createEmail...
Am using provider to deal with functions linked to appwrite. Here is my login. Future<String?> login(String email, String password) async { try { aw...
- fastly error
Hey! I'm hitting a Fastly error on the www version of our site, but the root domain works fine. We have a wildcard set up, so I expected the subdomain to be cov...
- Facebook's scraper facebookexternalhit g...
share.bardbliss.com but works fine on the raw fra.appwrite.run URL. No execution logs appear when Facebook hits the custom domain. This was working before. How ...