There was an update via firebase/firebase-ios-sdk#10582 which:
"Prevent keychain pop-up when accessing Firebase Auth keychain in a Mac app. Note that using Auth in a Mac app requires that the app is signed with a provisioning profile that has the Keychain Sharing capability enabled (see Firebase 9.6.0 release notes) (firebase/firebase-ios-sdk#10582)." (see https://firebase.google.com/support/release-notes/ios#version_1050_-_february_7_2023).
This is a breaking change if (i) an Apple Developer team has not been applied to the flutter macOS app, and (ii) Keychain Sharing capability has not been enabled (as a result of i above) - as it stops Firebase Auth from being able to login. In our case, we did not make any changes to the Firebase Auth Flutter package version, carried out flutter run and Firebase Auth can no longer log users in. This is a breaking change, so it may have been a good idea to push this out in a major release, and at a bare minimum throw an error if i and ii are not met above - so the developer experience is great and days of time are not spent debugging and then stumbling on the above release article, as in our case.
There was an update via firebase/firebase-ios-sdk#10582 which:
"Prevent keychain pop-up when accessing Firebase Auth keychain in a Mac app. Note that using Auth in a Mac app requires that the app is signed with a provisioning profile that has the Keychain Sharing capability enabled (see Firebase 9.6.0 release notes) (firebase/firebase-ios-sdk#10582)." (see https://firebase.google.com/support/release-notes/ios#version_1050_-_february_7_2023).
This is a breaking change if (i) an Apple Developer team has not been applied to the flutter macOS app, and (ii) Keychain Sharing capability has not been enabled (as a result of i above) - as it stops Firebase Auth from being able to login. In our case, we did not make any changes to the Firebase Auth Flutter package version, carried out flutter run and Firebase Auth can no longer log users in. This is a breaking change, so it may have been a good idea to push this out in a major release, and at a bare minimum throw an error if i and ii are not met above - so the developer experience is great and days of time are not spent debugging and then stumbling on the above release article, as in our case.