The docs say that getIsAuthorized shouldn't fire before the module is setup and that a renew should also execute and complete (success or fail) before getIsAuthorized is fired.
I can confirm that in neither of these cases is that true. And it doesn't fire the first time if there is no login information in storage either.
I would think that this event needs to fire after the module is setup, and only after everything is completed. That means, looked up in storage, if nothing, then fire. If something, but past expiration, then try silent renew, then fire. If something, but good, then fire.
But we're seeing many fires of this event instead. (we're also seeing it fire when there has been no changes at all)
Just relax - and waiting for next 11 release with promised updated docs, samples and api. Otherwise - using another lib, because due to this lib - a lot of headache & waste time to proper working with it.
@JohnGalt1717 This has been refactored and changed in verison 11 which we plan to release in the next few days after testing
Greetings Damien
Great! Thanks!