I think I found out the root cause:
When you call getAccessTokenSilently are you using the same audience and scope that is set in the Auth0Provider? I’ve seen in some cases that silent auth will be required because a new scope or audience is requested after the app initiates. Silent …
By the way, this is definitely a new thing, as earlier this year all above worked, but somehow recently I found out we will need to pass in exact both scope and audience to Auth0Provider.
Can can I track those software updates by the way?