07-19-2012 03:57 PM
Any way for sniffing traffic at DebugPortal?
Currently I can only tell you what I see at the UI:
Subscriber Id: 9810
Application Id: (correct value)
Status in SDK: ACTIVE
Status in PPG: ACTIVE
I currently do not have a custom solution for that type of query in order to see traffic.
07-19-2012 03:59 PM
No, you will need to send a PAP request to the server. This is what was explained earlier, I thought you did this as you stated : "Somehow it gets de-registered at the PPG." which can only be known if you query the PPG.
07-19-2012 04:03 PM
isn't the "Query status in PPG" option in DebugPortal supposed to do that?
What does that option really do? what does it really debug?
Also tried "Sync status with PPG". Returns ACTIVE.
Can you please provide a PAP request example in order to continue testing?
07-19-2012 04:07 PM
Included in the message I posted right before your first post:
07-19-2012 04:11 PM
It's still unclear what's the DebugPortal for, then. And why does example software not work as it's supposed to. This means less productive. development hours.
Will try what you are suggesting and reply.
07-19-2012 04:14 PM
It should work as expected. I'd rather not speculate on what the issue may be until we have enough information to make an educated decision. The faster you respond with the requested info the faster we should hopefully be able to get you an answer on why the failures are occurring.
Speculation at this point will not help with getting you an answer.
07-19-2012 04:24 PM
I agree on speculation drives nowhere. In that way I also think RIM always speculates it's the developer fault and that's the reason we are still discussing on a two years old unresolved ticket.
I hope you don't find I'm blaming on you personally. I want to get this fixed and I'm eager to spend some more hours.
Can you please provide the PPG resource part of the URL the request should be sent to? it's not in the code sample.
07-19-2012 04:30 PM
The push goes to the same URL that you use for your pushes.
This same code is working for many, many applications in market. If it did not work for anyone when there would be many more complaints and the code would have been re-written. I'm not saying there's no issue with the code, just stating that there is some due diligence that needs to be done at the developer's end to narrow down the issue before pointing fingers in any direction.
07-19-2012 04:55 PM
It's encouraging to know there are so many 3rd party push-enabled apps working perfect at the App World, a motivation to find a solution for this.
Here are my results (removed app ID and PINs for security)
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.1//EN"
<bpds version="1.0"><subscriptionquery-response pushservice-id=".............."><subscriptionquery
It seems to be ACTIVE for the 9810 device I'm having problems (PIN listed), like PPG query from DebugPortal
07-19-2012 05:00 PM
Looking at the 4.6 demo app on the 7.0 9810 device, I found an interesting line
"Failed to read push message, caused by null"
Note I'm using the DebugPortal to initiate pushes, not the custom script.