Keychain access group used for the sign-in state about googlesignin-ios HOT 3 OPEN

@petea what are your thoughts about this?

from googlesignin-ios.

GSI stores sign-in state in the default keychain group. If you have the Keychain Sharing capability enabled and one or more keychain access groups defined, the default keychain group will be the first item in this list of keychain access groups. Groups defined after this first group could be used for state sharing between apps without GSI state being present, if that's desired.

from googlesignin-ios.

@petea
In our apps the first keychain access group is the shared one, meaning GSI will store the state in a shared place that will be read and written by all our apps. That's undesired of course.
I can think of several ways to avoid such mistakes in the future:

• Keep the current behavior and explicitly mention this in the README.
• Use a different service for each app based on their bundle ID (Like being done in FB SDK). This will require migration which is not desired I assume.
• Allow to select the keychain storage name (Like being done in MSAL). Might also require migration

What do you think?

from googlesignin-ios.