Reliability of silent push
A chat app is built to wake up on a silent push (content-available) for each new message and sync ahead of time, but the data says more than half never arrive or arrive late. Why is that happening?
A chat app is built to wake up on a silent push (content-available) for each new message and sync ahead of time, but the data says more than half never arrive or arrive late. Why is that happening?
A silent push is low priority (apns-priority 5), delivery and execution aren't guaranteed, the system throttles it by app usage and battery, and it doesn't come at all after a force quit or in Low Power Mode.
App lifecycle and systemShort answerIntro
A user is working in your app, takes a phone call, hangs up, goes out to the home screen…
#background
App lifecycle and systemShort answerBasics
You get a report that a save to the server never lands when the user taps save and goes…
#background
App lifecycle and systemShort answerBasics
Can you walk me through the whole path a single remote push takes to reach a user's…
#apns
App lifecycle and systemShort answerAdvanced
A requirement comes in: "every night while the user sleeps, clear the cache and prefetch…
#background