I know the OP said they had resoled this on their own, but for public sake i wanted to document the process:

So the way to circumvent this while retaining 2FA on your account is to generate Application Passwords which allow access without triggering the TOTP dance.

https://security.google.com/settings/security/apppasswords

Once you've generated the app password and entered it into your app (Dekko, Thunderbird, Etc.) you should have the same browser login experience with 2FA, and your apps should be able to function securely. Note: that those app passwords are scoped to the entirety of your google account and should be protected just like any other account password.

Best of luck, cheers

@vandys Do we know what API services were running at dash.ubuntu.com? I know that daisy is their error collecting/reporting system (think apport collector) and is likely to be unhelpful to us unless we have the funding to deploy loads of postgres and storage to have our own services of Whoopsy and Daisy deployed. I'm fairly certain that there are charms for these.

A cursory search of the charm store yields an older release

• https://jujucharms.com/u/daisy-pluckers/daisy/trusty/9

But again, I don't think we would need something of this magnitude until we are ready to collect automated crash reports when a user gives consent.

Greetings everyone,

I'm not so much a new comer to the project as I am new to the UB Ports community. I formerly worked at Canonical as a lead developer on the Canonical Distribution of Kubernetes and was a big mouth in the Juju community. (no really, I talked a whole lot...)

I have admiration for the Halium project and the continuation of UTouch. I just picked up a One plus One to lend a hand with QA of the releases. I may lean on you for help to track down the proper information to attach to a bug report but I do plan on trying to help make UTouch a daily driver, and will post fun hacks I come up with in my hobby time.

Cheers everyone, and may we find good luck on our adventure together.