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
- Bulk API limitations in self-hosted serv...
Environment: Appwrite Selfhost SDK: node-appwrite 28.0 Calling `upsertRows` (also applies to `createRows`/`updateRows`/`deleteRows`) with more than 100 rows fa...
- Self Hosted GitHub connection not adding...
After upgrading to 1.9.6 i noticed that i cannot search for new repositories when trying to add new functions. I removed the existing github connection via Set...
- Getting current user has been blocked
Getting current user has been blocked error while signing in the appwrite console. Got this during I am testing with the my saas web project. Please help to unb...