Languages

Menu
Sites
Language
Push notification regID timeout

I created a sample php script to test the sending of push notifications to a tizen web app and I am able to successfully send notifications to a tizen (2.2) test device.  The test script uses hardcoded values for every part of the notification (e.g. regID, appID, etc), however, I have noticed on several occassions that I start getting 3008 ("error of not registered regID") errors.  So here is the chain of events:

1) Run (unchanged) php script to send notification
2) Notification sent/received succesfully
3) Run (unchanged) php script to send notification
4) Notification sent/received succesfully
5) Run (unchanged) php script to send notification
6) Get 3008 error.

As soon as I get that error once, any further attempts to send the notification fail w/a 3008 error until I uninstall and reinstall the app.  As soon as I reinstall, even though it creates the exact same regID, the push notifications start working again.  At least temporarily until they randomly stop again.

Any ideas?

Edited by: Brock Boland on 17 Mar, 2014 Reason: Paragraph tags added automatically from tizen_format_fix module.
List

Responses

4 Replies
Matt Alonso

Problem solved.  Looks like this only happened when the app was closed by ending the process in Task switcher.

Matt Alonso

Problem unsolved.  Probably a stupid question but does "tizen.push.registerService"  need to be called every time the app opens or only the first time it runs so that the initial regID is generated?

 

Thanks

Alexander AVSukhov

Hello,

Must be called once when you first start and after the call unregisterService.

Matt Alonso

Thanks for the quick reply. 

So by "first start", does that mean the first time a user *ever* opens the app, or do you mean it needs to be called each time the app is started?

Thanks!