Well, yes, it's a business decision. Google wanted to push their Chromecast devices so they made them use proprietary Google Cast protocol and removed Miracast from Android (both phones and TVs). They later added Chromecast/Google Cast to Android TV but it is still not supported on other platforms. Samsung on the other hand had their own TVs which don't use Android TV so they added Miracast back to their phones and removed Chromecast so that their consumers would buy Samsung TVs.
That's how they do it. They send their "proposal" and immediately implement it in Chrome (with work on that being started long before "proposal" is made public obviously). Then they start using it on their own websites (with compatibility for now) and start propaganda campaign to push webdevs to use it too (which they do of course). Then they start complaining that other browsers' developers are slow to implement this new "standard" (at this stage they won't call it a "proposal" anymore) and are "stifling development of the web" or being actively malicious because they are jealous of Chrome or something. Then compatibility mode on their websites is first subtly broken so that users once again will witness how Chrome is superior browser and then removed outright. Boom, we have a new web standard!
Sounds like they didn't test what happens with their apps when token is reset on server 🤔 should be reported to the apps devs. Thankfully with lemmy this is easier to fix than with proprietary services because you can self-host it and check various edge cases.
Well, yes, it's a business decision. Google wanted to push their Chromecast devices so they made them use proprietary Google Cast protocol and removed Miracast from Android (both phones and TVs). They later added Chromecast/Google Cast to Android TV but it is still not supported on other platforms. Samsung on the other hand had their own TVs which don't use Android TV so they added Miracast back to their phones and removed Chromecast so that their consumers would buy Samsung TVs.