No auth token found when signing message

[LeonelSalvo]

Issue started last week after a redeploy, useActiveAccount or any other ways to get to the signMessage() will throw this error for email logged wallets using In-App wallet with default settings. Weird thing, is not happening with metamask or other log in ways.

Looking into localstorage, i see that previous deploys of my app, using thirdweb sdk v5, had wallets as "sharded", now are "enclave" and methods from account objects from email logins fail with this.

Looking into localstorage, i see in my previous versions a lot of data populated, but in the new ones ( the ones that email fails ) never gets populated

Actual storage:

Previous:

Looking into .js bundled sources i see that the signMessage() fn looks for the auth token, like "authCookie" and is not defined.

[linear]

CNCT-2506 Error 🔥 No auth token found when signing message. Only with Email login

[gregfromstl]

Hey @LeonelSalvo, could you please provide the version of the SDK you're using

[LeonelSalvo]

hi @gregfromstl From 5.68 to 5.72.0 happens

[LeonelSalvo]

Following through the sdk, seems like the postWalletSetUp() call is not saving the authCookie, the network request from email OTP process brings storedToken good thou:

    "storedToken": {
        "jwtToken": "BRINGS_THE_JWT",
        "authProvider": "Email",
        "developerClientId": "DEV_ID",
        "authDetails": {
            ... BRINGS_DETAILS
        },
        "cookieString": "BRINGS_THE_COOKIE_STRING",
        "isNewUser": false,
        "shouldStoreCookieString": true
    }

        this.wallet = await this.initializeWallet(
          authResult.storedToken.cookieString,
        );

        if (!this.wallet) {
          throw new Error("Failed to initialize wallet"); // Not triggering, so its OK
        }

        const deviceShareStored =
          "deviceShareStored" in authResult.walletDetails
            ? authResult.walletDetails.deviceShareStored
            : undefined;

        // Here ? im not finding `${AUTH_TOKEN_LOCAL_STORAGE_PREFIX}-${key}`
        await this.wallet.postWalletSetUp({ 
          storedToken: authResult.storedToken,
          deviceShareStored,
        });

All calls after for other things are good as i see, at least in UI and network inspector

But for the enclave wallet sign

 signEnclaveMessage({
          client,
          payload: messagePayload,
          storage,
        });

throws

  const authToken = await storage.getAuthCookie();
  const ecosystem = storage.ecosystem;
  const clientFetch = getClientFetch(client, ecosystem);

  if (!authToken) {
    throw new Error("No auth token found when signing message");
  }

[gregfromstl]

Hey @LeonelSalvo, thanks for the details on this. I can't seem to reproduce this by trying to replicate your setup. Could you please provide a minimal reproduction and I can look into it further? Also, I'm assuming you've tried clearing your local storage and refreshing already?

[LeonelSalvo]

Hey @gregfromstl , yes already cleared and refreshed, even going back or moving between 5.68 and 5.72 im seeing this issue

Have been working past 8 months with same code, just started to happen after wallet sharded => enclave migration

Im working to create a small implementation with this for you

[LeonelSalvo]

May be a fix on our end:

Plus: updated to latest sdk version, upgraded package lock, erased all cache from deployments

Doing the small repro, i reached old code where we need to clean user localstorage before the sign ( previously without problem, since embedded wallet relayed on cookies instead ) since authCookie is now on localstorage, not necessary a problem on your end then