Closed PasqualePuzio closed 5 months ago
We are checking that. We keep you posted.
We are doing our best to release the change today. We will keep you posted.
Any update on this? https://github.com/teads/TeadsSDK-iOS/issues/241#issuecomment-2084590347
kindly provide an update for this as today is the last day to fix these warnings
Sorry for the inconvenience but we have a new ETA for next Thursday May 2. Anyway we are doing our best to release it as soon as possible.
Same issue that we reported here: https://github.com/teads/TeadsSDK-iOS/issues/232
Thanks for the update @github-lucas-bon, we will wait for the update on Thursday.
We deployed a new SDK v5.1.3
that fix the issue with in Privacy Manifest with API NSPrivacyAccessedAPICategoryUserDefaults
.
Let us know in case of any other issue. Thanks for you patience.
Hi,
after submitting our app to the iOS AppStore, we received the following warning.
I think you should be able to easily fix it by removing C617.1 at line 27 in here https://github.com/teads/TeadsSDK-iOS/blob/master/Frameworks/TeadsSDK.xcframework/ios-arm64/TeadsSDK.framework/PrivacyInfo.xcprivacy
ITMS-91055: Invalid API reason declaration - The PrivacyInfo.xcprivacy for the “Frameworks/TeadsSDK.framework/TeadsSDK” file contains “C617.1” as the value for a NSPrivacyAccessedAPITypeReasons key instead of a valid reason code for using an API in the NSPrivacyAccessedAPICategoryUserDefaults category. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, values for NSPrivacyAccessedAPITypeReasons keys in your app’s privacy manifest must be valid reason codes for the corresponding API category.