Mike Hardy

@BrayanDSO - I think you mean "In most use cases, the user either will never use the timer or always use the timer" (never/always, vs never/never) ? @david-allison I'm inclined...

It is not exactly stale but it is duplicated ("docs are not up to date") working on that, main issue tracking is #559

@BrayanDSO > The issue is about APK optimizations, but there is also https://github.com/ankidroid/Anki-Android/issues/9259 to keep in mind. ...this is true, but unfortunately I do not think that will offer much...

Here is my thinking on comparing release APK size growth on an ongoing basis to prevent silly problems from creeping in again and doubling our app size without meaning to:...

A slight wrinkle in the implementation design idea I had above: If we are just storing the release APK size for "main", updating it on any merge to "main" and...

@lukstbit yep - just had to handle that to pass lint in the stack of PRs, commit here - and examination of that commit (probably altering it or the objects...

PR #13586 looks like the proper way to go about things - sad (word directed at myself) that the PR has sat so long and accumulated some conflicts! It looks...

Just adding a quick note here that one item has been provisionally handled, so it may not show up in the deprecation scans anymore, but it needs a more thorough...

Possibly worth noting that in a macos context, auth is just about fully supported (even with TOTP working now...) via the "other" platform (which wraps firebase-js-sdk). You can run our...

similar recurred - discord discussion https://discord.com/channels/368267295601983490/701922522836369498/1244755057342283816 I cleared related caches and CI went green https://github.com/ankidroid/Anki-Android/actions/runs/9258853942/job/25469709342#step:8:91 ``` Execution failed for task ':AnkiDroid:processPlayDebugResources'. > Multiple build operations failed. Could not read workspace...