hengsokchamroeun / javapns

Automatically exported from code.google.com/p/javapns
0 stars 0 forks source link

APNS feedback service does not return inactive device(s) during the first try APNS push #52

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. Install MDM configuration profile 
2.  APNS push succeeed
3.  remove configuration profile
4.  APNS push failure, that is expected. 
5.  feedbackManager.getDevices ,  inactive devices.size() is 0

What is the expected output? What do you see instead?

inactive devices.size() shoudl be 1
repeat 4 and 5,  start from the second try,  inactive devices.size() is 1

What version of the product are you using? On what operating system?
javaapns-jdk16-163.jar  window 7  and JDK 1.6

Please provide any additional information below.

Original issue reported on code.google.com by innoip...@gmail.com on 2 Jun 2011 at 8:13

GoogleCodeExporter commented 8 years ago
I've been told it works, but I have no way of testing it. Maybe someone else 
can fill in with more info.

One things to note:
- When using the sandbox server, no feedback devices will be returned

Original comment by idb...@pugetworks.com on 6 Jun 2011 at 10:09

GoogleCodeExporter commented 8 years ago
I am testing production server.   The feedback inactive devices are returned 
only on and after the second push 

Original comment by innoip...@gmail.com on 7 Jun 2011 at 6:49

GoogleCodeExporter commented 8 years ago
I can not get the return devices too. I use the javaapns-jdk16-161.jar window 7 
 and JDK 1.6.
What is the problem? who can provide some advise?

Thanks.

Original comment by jsonzhu...@gmail.com on 8 Aug 2011 at 2:30

GoogleCodeExporter commented 8 years ago
Since Apple does not specify precisely when a device will end up on the 
Feedback list (ie how many failed push must occur or how much time must elapse 
before it is marked as inactive), I believe that what you are seeing is the 
normal behaviour of Apple's Feedback Service.

We must not forget that the whole purpose of having an asynchronous Feedback 
Service to detect inactive devices instead of simply receiving error codes 
while pushing notifications is because Apple has a lot of factors to consider 
before listing a device as inactive...  If a notification can't be pushed, it 
can be because of network issues, device issues, bad reception issues, 
configuration issues, etc.  but if any of these problems arise, it does not 
necessarily mean that the device is permanently inactive...  it may simply be a 
temporary situation.

Considering that the observed behaviour meets Apple's blurry description of how 
the Feedback Service works, and seeing the devices do eventually get on the 
Feedback list, I'm closing the issue as Won't Fix. Please feel free to re-open 
with more details if the issue is still valid.

Original comment by sype...@gmail.com on 7 Sep 2011 at 4:12