Authentication Network error detected

Hello!

So, we’ve been using UnityServices package for some time and since, for some reason, authentication is required to use Remote Config, we added that as well.

This is an approximate implementation of the init process:

        var options = new InitializationOptions().SetEnvironmentName(UGSEnvironment);
        await UnityServices.InitializeAsync(options);


        if (!AuthenticationService.Instance.IsSignedIn)
        {
            try
            {
                await AuthenticationService.Instance.SignInAnonymouslyAsync();
            }
            catch (Exception e)
            {
                //
            }
        }

Recently, after publishing a major update, after inspecting LiveOps Error Reporting, I’ve noticed quite significant number of reports (not related to Services at all) with logs such as this:

This happens at the very beginning of the app/game and further logic kind of depends on the response, so we are showing a loading progress while waiting. In this case, the wait reaches upwards to 20s.
And thus, I have a couple of questions:

  1. Is there a way to explicitly set the timeout to any other number?
  2. Is there a way to turn on/off the ‘retrying’ process of the service?
  3. Is there a way to manually/explicitly control the run of the awaitable tasks (ie via task cancel tokens) ?

Since I’ve inspected the documentation and what intellisense provides, the above questions are more-or-less rhetorical, as the answer looks to be ‘no’.

So, my real question is: ‘why’ ?

Currently, we can’t adjust the game logic so that the authentication runs in the background and we proceed with other stuff. I also got notified that the Remote Settings service is getting turned off by the end of the month, so one option is to remove it completely and thus not require an authentication. But that is for later date.

Is there something (possibly in documentation) I’m missing?

Thanks in advanced for any response.

Hello
You can use remote config without authenticating as a player which may simplify your use case.

What version of remote config and authentication do you have in your project?
I would recommend updating both to the latest versions available. (Remote Config Runtime 3.3.2 & Authentication 2.6.1)

I would also recommend to not log exceptions related to network errors as these are common and normal errors to handle when a player does not have internet/fails to connect.

We do not offer configuration for the retry policy or cancellation token support at this time, but we are considering these for future improvements. Retries usually happen on network errors which normally fail quickly.

Thanks for the feedback.

Actually, Authentication already has version 2.7.2 available and one of the Remote Config packages has version 4.0 available.

Hi, thanks for responding.

I’m not aware of Remote Config not requiring authentication. Maybe you should clarify that in your current documentation if that’s really the case:
9193403--1281428--upload_2023-8-4_9-43-39.png

AFAIK, without authentication, the remote config doesnt work (either properly or at all). I’ll have it tested again since we’ve implemented that quite some time ago, but as far as I remember, RC didn’t return anything without authentication, since it couldn’t work with services’ environments.

We don’t usually log exceptions and we certainly don’t log anything in release builds. Everything I posted above comes from unity packages.

We always update to latest package version before releasing, in this case, Remote Config is on 3.3.2 version (unity 2021).

Looks like removing Remote Config is the only way to solve this for the time being.

We made a couple of tests on development environment and can confirm that Remote Config does not actually require authentication anymore, not even for overrides.

I suggest clarifying that in the documentation.