Closed nicolas-vivot closed 1 year ago
Hi Nicolas,
We will provide troubleshooting advice on the Zendesk support ticket you raised earlier, please see that for updates.
No update on the ticket for the last 20 days
This has been recognized as a bug on the SDK, the fix would probably take 2 to 3 lines of code but there is still nothing...
@benjamin-tang-pusher When can this be fixed on the SDK (handling correctly the error returned by Pusher backend services) ?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thankyou.
Hi,
We released an iOS app recently and are facing some issues to log in with Pusher Beams authenticated users.
Here is the process we apply when a user log into our application successfully:
When a user explicitely log out our application, we don't do anything since we want that user to be able to receive notification on the mobile application. That's also the reason why we do this 'stop()' call first after a login, to clear the pusher SDK local state if the new logged user is different than the previous one.
Time to time, some users get errors while doing the 'setUserId()' operation with the following message:
Device could not be created
I believe this is an error returned by the Pusher backend itself, not the SDK.
For one of these users, i have checked on our backend the devices it get, and try to send notifications to his device with the Pusher debug console, but not user nor device were found on Pusher for the given Pusher User ID.
What does this error message means ? What could be the potential reasons ?
Note: please confirm here whether this is more a server side pusher issue than an SDK one.