I do this for android notifications
TypeScript
ID.unique(), // targetId
token, // identifier
this._pushNotificationsProvider
)```
after user login, I don't check previous target exists neither delete target when user logs out
but I'm using `ID.unique()` so why does it launch this error?
TL;DR
Developers are experiencing an error stating "A target with the same ID already exists" when trying to update the user's phone from the dashboard. The issue might be related to not checking if a previous target exists or deleting the target when the user logs out. Despite using `ID.unique()`, the error persists.
Solution: Implement a check to verify if the target already exists before creating a new one, and consider deleting the target when the user logs out to prevent conflicts.Same stated happening for me when I try to update the User phone from the app write dashboard (selfhosted-latest)
Recommended threads
- `type 'Null' is not a subtype of type 'b...
When creating a new file using Appwrite Flutter SDK, the file is successfully created on the server, but the client throws the following exception: ``` type ...
- Console: Query on attribute has greater ...
I noticed an issue when one of my tables reached over ~800 rows. That table is relational to my users table Within the console I am able to view the table with ...
- Appwrite 1.8.1 - Traefik Returns 404 Due...
Problem: Fresh Appwrite 1.8.1 installation returns 404 on all requests. Traefik can't communicate with Docker daemon. Error: Error response from daemon: client ...