Hopefully I'm posting in the right side of the forum. Having some issues with the app that I'm working on, the developers that made it said that the issue it may be watch related (I'm testing on a Samsung Gear S3 Frontier Wi-fi Only).
Until Thursday, everything went smooth with the app. But since Friday, when I login, I keep getting the message that "Registration id is not avaiable". The login works, but when I get to the registration id i'm seeing: "NotificationRegId":"tizen:null" followed by "The following error occurred: UnknownError push-notification-service.js:70" message in the debugger of the app.
Tried with the emulator from Tizen Studio, there is no issue there (the registration id from the emulator it starts with "04". The registration id of the watch was starting with "54". Since there were no edits on the push notification part of the code and that the issue happens kind of inconsistent (one of the developers has two devices, one works and one has the same issue as mine), do you know that maybe there are some issues with the Push Notification service not being able to track the registration id?
Thanks,
Gheo