[Question] macOS version does't store player credentials after game quit.

[Fatorin]

What is your question?

My project is using Firebase Authentication as our identity authentication system.

The login mechanism for our desktop version originally involved embedding a web browser within the game and storing login credentials internally.

Later, to improve the player login experience, we switched to a login process similar to the mobile version.

When testing on Windows version, Unity Editor on Windows, and Unity Editor on MacOS, player credentials(FirebaseUser) are stored after successful login, so there's no need relogin until signout.

However, when I build the macOS version, player credentials aren't stored upon closing the game, requiring login every time when application start.

I understand that the desktop version SDK is still in the beta phase, but if credentials can be stored on Unity Editor on MacOS, why can't they be stored in the macOS version?

Note: I'm testing using a Mac M1.

Firebase Unity SDK Version

11.8.1

Unity editor version

2021.3.25f1

Installation Method

.unitypackage

Problematic Firebase Component(s)

Authentication

Other Firebase Component(s) in use

No response

Additional SDKs you are using

No response

Targeted Platform(s)

Desktop

Unity editor platform

Mac

Scripting Runtime

Mono

Release Distribution Type

Pre-built SDK from https://firebase.google.com/download/unity

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[argzdev]

Hey @Fatorin, thanks for reaching out. The player session should remain after a successful login, there should be no need for a relogin. That said, I've tested this out with our quickstart-unity and it seems to work correctly. There might be a configuration issue on your side, you could test out our quickstart to get a code reference on how this is setup. Make sure your code is monitoring the StateChanged right after initializing Firebase:

e.g.:

    protected void InitializeFirebase() {
      DebugLog("Setting up Firebase Auth");
      auth = Firebase.Auth.FirebaseAuth.DefaultInstance;
      auth.StateChanged += AuthStateChanged;
    }

Also could you check if you allowed the permission to store the credentials in the Apple Keychain? There should be sort of a pop up dialog asking for this permission when you log in the first time.

Let me know if this helps!

[Fatorin]

@argzdev Thank you for your reply. I encountered an error message when Firebase was saving credentials.
SaveUserData: Error -67030 adding com.xxxx.oooooooo.xxxxxbeta.F2TvZ5cmdn8.firebase.auth/__FIRAPP_DEFAULT: invalid Info.plist (plist or signature have been modified)

Probably this Info.plist file only works on iOS. Maybe I should manually modify the Info.plist file to use it on macOS?

[argzdev]

From my understanding, this type of issue "Invalid Info.plist" can only occur whenever the app is code signed. Does the issue happen after building the macOS version prior to code signing? Or after you've performed code sign on your app?