Comments (5)
'If a provider attempts to deliver a push notification to an application, but
the application no longer exists on
the device, the device reports that fact to Apple Push Notification Service.
This situation often happens when
the user has uninstalled the application. If a device reports failed-delivery
attempts for an application, APNs
needs some way to inform the provider so that it can refrain from sending
notifications to that device. Doing
this reduces unnecessary message overhead and improves overall system
performance.
For this purpose Apple Push Notification Service includes a feedback service
that APNs continually updates
with a per-application list of devices for which there were failed-delivery
attempts. The devices are identified
by device tokens encoded in binary format. Providers should periodically query
the feedback service to get the
list of device tokens for their applications, each of which is identified by
its topic. Then, after verifying that the
application hasn’t recently been re-registered on the identified devices, a
provider should stop sending
notifications to these devices.
Access to the feedback service takes place through a binary interface similar
to that used for sending push
notifications. You access the production feedback service via
feedback.push.apple.com, port 2196; you access
the sandbox feedback service via feedback.sandbox.push.apple.com, port 2196. As
with the binary interface
for push notifications, you should use TLS (or SSL) to establish a secured
communications channel. The SSL
certificate required for these connections is the same one that is provisioned
for sending notifications. To
establish a trusted provider identity, you should present this certificate to
APNs at connection time using
peer-to-peer authentication.
Once you are connected, transmission begins immediately; you do not need to
send any command to APNs.
Begin reading the stream written by the feedback service until there is no more
data to read. The received data
is in tuples having the following format:
time, token length, token id'
This would indicate to me that there is no way to discern between failed
connectivity issue and a removed app.
Original comment by [email protected]
on 27 Apr 2010 at 4:33
from javapns.
Original comment by [email protected]
on 27 Apr 2010 at 4:36
- Changed state: New
- Added labels: Priority-Low, Type-Enhancement
- Removed labels: Priority-Medium, Type-Defect
from javapns.
very clear!
Thanks
Original comment by [email protected]
on 27 Apr 2010 at 9:39
from javapns.
Original comment by [email protected]
on 27 Apr 2010 at 10:42
- Changed state: WontFix
from javapns.
FYI, There was a company called Pinch Media, that recently became Flurry:
Analytics that would track app installs.
http://www.flurry.com/product/analytics/index.html
Now for the down side... Apple's new policy doesn't allow any analytics so that
won't work... but that would
indicate that Apple is gearing up provide their own version.
Bill
Original comment by [email protected]
on 28 Apr 2010 at 10:04
from javapns.
Related Issues (20)
- invalid token error HOT 5
- encountered "KeystoreException (Keystore contains too many certificates)" HOT 3
- Apple dropping support for SSL 3.0 on push notification servers, requiring TLS by October 29th HOT 3
- JavaAPN can't work on Windows but Mac OS is fine, why???? HOT 3
- Feature request: configurable or parameterized time waiting on socket HOT 4
- Feature request: configurable or parameterized retry policy HOT 3
- Creating certificates step-by-step link broken HOT 1
- thread terminated after reached max msg send HOT 3
- Exception reporting not working for multiple payloads
- Responses not read? HOT 1
- Javapns Communication exception:Connection refused to ConnectionToAppleServer
- support for title-loc-key (ios 8.2)
- Unable to connect APNS - CommunicationException - java.net.ConnectionException : Communication Timed Out HOT 2
- Duplicate notifications being sent out at high rate
- Add content-available to PushNotificationPayload
- Do you support VoIP push notifications?
- javaapns does not supports log4j 2
- Exception java.net.SocketException
- Javapns Notifications SSL Exceptions and Closed Sockets HOT 1
- thead lake
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from javapns.