The issue is present here: https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route
The solution I recommended (although this should be re-validated):
I think you can resolve this by updating verifyToken to resolve with undefined instead of rejecting with an error in this case. The user is not expected to be logged out btw, they should be able to refresh in this case. (So you should end up in the branch rendering TryRefreshComponent)
For more details see this thread