Upload Privacy Policy

[sagarthecoder]

Apple says "Starting May 1, 2024: You'll need to include approved reasons for the listed APIs used by your app's code to upload a new or updated app to App Store Connect."

Please add privacy policy otherwise we couldn't use this library.

[fury21]

+1

[BenoitDeguine]

+1

[nts0311]

+1, We're close to May 1st. Can we override Alamofire version in pod or spm?

[TeeNT1]

+1. Moya is a wonderful library. I really hope it will continue to be maintained and further developed.

[Shannon-Yang]

+1

[zxhkit]

+1

[SherifShokry123]

+1

[manuelsalinas-mx]

+1

[muruganandham]

+1

[lukeleleh]

As Alamofire and RxSwift dependencies are listed here and Moya repackages them, Moya is included in the requirement.

I checked the internal constraints that Moya is setting internally for these dependencies and they're flexible, so you can explicitly add the dependencies version needed that has the privacy manifest in your project and the project should resolve them successfully.

In this case, the privacy manifest is added to these dependencies in these specific versions:

• Alamofire: 5.9.0
• RxSwift: They specify here that it seems it's not needed because they don't receive any API messages after submitting your app for AppStore or external TestFlight

Considering the Alamofire dependency, if you add manually version 5.9.0 to your project, Moya should use this version, which has the privacy manifest and I guess it should work to address the issue. If that's the case, I hope this helps!

[mhaashim]

Considering the Alamofire dependency, if you add manually version 5.9.0 to your project,

@lukeleleh I have updated the alamofire version to 5.9.0 in my main project using pod update. But I still got the warning from the Apple. I think Moya should only update the alamofire version to 5.9.0