Closed rodrigojrmartinez closed 5 years ago
Are you using Phone Gap to build your apps? If so, Phone Gap essentially ignores the preference and downloads the entire plugin. I had to build the iOS version in Xcode. Others have used a forked version of the plugin. (I'd add a link but I can't find it at the moment.)
I'm using ionic actually and cordova beneath it, with the following command
ionic cordova build ios
I am having the same issue, any solution?
Same error for me. Using ionic 4 / XCode 11.1 / iPhone iOS 13.1 this error appear when upgrading iOS version of iPhone into 13.+
If you aren't using PhoneGap it may be that the bluetooth plugin is still present. I had to remove the plugin, remove the platform, make sure the preference is set in config.xml, then add the plugin, then add the platform.
Thank you @attebury it's good for me !
Okey, I finally got it. It wasn't enough to just uninstall and re-install the plugins & module but also the platform as well, so for anyone having this issue and to make it as clear as possible, you should
ionic cordova platform remove ios
npm uninstall @ionic-native/diagnostic
ionic cordova plugin remove cordova.plugins.diagnostic
<preference name="cordova.plugins.diagnostic.modules" value="LOCATION" />
ionic cordova plugin add cordova.plugins.diagnostic
npm install @ionic-native/diagnostic
ionic cordova platform add ios
ionic cordova build ios
@rodrigojrmartinez Thanks. It worked!
@rodrigojrmartinez Thanks. It worked!
The preference cordova.plugins.diagnostic.modules is not working with ionic@2 & cordova@6. I followed @rodrigojrmartinez steps but all modules are present in platforms/ios/YOUR_APP/Plugins/cordova.plugins.diagnostic folder. The plugin version i'm using is 4.0.8 due to cordova@6.5.0 compatibility. @dpa99c Any clues on this? Thanks!
@molinet88 I suggest updating to latest cordova
(CLI) and cordova-android
(platform) versions then you can update to the latest version of this plugin.
@dpa99c Yes, but I wanted to skip this solution because it's too aggressive to all project dependencies.
Just to clarify, since plugin version 4 the modules
preference should work, isn't it?
In theory it should work but I can't support such old versions of the plugin so if you're having issues, you'll need to resolve them yourself.
Sure, it's a mess to use old versions...
I finally solved it updating cordova CLI
to latest version (9.0.0) and using plugin version 4.0.8 (due to cordova-android@6.1.2
compatibility).
That way the modules
preference is working fine!
Thank you :)
Hi, I'm building an Ionic 4 app meant for both Android and iOs and recently I've been starting to receive a warning from Apple App Store Connect regarding a missing purpose on why I'm using bluetooth information on my App. For my case I'm not using it at all and I've read the 'Specifying modules' section of the readme, so I know this comes by default when installing the plugin. I've tried to do what it's suggested in this section so as to avoid having this warning
So what I've done now is to add this line over my config.xml
Since this is the only information I've been retrieving for the app. Also I have a merge for Info.plist to specify why I need the location as follows:
I have removed the plugin and uninstall the ionic dependency as well and then reinstall it with the following commands
Which updated my package.json with the latest versions, Then I've build the app for ios just fine, then I check for the ios.json generated file and I can't find the 'NSBluetoothAlwaysUsageDescription' description on the "*-Info.plist" information (though I can see that there are other values such as NSCamaraUsageDescription, NSMicrophoneUsageDescription, etc. which I'm also not using). Then there's an entry for config.xml parents where I can indeed see
At the end when submitting the app to the App Store for testing purposes I still receive the usual warning:
Am I doing something wrong? I wouldn't want to add a description of the use of data I'm not taking into account for my app since it would be a lie and I run the risk for my app to be rejected when publishing it for real. Some advice for avoiding this?
Thanks a lot!