Empty idToken when adding Curve.ED25519 to LoginParams

As the title says, the idToken is empty with login in with Curve.ED25519 in LoginParams

    public void Login(Provider provider)
    {
        string verifier = "";
        TypeOfLogin typeOfLogin = TypeOfLogin.GOOGLE;
        string providerName = "";
        string clientId = "";

        switch (provider)
        {
            case Provider.GOOGLE:
                verifier = "solcraft-google-auth";
                typeOfLogin = TypeOfLogin.GOOGLE;
                providerName = "google";
                clientId = GOOGLE_ID;
                break;
            case Provider.FACEBOOK:
                verifier = "solcraft-facebook-auth";
                typeOfLogin = TypeOfLogin.FACEBOOK;
                providerName = "facebook";
                clientId = FACEBOOK_ID;
                break;
        }


        var loginConfigItem = new LoginConfigItem()
        {
            verifier = verifier, // get it from web3auth dashboard
            typeOfLogin = typeOfLogin,
            clientId = clientId,
        };

        web3Auth.setOptions(new Web3AuthOptions()
        {
            redirectUrl = new Uri("torusapp://com.torus.Web3AuthUnity/auth"),
            clientId = WEB3AUTH_ID,
            network = Web3Auth.Network.SAPPHIRE_DEVNET,

            //Optional loginConfig object
            loginConfig = new Dictionary<string, LoginConfigItem>
            {
                {providerName, loginConfigItem}
            }
        });

        var options = new LoginParams()
        {
            loginProvider = provider,
            curve = Curve.ED25519
        };
        web3Auth.login(options);
    }

Works fine without adding the curve option, but since I want to connect to Solana I need ED25519.

Thank you for looking into it.

@gillesjo.walther Thanks for reaching out.

We will review your issue and get back on Monday with an update.

Our team are working on your issue and I will get back once there is a meaningful update to share

@gillesjo.walther Sorry for the delay.

Our team confirmed the issue has been fixed. Please check.