Ios beacon

Question

As stated in Apple's docs, a range of beacons can only be performed in the background for a short period of time, for example, up to 10 seconds by default or up to 3 minutes using the background task expiration handler. As is the case with my application, the application should make a beacon within every 15 minutes, until the user leaves the region. I mean to use a background push notification (silent push notification) for this purpose (provided that a data connection is always available on the device). Thus, the flow is as follows: when the user enters the region, the application calls the server with the device token, the server sends a quiet push notification every 15 minutes. After the application has received a push notification, it will be a beacon for a valid period of time, if necessary. Question: I mean, whether using push notification in the background to make the ranking legal, I will encounter any problems during the presentation of the application store.

Note I also need to enable BLE background mode for the application in order to read some specifications from some BLE devices.

Answer 1

If you use one of the background modes incorrectly, the application will probably be rejected, saying that I do not think that silent push notifications were intended to: keep the iOS application in the "Background" state by sending it a quiet push notification every few minutes.

Another thing is that silent push notifications are limited in speed, as described by http://asciiwwdc.com/search?q=push+notification , so I'm not sure if they will be sent every few minutes.

Apple says that:

Silent notifications are not intended for your application to wake up in the background, and they are not intended for high-priority updates. APNs views silent notifications as a low priority and may if the total becomes excessive. These limits are dynamic and may vary depending on conditions, but do not try to send multiple notifications per hour.

Answer 2

Technically, you can do this, but Apple basically rejects such an application. One important thing you should consider is that if the application was manually killed by the user and does not work in the background, the application will not wake up with a quiet push notification. There is a workaround if you have VoIP alerts that it will wake the application even from a termination state. But you may need a strong reason, while pushing it toward the AppStore.

Answer 3

You might want to see this article . The user talks about apps that use silent notification to trigger location tracking. But ultimately it ’s a hack that Apple may reject some time in the future , so it’s best to have a contingency plan. FWIW so far I have not heard anyone report a denial.

So the official answer does not do this because you can refer to Ashish's answer . Unofficial answer: if you can’t change your business logic, do it at your own risk.

Answer 4

There is an exact thing in the iOS application I'm working on, except that I use the record instead of Beacon. IOS standards recording gives more problems when you click an application in the app store.

But Apple has not rejected this application. Although we still encounter some problems, they are not related to your problem. You can follow this guide for further help besides the answer you were looking for: iOS Push Notification Demysitfied

In addition, I cheated on local notifications while the application is in the background. BLE even works if the application was killed by the system, when the OS receives some communication from your peripheral or central device, iOS wakes up your application and performs the desired function before returning your application again.