Hi @dan.woda,
It seems it works ok and it happened “magically” …not exactly, but when I was testing the solution, my auth flow, I always used a social provider Google to authenticate myself. And I was always propmted to login again. But then, just by chance, I used another login method with email and password. Then the session was stored properly.
So when I was reading this https://auth0.com/blog/react-tutorial-building-and-securing-your-first-app/article I found that sentence which helped me.
Blockquote
You might not have noticed but, even though you didn’t configure anything related to Google in your Auth0 account, the social login button is there and works just fine. The only reason this feature works out of the box is because Auth0 auto-configure all new accounts to use development keys registered at Google. However, when developers start using Auth0 more seriously, they are expected to replace these keys with their own. And, to force this, every time an app tries to perform a silent authentication, and that app is still using the development keys, Auth0 returns that there is no session active (even though this is not true).
So I haven’t re-factor anything and it seems working. But I do not know if the silentAuth() is called from somewhere or just works out-of-the-box of the react-auth0-wrapper.js?