Sunday, December 15, 2024
HomeiOS Developmentswift - Dealing with Privateness Manifests for Third-Get together Dependencies in iOS...

swift – Dealing with Privateness Manifests for Third-Get together Dependencies in iOS Initiatives


I’ve an iOS challenge that depends on a number of third-party dependencies, together with RxSwift, which at the moment doesn’t have a privateness manifest. I’ve a couple of questions relating to this case:

  1. What ought to builders do if a dependency lacks a privateness manifest? Are there finest practices for assessing and managing such dependencies?

  2. Is the absence of a privateness manifest relevant solely to new apps or new dependency additions? My utility is older and already contains these dependencies.

  3. If a dependency (e.g., dependency1) has launched a brand new model (2.0) with a privateness manifest, however I can’t improve resulting from compatibility points with different dependencies, what steps ought to I take? How can I optimize my challenge whereas addressing this concern?

Any insights or suggestions can be drastically appreciated!

RxSwift open concern: https://github.com/ReactiveX/RxSwift/points/2625

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments