Posts by SylvieLorxu@chaos.social
(DIR) Post #B4QUmROoRT2zDTV4xk by SylvieLorxu@chaos.social
0 likes, 1 repeats
RE: https://chaos.social/@grote/116257002625921666For the purpose of preventing someone over the phone or remote control guiding someone to sideload malware just disallowing app/sideload installs during a phone call/screen share would be more than sufficient. But of course, now I am arguing in good faith, which Google is not.It is literally faster to install a custom Android ROM at this point. Over 24 hours of waiting? I need to wait a full day to be allowed to install my own apps on my own phone?...RT: https://chaos.social/users/grote/statuses/116257002625921666
(DIR) Post #B4RfPjRmT3YJBUDrou by SylvieLorxu@chaos.social
0 likes, 1 repeats
RE: https://chaos.social/@grote/116257002625921666I quote boosted this before focusing on the 24h delay, but the worst part is having to enable developer options.Fairphone: Settings -> About phone -> Build number (7 taps)Samsung: Settings -> About phone -> Software information -> Build number (7 taps)Given the steps differ per device it is impossible for any third party app store to give clear instructions. To top it off, the first 3 taps give *no feedback* at all.Even worse, some apps refuse to run on devices with dev mode enabled.RT: https://chaos.social/users/grote/statuses/116257002625921666
(DIR) Post #B4RfPjeXhblDp4C3iC by SylvieLorxu@chaos.social
1 likes, 0 repeats
Google obviously knows how user unfriendly it is to enable developer mode and how this will effectively make it impossible for the vast majority of non-technical users to access any third party app stores. This is as malicious as malicious compliance to EU law goes. I cannot think of a more aggressive roadblock they could have put up, even forcing some to choose between third party app stores like #FDroid or #IzzyOnDroid and banking apps.There is no doubt about it, this is not about safety.
(DIR) Post #B4RfPk7FyqjHG7czT6 by SylvieLorxu@chaos.social
0 likes, 0 repeats
Keep in mind, enabling developer mode is just *ONE* of the many steps. This whole process is made as difficult and with as much friction as they possibly could. No third party app store could guide most users through this successfully.
(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 #B5SrITBJz23h7SIphw by SylvieLorxu@chaos.social
0 likes, 1 repeats
Begrudgingly dealing with the Android Developer Verification bs.Added the IzzyOnDroid/GitHub and F-Droid fingerprints for Catima to not have them blocked by Google.I submit them and... "In review"?What do you mean, "In review". How about you let *me* choose which keys *I* sign *my own goddamn app* with?This shit is utterly disgusting. I have no words for it.Fuck Google. Fuck this "developer verification" lockdown. The EU needs to fine the shit out of them for this bullshit.
(DIR) Post #B5SrITVskaVO9DvFku by SylvieLorxu@chaos.social
0 likes, 0 repeats
For others who have to deal with this nonsense, I've found the easiest way to get your fingerprint for your IzzyOnDroid and F-Droid builds to be the following curl command:```export INDEX_V2_URL="https://apt.izzysoft.de/fdroid/repo/index-v2.json" # IzzyOnDroidexport INDEX_V2_URL="https://f-droid.org/repo/index-v2.json" # F-Droidexport APP_NAME="your.package.name"curl -s "${INDEX_V2_URL}" | jq -r ".packages.\"${APP_NAME}\".metadata.preferredSigner" | tr [:lower:] [:upper:] | sed 's/../&:/g; s/:$//'```
(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 #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 #B5t5jVjH4O62J7vkZ6 by SylvieLorxu@chaos.social
0 likes, 0 repeats
@rexo @IzzyOnDroidOrg I think you may have been looking for https://apt.izzysoft.de/? While https://izzyondroid.org/ is our new user-facing website the actual repository is still under https://apt.izzysoft.de/ :)Did you find an incorrect link somewhere leading you to the non-existent domain?
(DIR) Post #B629BROQpjbXFipYYq by SylvieLorxu@chaos.social
0 likes, 1 repeats
Catima 2.42.0 is out!https://github.com/CatimaLoyalty/Android/releases/tag/v2.42.0#Catima is an #Android app to store and organize tickets, loyalty cards and other barcode/pkpass-based data.A new feature this release is a setting to disable NFC while showing a card, preventing accidental NFC payments from other apps. Dutch train travellers rejoice :)It also contains some small refactoring and modernization under the hood.Coming soon to an app store near you.#IzzyOnDroid #FDroid #GitHub #GooglePlay
(DIR) Post #B69PBfqM499HRVkBSi by SylvieLorxu@chaos.social
0 likes, 3 repeats
RE: https://toot.teckids.org/@nik/116540880770634816As someone who has been programming since being a young teenager, things like this make me enormously sad.If I was banned from being part of tech communities until the age of 16 or even 18 I would've never been able to learn all I did. I would've never been able to truly get into FOSS.I would've never had a chance to become who I now am.Age verification is literally killing the ability for kids and teens to excitedly participate and learn cool stuff and learn how to have digital agency.RT: https://toot.teckids.org/users/nik/statuses/116540880770634816
(DIR) Post #B6BODgKnV3nLuHIRt2 by SylvieLorxu@chaos.social
0 likes, 1 repeats
I've paused the Google Play rollout due to https://github.com/CatimaLoyalty/Android/issues/3124.Does anyone else have this issue? I'm trying to figure out how widespread this is and if I should treat this as an "one random person with a buggy launcher" or "affecting the majority of users".
(DIR) Post #B6IQeg7Dyvxp3rfU2a by SylvieLorxu@chaos.social
0 likes, 1 repeats
Okay so, summarizing feedback: if this happens seems to depend on Android version and launcher, making it very hard to reproduce. And the workaround is simple, recreate the shortcut. So I guess I will just accept this being suboptimal and not have it be a blocker.I'm more worried about this NFC crash, has anyone else been having crashes in 2.42.0? If so, please give me as much info as you can: https://github.com/CatimaLoyalty/Android/issues/3131
(DIR) Post #B6MDKuFfC14CL9hG0e by SylvieLorxu@chaos.social
0 likes, 1 repeats
Catima 2.42.1 is out!https://github.com/CatimaLoyalty/Android/releases/tag/v2.42.1#Catima is an #Android app to store and organize tickets, loyalty cards and other barcode/pkpass-based data.This release is functionally identical to 2.42.1, except that it fixes a crash on devices with misbehaving NFC. If your device is affected you will now see a "Failed to pause NFC" message instead of a full app crash.Coming soon to an app store near you.#IzzyOnDroid #FDroid #GitHub #GooglePlay
(DIR) Post #B6MDKy9mfojyS4ycOu by SylvieLorxu@chaos.social
0 likes, 0 repeats
This was made possible due to the several people who not only reported the crash, but who also were willing to spend some time back-and-forth testing new debug builds. Given this doesn't happen on any of my devices, I may not have been able to fix it without that help.
(DIR) Post #B9mLYvWd1QY3HIX7wW by SylvieLorxu@chaos.social
0 likes, 1 repeats
@IzzyOnDroid @fabio deserves most of the thanks, this is mostly his code, I just wrote up what I understand of it :)