Maybe we're not sending the domain to lit protocol correctly. Or maybe it's a bug in the Lit SDK. Unclear.

I could replicate this issue when Lit Session has expired. So user need to disconnect wallet and connect wallet again so the Lit Sign message will apear and allow decryption to work again.

After further investigation it looks like the issue is happening on the LIT SDK.

Message I sent to Lit support:

I think I found a bug in the Lit SDK and I want to see if that is the case.

We are getting an domain undefined error in our application when the session expires. So as we discussed before here we are passing our application domain to the createSiweMessage function.

The thing is that this function is called inside the authNeededCallback

So when our application calls it at the first time everything works as we pass the domain param when calling our application get session function.

But when LIT calls authNeededCallback later on, the domain param will be undefined

It looks like LIT SDK should add domain param to the AuthCallbackParams

Then when authNeededCallback is called again because the session has expired it would have the correct domain saved in there like the uri param.

See image bellow