This is the seventh day of my participation in the August More text Challenge. For details, see: August More Text Challenge.

In recent two days, apple have updated the new equipment, also update the new system, including also updated the Xcode, apple released new product every year and the new system will cause some changes, for iOS developers generally met with the pit, not this year is no exception, the day before yesterday in the packaging on a regular version, was turned down.

The reason is as follows:

We identified one or more issues with a recent delivery for your app, Please correct the following issues, Then upload again. Itms-90683 :Missing Purpose String in info.plist-your app's code References one or more APIs that Access sensitive user data. The app 's Info. Plist file should contain a NSBluetoothAlwaysUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data.Starting Spring 2019, All apps submitted to the App Store that access user data is required to include a purpose string. If you're using external libraries or SDKs,they may reference APIs that require a purpose string.While your app might not use these APIs, a purpose string is still required.You can contact the developer of the library or SDK and request they release a Version of their code that doesn't contain the APIsCopy the code

Email icon:

The translation is as follows:

Just beginning to see the rejection reason to feel wulitou, because bluetooth until the permissions are no problem, and the prompt “NSBluetoothAlwaysUsageDescription” haven’t met before, as shown in figure:

When I entered the beginning letter in the PList file, there was no prompt, I thought it was a bluetooth description problem. As a result, I modified the Bluetooth description text and submitted the version, but it was still rejected. Moreover, after several times of submission, the version was directly deleted by Apple background and could not be found, as shown in the picture:

 

And then to find the latest news in the official API directly, the results found the reason, iOS13 abandoned the previous bluetooth permissions, new NSBluetoothAlwaysUsageDescription permissions, prompt official API is as follows:

 

I then added the key-value pair to the plist file, as shown in the figure below:

 

Finally, recompile and solve the problem, as follows:

Although this is only a new problem encountered, but at the beginning of everyone will be at a loss, so I shared it with everyone. The above is all of this chapter, welcome to pay attention to three shopkeeper’s wechat public number “program ape by three shopkeeper”, three shopkeeper’s Sina Weibo “three shopkeeper 666”, welcome to pay attention!