@slurpnik
Thanks for your kind words which I really appreciate š
I donāt want to blame anybody, I am convinced that everyone who works as an engineer or developer individually is doing their best to find out whatās going on and to find a solution.
Nonetheless, imo itās not enough to just keep on trying.
If you realize as a company that you have launched an update that makes devices completely (!) unusable (even if only a part of the users is affected), and youāre not able to find a solution within a short period of time, the right decision would be to openly communicate and to go back to the status quo ante (which then would give you all the time you need to figure out what was going on and to work on an improved version).
That is what imo a professional reaction would be when you realize that something like that has gone wrong.
Imagine apple would launch an update for their phones and afterwards you are no longer able to make a telephone call for one month (and thereās no communication when this status is about to end). No one would accept this, I am sure.