Sorry for being away for a few days - Xmas, family stuff, etc. Even evil trickster gods have to take family time.
The challenge to that is that - prior to the update, all anyone wanted from them was to say SOMETHING...even if it were just "we are working on it, coming soon". So they are kinda damned if they do, damned if they don't here. Personally, I would rather them err on the side of saying something vs just abject silence until the fixes suddenly appear.
I, too am wondering where the GP update/fix went...I have sent an email to that regard this evening.
Afraid that is unavoidable. Even if a fix were sitting right there to submit, if the device companies are not open, there is nothing that can be done.
They got all that they could do done prior to what I assume was a cross-the-board shutdown (not only for them, but also for Apple, Google, and most companies). That said, as I noted above, I too am curious as to where that GP update went.
I've asked about this directly. I know they are working directly with Microsoft to fix the issue - AND rebuilding the entire code for WP in parallel in case that doesn't work. I do not know why tickets are closed - but I asked those that would know.
Except that in order to pass certification, it would have to have been tested by MS as well. If it were crashing every time on their devices, there is zero chance the update ever passes cert. If that makes sense? It has been a confounding mystery for all thus far.
Duplication in QA terms means consistent cause-and-effect replication. Anyone can make a file go corrupt (power down or crash during a save cycle, for example)...but to actually find a bug to fix you need to have that cause and effect. Crashes in general are a very generic and nebulous issue. Impactful, to be sure...but often multifactorial and not always as simple as "a problem in the software". That is what they mean.
Again, I have asked about the ticket closings directly.