Christopher Boyd

I'm also seeing this with v4.9.0. Notably, I was using the automatic login scheme, which threw warnings about falling back to the `v2` logout because OIDC RP-initiated logouts aren't enabled...

I'm not calling `auth0.getSession` but I did implement `async onCallback(error, context, session) {}` which includes the `session` as argument (but again, is not referenced within my code).

In my workflow, I was using `auto` which reported downgrading to a logout strategy of `v2` since OIDC logout was disabled on the tenant. I believe that both Chrome-based browsers...