[Post-Reading] I THINK ABOUT socketvoip, "the socket voip backend is rejected by Apple for long connection ".

[Post-Reading] I THINK ABOUT socketvoip, "the socket voip backend is rejected by Apple for long connection ".

[Post-Reading] I think about "Apple rejects socket voip background persistence"

Beautiful Life of the sun and fire god (http://blog.csdn.net/opengl_es)

This article follows the "signature-non-commercial use-consistency" creation public agreement

Reprinted please keep this sentence: Sun huoshen's beautiful life-this blog focuses on Agile development and mobile and IOT device research: iOS, Android, Html5, Arduino, pcDuino, otherwise, this blog post is rejected or reprinted. Thank you for your cooperation.

From the following point of view, Apple has now stepped out from the technical level and started to review the content.

So be careful when you want to steal your camera.

To maintain persistent connections in the background is nothing more than a channel for the server to directly communicate with the client. Although this real-time method is good, Apple is more concerned with user experience and user privacy.

The client ID is not directly connected. Although the UDID cannot be used, the unique UUID Generation ID method officially recommended by Apple is also good.

An application is installed on a device. The UUID is automatically generated and stored in the sandbox when it is run for the first time. This is enough to uniquely identify a device. More specifically, identifies the application on a device.

Logon authentication is an authentication method that uses the application. It cannot identify the current device.

By combining device identification and user information, you can fully determine which user is on which device to log on to and use this application. This should be a complete authentication, including subsequent lifecycle control.

Compared with Android, Apple is more suitable for stateless interaction management of short links. Each network request has a response and a network interaction. The request carries a source ID: device ID and user ID;

If you want to avoid the UUID long string, put your messy things in the automatic storage cabinet and get the number of a storage cabinet, there will be no error in getting this number directly, because the inventory Cabinet issued a uniform number, and the number is only two or three digits, and the UUID must be smaller than this.

Below are the translations and replies, both of which are very classical, followed by a link to the original text and title.

Some translations are as follows:

We found that your application uses the background mode, but does not contain any functions that require the persistent running of this mode. This behavior is incompatible with Apple Store review guidelines.

We have noticed that your application declares support for VOIP in the UIBackgroundModes key in the Info. plist file, but does not provide any VOIP service.

Reply Abstract:

Apple rejected socket voip background persistence ----- 2.16 -----

We found that your app uses a background mode but does not include functionality that requires that mode to run persistently. This behavior is not in compliance with the App Store Review Guidelines.

We noticed your app declares support for VoIP in the UIBackgroundModes key in your Info. plist but does not provide any Voice over IP services.

We recognize that VoIP can provide "keep alive" functionality that uses app features wowould like to use. however, using VoIP in this manner is not the intended purpose of VoIP, which, as indicated in the iOS Application Programming Guide, is that: "A Voice over Internet Protocol (VoIP) application allows the user to make phone callusing an Internet connection instead of the device's cellular service."

It wocould be appropriate to add VoIP features or remove the "VoIP" setting from the UIBackgroundModes key.