Play Families, and eMudhra

Welp, it turns out there was a reason I got those "policy violations". It was the Play Families policy... Plus, a certain company called eMudhra had a certificate compromise, that affected the desktop app.

When I was filling out the target age ranges for the app, I intended for it to be for general audiences. So, I naturally just checked every age box they had. BUT, in doing this, I was forced to be compliant with the Play Families policy.

My app didn't violate anything in the policy (and, the last 2 releases bound by it were approved). But updates were PAINFULLY slow. What would take a few hours to go on the store for the 13+ age range I use now, took at LEAST 5 full days with the old age ranges bound by the policy. It'd still get approved, but there's no guarantee the families policy wouldn't SUDDENLY change one day and ruin it all.

Plus, eMudhra had a now-pretty-well-known incident of many of their intermediate certificates being compromised. Basically: until Google and Apple, and Microsoft, and more patched this out (they did a a few days ago) anyone could fake that their website is "secure", and replace actually secure websites with fake pages, because the fake page can now appear as trusted.

But, Electron (used in the desktop app) has its OWN list of trusted certificates. This meant I had to patch the app in order to remove the untrusted certificate. It was easy, because all I had to do was update the Electron version which patched it for me, but I also patched the ARMv7 builds, because there was still one user on the Snap Store (yes, literally only one), using ARMv7. So, since I was only viewing the Snap Store analytics, but one person showed up as an ARMv7 user, I knew that there was some use of that at least... so may as well patch it because it's easy.

Anyway, that's all for now! See ya soon! :D