Closed TMSantos closed 1 year ago
I was running into this issue as well. Cloned the repo and discovered that KeycloakPromise extends Future, which is causing the issue because the JS promise is not a future, which causes this exception to happen when the future chaining checks if the returned value is a future.
This has seen been resolved. Closing. Please create another issue if thats not the case.
it throws this error at initialization:
--debug works --profile doesn't work --release doesn't work
I guess is because keycloak.js gets obfuscated, changing it's method names
Any ideias?