iOS Application Bluetooth Permission

Is it possible for the Bluetooth permissions of an app to be turned off due to changes in the iOS application's Bluetooth library, possibly because of Apple's security requirements or OS-related factors?

There are two applications, Application A and Application B, that control Bluetooth devices. Application A uses a third-party Bluetooth library to control the Bluetooth devices. Application B also uses a third-party Bluetooth library to control the Bluetooth devices.

The Bluetooth libraries used by Application A and Application B are different, but both applications work without any issues. However, when the Bluetooth library used in Application B was changed to the one used in Application A, the Bluetooth permissions for Application B sometimes turned off.

Since Application A and Application B operate without any issues on their own, we believe the problem is not with the Bluetooth libraries themselves. Given the above situation, is it possible that changing the Bluetooth library used could cause the Bluetooth permissions of the app to be turned off due to Apple's security requirements or OS-related factors?

This question is too abstract to guess what the problem might be.

For starters, what do you mean by “permissions turned off”. Did this app have permissions before in Settings, and now when you look they are turned off? If that’s the case, this might be a user level change. Did the users delete the app and reinstall the new one? Could they have turned the permissions off themselves? Is the Bundle ID of the app still the same?

Or is it that the new app suddenly started to ask for permission? This could happen if the app has been built a while ago against an older iOS SDK, before Bluetooth permissions were required, and now with the new build they have become obligatory.

You say the apps don’t have issues on their own? What does that mean, that the permission gets turned off when both are running?

if the permission is off, does everything work ok if the user turns it back on?

Perhaps the new library is using a function that the old one didn’t. In any case this is not something that looks like it would be related to the OS or the framework unless, like I said above, it is a matter of linking against an old SDK vs a new one with the new app. Hard to tell.


Argun Tekant /  DTS Engineer / Core Technologies

iOS Application Bluetooth Permission
 
 
Q