-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug(barcode-scanning): missing privacy manifest #178
Comments
According to the changelog, the latest version for |
Hi! I updated the GoogleMLKit/BarcodeScanning to 6.0.0 manually and ran pod update.
The privacy policy was added on version 4.2.0 for GoogleToolboxForMac. |
I have created a PR to update the pods: #179. Unfortunately, it contains breaking changes, so I can't merge the PR yet. You can use the pre-release in the meantime:
|
Closed by #179. Please install the latest version using the
|
While updating to ^7.0.0-next.1, I'm receiving this error:
To correctly build the application, I had to increase the iOS platform version in my Podfile to: Is this supposed to be correct? |
@geckozr Yes, see BREAKING.md. That's the reason why we can't publish a new latest version before the next major release. |
@robingenz can you manage to merge the fix for GoogleMLKit/BarcodeScanning in version 6, please? My project cannot increase the the IOS platform version to 15.5; I believe it is the same for many others. |
@hoangqwe159 That's the problem. We have to increase the minimum deployment target to be able to merge it. This is a requirement from the ML Kit Barcode Scanning SDK. |
- use mlkit/7.0 @next.2 see capawesome-team/capacitor-mlkit#178 - because of this bumb ios mimum target from 13.0 to 15.5
Plugin(s)
Current problem
When I push my app to apple there is always this warning about privacy
Preferred solution
I think this is due to dependency to MLKIT (which is dependent to an old version of GoogleToolboxForMac) version which is 5.0.0 currently and should be at least 6.0.0 or even 7.0.0.
On those latest versions the privacy issue is fixed.
Is it possible to update podspec to fix this or another solution in mind ?
Alternative options
No response
Additional context
Using current latest version of package 6.1.0
Before submitting
The text was updated successfully, but these errors were encountered: