#iOSDev What's the proper way of handling Required Reason APIs when the API in question is only referenced by a part of a #swift package dependency that I'm not ever calling?
None of the usage reasons fit – there's no way to declare “this is only linked because a dependency references it, but I pinky promise my app doesn’t actually call it”
@dale_price I'd work with the package maintainer to make that part of the package optional. In the short term, I'd consider forking, removing the problematic code, and using my fork until the changes can be upstreamed.
Add comment