-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auth not Shared Correctly with App Groups #6876
Comments
Hey there! I've filed b/172260275 to track this issue internally. |
@malcolmdeck could this be related to why on the Mac I am getting a token mismatch but on iOS with the same bundleID— it works fine when using Auth() for phone login? |
Did anything come of this? When you say "shared app group", does that include an extension within the main app? If so, I'm having the same issue.iOS Extension authentication in Firestore |
Any way you can tell me how I track this bug #? |
@OGmetamonkey @ccjernigan I have the same issue in the macOS extension. Did you manage to solve it? |
Should be fixed in #9102. |
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Firebase Auth is not properly shared between multiple bundles within the same app group.
I have a macOS app where the main app and a second process (in the same app bundle) share the same app group. After the main app signs in, the second process launches via
SMLoginItemSetEnabled
as part of the setup process. When the second process touches Firebase Auth, a system password prompt appears to grant keychain access (for a keychain item named for my API key).Steps to reproduce:
Auth.auth().useUserAccessGroup(AppGroupId)
first)Auth.auth().useUserAccessGroup(AppGroupId)
and listens for auth changesAuth.auth().addStateDidChangeListener({ (_, user) in ... })
Results:
Actual: Second process triggers a system keychain dialog asking for a password.
Expected: No keychain dialog should appear, since these are using a shared app group
I realize that macOS is "community supported" although this seems to be a bug that should be resolved to better support app extensions and other multiprocess use cases.
The text was updated successfully, but these errors were encountered: