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 don't know if this is the right place to ask this.
I developed a library with Swift Package Manager that uses Apollo for network calls. The problem is that the Swift package manager does not allow the installation of remote packages with a local target SE-0201 60, this stops me from adding my Swift package to other applications. Apollo Schema uses a local target for adding a schema to the Swift package so there is a conflict. Is there any way around this?
The text was updated successfully, but these errors were encountered:
Hi @sa-ma - I'm not sure whether I understand your issue correctly.
What I think you're describing is that you're trying to distribute your own Swift package that uses Apollo iOS but as a local dependency? To do that you'd need to ensure that any project using your Swift package had already manually cloned the Apollo iOS repo to the path defined in your Package.swift file. This is not the way that Swift packages are meant to be distributed.
Why do you need a local dependency vs. the remote dependency?
Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo iOS usage and allow us to serve you better.
Question
I don't know if this is the right place to ask this.
I developed a library with Swift Package Manager that uses Apollo for network calls. The problem is that the Swift package manager does not allow the installation of remote packages with a local target SE-0201 60, this stops me from adding my Swift package to other applications. Apollo Schema uses a local target for adding a schema to the Swift package so there is a conflict. Is there any way around this?
The text was updated successfully, but these errors were encountered: