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
We've recently migrated our project from the legacy Amplitude SDK to this Swift one. We're using SPM for dependency management. I'm seeing continual problems with Xcode failing to resolve the Amplitude-Swift package, various combinations of resetting caches, purging derived data and so on will typically get the project to a working state but as it breaks every time branches are switched or even on restarting Xcode this is not a very desirable workaround. I've never had an issue like this with a Swift package before; Xcode will literally go into a loop of checking out the package and deleting it until packages are reset.
When it's in a working state Xcode will still show this warning:
We're also using the session replay plugin and experiments SDKs so I don't know if there's a possibility it's some kind of interaction between these? I see the session replay SDK has dependencies on both the Swift and legacy SDK which the experiments one does not.
Do you folks have any idea what could be the issue? I'm assuming this is not affecting everyone or the issue would have been raised already.
The text was updated successfully, but these errors were encountered:
Hi @roryprior - we've tried to reproduce this in a few variations with no luck on our end. We can take a closer look if you are able to share some minimally reproducing example.
We've recently migrated our project from the legacy Amplitude SDK to this Swift one. We're using SPM for dependency management. I'm seeing continual problems with Xcode failing to resolve the Amplitude-Swift package, various combinations of resetting caches, purging derived data and so on will typically get the project to a working state but as it breaks every time branches are switched or even on restarting Xcode this is not a very desirable workaround. I've never had an issue like this with a Swift package before; Xcode will literally go into a loop of checking out the package and deleting it until packages are reset.
When it's in a working state Xcode will still show this warning:
We're also using the session replay plugin and experiments SDKs so I don't know if there's a possibility it's some kind of interaction between these? I see the session replay SDK has dependencies on both the Swift and legacy SDK which the experiments one does not.
Do you folks have any idea what could be the issue? I'm assuming this is not affecting everyone or the issue would have been raised already.
The text was updated successfully, but these errors were encountered: