Post B5nMmc5IQkTF9uXKnw by SylvieLorxu@chaos.social
 (DIR) More posts by SylvieLorxu@chaos.social
 (DIR) Post #B5RtmQpzGijTHqmLYG by SylvieLorxu@chaos.social
       0 likes, 0 repeats
       
       I'm amazed that Google's stupid new nonsense "Android developer verification" program is so broken that they literally fail to auto-register one of my three apps that are *on Google Play*. I need to "prove ownership" over an app I published to Google play in February 2020 and that's still in my account...Sigh.Google, if you're going to be evil, can you at least be competent for once? Please? I have better things to do than this nonsense?
       
 (DIR) Post #B5lFYTS2dxeMKmZBnE by SylvieLorxu@chaos.social
       0 likes, 1 repeats
       
       It got even weirder.Catima: auto-registered with just the Google fingerprint, but I could add the GH/IoD and F-Droid ones without any workRaise To Answer: auto-registered with just the GH/IoD fingerprint but could add the F-Droid one without work (probably because targetSdk too low to keep on Google Play)Share To InputStick: I need to manually upload an APK and it only treats the F-Droid key as eligible. Trying to verify with my key instead, we'll see how that goes.What an absolute mess.
       
 (DIR) Post #B5lFYUqXSMq6f32GcC by SylvieLorxu@chaos.social
       0 likes, 0 repeats
       
       Leave it to Google to find the most botched way to launch an inherently stupid program like this.
       
 (DIR) Post #B5nMmZRWFfSqxxuXWi by SylvieLorxu@chaos.social
       0 likes, 0 repeats
       
       Okay approved but apparently I need to... sign an APK including this file with F-Droid's key.This flow makes no sense.They should *know* this flow makes no sense.This nonsense must be on purpose, forcing people to do new releases on F-Droid solely for verification. Using a file that they literally did not document if it can safely be included in git or not.
       
 (DIR) Post #B5nMmZzYD8gcfVpiZU by IzzyOnDroid@floss.social
       0 likes, 0 repeats
       
       @SylvieLorxu Having Reproducible Builds fail because of missing to document that (so devs put it into their .gitignore, considering it being a "secret" – and no, I definitely do NOT blame the devs for that, but rather those who cause these shenanigans)
       
 (DIR) Post #B5nMmc5IQkTF9uXKnw by SylvieLorxu@chaos.social
       0 likes, 0 repeats
       
       This is so frustrating because I have no plans to do a new release any time soon as the app works fine. Now I need to bother users with an useless update and waste their bandwidth just because Google decided to create this dumb verification method for this dumb policy? :/
       
 (DIR) Post #B5nNgYP3IwtlxSS54q by SylvieLorxu@chaos.social
       0 likes, 0 repeats
       
       @IzzyOnDroid At least it only seems to be necessary once so devs can remove it after again. Though one release failing RB can be quite a bother already from wasted debugging time...
       
 (DIR) Post #B5nPBBF1ZMGd3QvfH6 by IzzyOnDroid@floss.social
       0 likes, 0 repeats
       
       @SylvieLorxu At RB it's rather nasty. Though after we figured it the first time, a work-around is ready. Still, with 20+ builds each day, it's needlessly wasting time…