The latest version of [andOTP](https://github.com/andOTP/andOTP/releases https://github.com/andOTP/andOTP/releases) indicates that it protects some of the field

The latest version of [andOTP](https://github.com/andOTP/andOTP/releases https://github.com/andOTP/andOTP/releases) indicates that it protects some of the fields from accessibility hijack. I suspect other apps will find a way to prevent this attack. The problem I, the author, have is that it seems unlikely that Google can fix this. What are the risks associated with suddenly changing a codebase which is 2.5 years old? Is there anyone there who works on it day-to-day, understands how it works, and can release a verifiably fixed patch? Security products need constant maintainance.