Android Developer @ Doist (Todoist and Twist). Words are my own.
I write on https://afzal.me and https://doist.dev
| Pronouns | he/him |
| Work | Android @ https://Doist.com |
| GitHub | https://github.com/AfzalivE |
| Twitch | https://www.twitch.tv/afzal____ |
Android Developer @ Doist (Todoist and Twist). Words are my own.
I write on https://afzal.me and https://doist.dev
| Pronouns | he/him |
| Work | Android @ https://Doist.com |
| GitHub | https://github.com/AfzalivE |
| Twitch | https://www.twitch.tv/afzal____ |
We have a screenshot requirement in our PRs (where it makes sense). I decided to be a bit cheeky when I added some logging yesteday. π
(Using Stable Diffusion)
#AndroidDev PSA:
If you updated to androidx.test:core:1.5.0 (or androidx.test.ext:junit:1.1.4) and you're getting an NPE crash with this message.
Current state was null unexpectedly. Last stage = STARTED.
Create your own AndroidComposeTestRule and pass your activityScenarioRule to it.
Earlier this year, we migrated the Todoist WearOS app to Jetpack Compose. We got a chance to completely redo the UI in the process.
Yesterday, this happened! π π
https://play.google.com/store/apps/editorial?id=mc_bo22_apps_wear_fcp
When you're recreating a component in Compose but testing the `View` version.
I was like "Why is this link clickable? How is it even underlined!?" π
I don't think Doist (my company) has any open roles at this time but I can certainly get any Tweeps in touch with people that are hiring like SpotHero here.
π