de0u Reading back, I think I was emotionally reacting to the discouragement of using ADB, as someone who values the possibilities it provides to interact with a device and learn about Android, and who has been using it for years without any issues. I was also triggered by NetRunner88's comment:
NetRunner88 Again someone messed with adb and boom nothing work as intended
And what I said was maybe more of a reaction to this than to your remark. The point I wanted to make is that ADB is just a tool, and usually if there is an issue that was preceded by the use of ADB, the issue lies with the user, not with ADB. With great power comes great responsibility, as my computer used to say when I was about to elevate my privileges...
Now for an actual reaction to what you wrote:
Overall, please recall that Google expects that developer options including adb are used on development devices that contain no private data and are wiped after testing
Where exactly does this notion originate? I have never encountered it before coming here. I don't see Android's developer documentation say anything like it in these pages on the topic:
You'd think it would be important to mention to people new to developing Android apps, if it were true.
And it is the case that many people manage to use adb in ways that lead to lasting trouble, which could be avoided by trying out a usage on a test device or just not using adb.
Fair point. It pains me to often see people pass around a bunch of ADB shell commands and recommendations while obviously having no real understanding of what it is they are doing. But also: what better way to learn than screwing up royally haha. Usually the only real issue is storing precious data on a vulnerable device and not doing backups... that's the ultimate user error that I've already seen reported several times since I signed up here over a month ago.