5 ms·

This is par for the course for Android, having had to work with it at the hardware enablement level. Google will refactor and break everything in a dot release,

This is par for the course for Android, having had to work with it at the hardware enablement level. Google will refactor and break everything in a dot release, and then swear up and down that their code is perfect, even as you point them directly to the commit that caused the issue. This is clearly unacceptable, but I've seen so much worse.

BoorishBears 4y ago
> and then swear up and down that their code is perfect Even worse when they don't do this and just flat out admit they broke a usecase intentionally and label it Won't Fix because the team that implemented the breaking change is also the team that triages the issue. See logcat access being completely broken in Android 13: https://www.reddit.com/r/tasker/comments/wpt39b/dev_warning_if_you_update_to_android_13_the/ https://www.reddit.com/r/tasker/comments/wpt39b/dev_warning_...
yazzku 4y ago
That's completely fucked up. Arrogance much or?
- cuteboy19 4y ago
  They just don't care
ofchnofc 4y ago
[dead]