Rico, Bubble friends,
I am pleased to announce Bask version 0.8.26 fixes our major authentication issue - Bask is operational again 
As referred to earlier in the thread, our prior releases were broken due to Bubble changing the way their public authentication endpoint worked (Bubble, is in fact, shutting down the endpoint we previously relied on this week). Fixing this required coordination with Bubble to get Bask whitelisted as an Official Bubble Oauth Client. As simple as that may sound, it took several weeks to confirm this approach would work.
From this point forward, when current and new users go to authenticate with Bask, we no longer ask for your Bubble password. Instead, the extension directs you to open a URL to sign in to your bubble.io account. Once you do (this will happen automatically for anyone who is already signed in) you will be redirected to our site that looks like.
The code provided, which is different for everyone, will need to be copy and pasted into the Bask VS Code extension (the input for which will already be open). Once entered, you will be authenticated and Bask will internally refresh your OAuth token whenever it expires (you should not need to authenticate again).
While I know this took some time to get working, this should be a nice improvement over our previous sign in flow.
Finally, I did take some extra time to add improvements for making Bask work better in Github Codespaces - which is a really nice way to isolate code/plugin development. More improvements to come.
Overall, getting these fixes in place took way longer than I would have liked. I really appreciate the folks who showed great patience while we resolved this. As a token of my appreciation and apology to you, I will be offering free access to a new Bubble tool/service I will be launching in the coming months. It’s the least I can do outside of offering refunds to whoever so desires one. Thank you guys!