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
{{ message }}
Repository navigation
Xcode fails to resolve dependencies when Flutter plugin uses relative path for their target's source #184021
This happens because plugins are symlinked in the same directory (introduced in #168932).
This pattern is not part of our migration guide, so I'm not sure why plugin authors are migrating this way. A couple example I found of people doing this:
For migrations that aren't following our instructions and are wrong, we'll probably need to mostly rely on package clients who start trying to use SwiftPM reporting issues to the package authors.
changed the title [-]Xcode fails to resolve dependencies when Flutter plugin uses relative path for[/-][+]Xcode fails to resolve dependencies when Flutter plugin uses relative path for their target's source[/+]on Nov 17, 2026
Activity
stuartmorgan-g commentedon Mar 23, 2026
For migrations that aren't following our instructions and are wrong, we'll probably need to mostly rely on package clients who start trying to use SwiftPM reporting issues to the package authors.
hellohuanlin commentedon Mar 26, 2026
@vashworth could you elaborate more about why this happens and how it is related to #168932?
vashworth commentedon Nov 9, 2026
There are other common errors we should parse for while we're at it. See https://github.com/flutter/flutter/pull/185218/changes#diff-36249c33b621961707281e68ef03fab89a7dc384c322fdc9d173065ae9e1b7a5R407
[-]Xcode fails to resolve dependencies when Flutter plugin uses relative path for[/-][+]Xcode fails to resolve dependencies when Flutter plugin uses relative path for their target's source[/+]