Yesterday I released a version of the core that includes new Helix scopes. The two we are most interested in our chat:read and chat:edit which are supposed to allow new applications to be used.
gOOvER reports that he still continues to experience the issue. So I'll need to run deeper tests with new applications. gOOver also reports that permissions are being requested during oAuth2 that were not selected as he only selected the new Helix ones.
Is the plugin relying on the initial users own scopes maybe?
Yesterday I released a version of the core that includes new Helix scopes. The two we are most interested in our chat:read and chat:edit which are supposed to allow new applications to be used.
gOOvER reports that he still continues to experience the issue. So I'll need to run deeper tests with new applications. gOOver also reports that permissions are being requested during oAuth2 that were not selected as he only selected the new Helix ones.
Is the plugin relying on the initial users own scopes maybe?
This is a very high priority issue.