I got around this by adding another dependency which caused Xcode to somehow also cause a change for an unrelated package in the Package.resolved file which was already there. Just asking Xcode to resolve packages wasn't enough to trigger this.
johankool
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
From
Rotterdam, Netherlands