iOS Package.resolved churn across machines with same Flutter app

[AlexDochioiu]

What happened?

In a Flutter iOS project, ios/Runner.xcworkspace/xcshareddata/swiftpm/Package.resolved changed unexpectedly on one machine, while a teammate did not see the same change.

The file changed to a different Swift package resolution (example from my local diff):

• flutterfire changed from 4.5.0-firebase-core-swift to 4.4.0-firebase-core-swift
• csqlite was added
• swift-collections was removed

This looked like non-deterministic SwiftPM resolution across environments.

Steps to reproduce

1. Open a Flutter app with Firebase plugins on iOS (ios/Runner.xcworkspace).
2. Trigger package resolution in Xcode.
3. Compare Package.resolved with a teammate on a different machine.

Expected results

Package.resolved should be stable for the same Flutter dependency set, or Flutter tooling should avoid unexpected churn in this file.

Actual results

One machine got Package.resolved changes while another did not.

Workaround

Running these commands removed the local Package.resolved diff in my case:

• flutter clean
• flutter pub get

Version

Flutter 3.41.3 (stable)
Dart 3.11.1
Xcode 26.3 (Build 17C529)
Swift 6.2.4

Additional context

Could this be caused by toolchain-specific SwiftPM resolution differences? If yes, is there recommended guidance from Flutter to avoid Package.resolved churn between teammates?

[stuartmorgan-g]

This looked like non-deterministic SwiftPM resolution across environments.

It's not clear what exactly the steps to reproduce this were. Are you saying you both ran pub get with the same pubspec.lock and the same SwifwPM flag setting, and got different results?

Running these commands removed the local Package.resolved diff in my case:

• flutter clean
• flutter pub get

This sounds like you may have been doing SwiftPM resolution with different pub package versions, which would be expected.

Could you provide clear steps to reproduce from a clean state? The steps here aren't specific enough to be repeatable.

[AlexDochioiu]

Same everything (same flutter version, same xcode version, same cocoapods version, same pubspec.yaml and pubspec.lock). On my machine it was downgraded SwiftPM dependencies because it was not aware of them (I guess some cache). After running flutter clean and flutter pub get, it started accepting the same Swift PM deps like the other machine.

Note: I think that the deps being downgraded/etc, were not directly Swift PM packages coming from flutter deps. Rather, they were (newer versions of) transitive Swift PM deps of the existing Flutter deps.

[mbcorona]

Hi @AlexDochioiu

Thanks for the additional context regarding the environment. However, to properly investigate this, we still need the exact, step-by-step instructions to reproduce the issue starting from a clean state (e.g., the specific commands run in sequence). Could you please provide those steps?

[sharifm-informatica]

in my project firebase packages (setup by flutterfire for FCM) were the ones upgraded and downgraded almost every build

[github-actions]

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now.
If you find this problem please file a new issue with the same description, what happens, logs and the output of 'flutter doctor -v'. All system setups can be slightly different so it's always better to open new issues and reference the related ones.
Thanks for your contribution.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.