You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using AlamofireObjectMapper version 6.2 in my Swift project, which automatically includes Alamofire 5.0.0-rc.2. However, I need to use Alamofire version 5.9 due to its support for the 'Privacy Manifest', which is crucial for my project. Is there a way to update AlamofireObjectMapper's dependency to accommodate Alamofire 5.9, or could you suggest a workaround?
Thank you for your assistance and for the great work on AlamofireObjectMapper.
Best regards,
Kashyap
The text was updated successfully, but these errors were encountered:
Hello @KKakadiyaKashyap, Did you solve this?
Actually I have also received an email from apple: ITMS-91061: Missing privacy manifest - Your app includes “Frameworks/Alamofire.framework/Alamofire”, which includes Alamofire, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests.
I have only this pod in my podFile: pod 'AlamofireObjectMapper', '~> 5.2'
"Hello,
I'm currently using AlamofireObjectMapper version 6.2 in my Swift project, which automatically includes Alamofire 5.0.0-rc.2. However, I need to use Alamofire version 5.9 due to its support for the 'Privacy Manifest', which is crucial for my project. Is there a way to update AlamofireObjectMapper's dependency to accommodate Alamofire 5.9, or could you suggest a workaround?
Thank you for your assistance and for the great work on AlamofireObjectMapper.
Best regards,
Kashyap
The text was updated successfully, but these errors were encountered: