iOS Question NSBluetoothAlwaysUsageDescription - Missing Purpose String in Info.plist

[yiankos1]

Hello friends,
I tried to upload my app at iStore but i recieved this mail back

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 are 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 APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).

My app DOES NOT use Bluetooth at all. Here are libs that i use:

Do you think is from iPhone lib? I use this lib for two reasons: to open a pdf file and send a mail.
Thank you for your time.

p.s. My previous iStore upload (about 8 months ago) with exactly same libs, didn't send me this mail.
p.s.1 As i see HERE something changed at iOS 13

 

[Erel]

The user will never see that description so you don't need to worry about it too much. The description only appears when the relevant permission is requested.

 

[yiankos1]

The user will never see that description so you don't need to worry about it too much. The description only appears when the relevant permission is requested.

So the string explaining will be about which lib? And what am i supposed to write?

 

[Erel]

So the string explaining will be about which lib?

I'm not sure. The iPhone library has nothing to do with Bluetooth.

 

[Brandsum]

Hello friends,
I tried to upload my app at iStore but i recieved this mail back

My app DOES NOT use Bluetooth at all. Here are libs that i use:
View attachment 83997
Do you think is from iPhone lib? I use this lib for two reasons: to open a pdf file and send a mail.
Thank you for your time.

p.s. My previous iStore upload (about 8 months ago) with exactly same libs, didn't send me this mail.
p.s.1 As i see HERE something changed at iOS 13

I got the same error today while updating an app. I thought it was for the iBLE lib. But as per your screenshot its clear that it wasn't the lib but something else.

 

[Erel]

I thought it was for the iBLE lib

Does your app use the iBLE library?

 

[yiankos1]

I got the same error today while updating an app. I thought it was for the iBLE lib. But as per your screenshot its clear that it wasn't the lib but something else.

The problem is that if we state something random about bluetooth, then Apple Rejection is in our pocket at anytime...

 

[yiankos1]

Does your app use the iBLE library?

So Erel, what is our next step? If none of this lib contain bluetooth, maybe is b4i bug?

 

[Erel]

You can release it with a generic description. It will be surprising if it will cause the binary to be rejected. Nothing bad will happen if the binary will be rejected. You will return to the current point.

I'm sure that we will soon get more information about this (if it is indeed related to one of the internal libraries).

 

[Erel]

I assume that you received this email after you uploaded the build and you haven't submitted it to review, right?

I've just uploaded a binary of an app with the following libraries:

I received the usual warning email about missing push notifications entitlement. The binary wasn't rejected.

 

[yiankos1]

I assume that you received this email after you uploaded the build and you haven't submitted it to review, right?

Exactly! I can forward mail if this could help. So, if I contrast my libs and yours, I think that would be another lib. Maybe admob or Firebase analytics? If you want, I can send you whole project privately.

 

[Erel]

No need to send anything. It probably comes from Firebase or AdMob SDKs (not the wrappers).

 

[Brandsum]

Does your app use the iBLE library?

Yes. For beacon tracking. After processing the uploaded binary it got rejected and received the email. Then I added that description and the binary got approved.

 

[David Meier]

I got the same error, when updating my app yesterday. Happily I saw this thread and did accordingly. I added:

    #PlistExtra: <key>NSBluetoothAlwaysUsageDescription</key><string>Used to integrate gmap framework.</string>

I could so upload the app without errors and I submit the update for reviewing. Now I am waiting for the ok from the reviewing team. I keep you updated.
Thx for everybody contributing in the above posts!
Cheers David

 

[David Meier]

I got the same error, when updating my app yesterday. Happily I saw this thread and did accordingly. I added:

    #PlistExtra: <key>NSBluetoothAlwaysUsageDescription</key><string>Used to integrate gmap framework.</string>

I could so upload the app without errors and I submit the update for reviewing. Now I am waiting for the ok from the reviewing team. I keep you updated.
Thx for everybody contributing in the above posts!
Cheers David

My App update got approved! So it is working with the above mentioned practice.
Regards
David

 

[angel_]

I have the same problem, but I am not using bluetooth.

 

[David Meier]

I have the same problem, but I am not using bluetooth.

View attachment 84098

View attachment 84097

Neither do I use bluetooth. But with the above solution you can submit your app.

 

[Andrew (Digitwell)]

Yup, same here. Thanks for the tip. Any idea which library is causing this?

 

[Erel]

It probably comes from Firebase SDK.