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.