Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some apps show up with a generic icon #273

Open
bt90 opened this issue Aug 13, 2022 · 8 comments
Open

Some apps show up with a generic icon #273

bt90 opened this issue Aug 13, 2022 · 8 comments

Comments

@bt90
Copy link

bt90 commented Aug 13, 2022

The fallback is correct for Transistor which doesn't provide an icon. Syncthing-Fork has a proper icon but it isn't used.

Screenshot_20220813-131910.png

https://f-droid.org/en/packages/com.github.catfriend1.syncthingandroid/

@machiav3lli
Copy link
Member

A lot of apps still don't respect modern metdata requirements and thus their icons are left out or a they should be aggregated from some others places (which have many negative sides regarding security, performance etc..).
To solve this, just write each project on the fact that metdata requirements say that the project's icon should be available in the main locale (e.g. en-US) under /images with the name icon.png

Ilithy added a commit to OlauncherCF/OlauncherCF that referenced this issue Aug 13, 2022
Addition relating to the absence of the application icon in F-droid (although it is present in the app, and perfectly displayed by Android).

See @machiav3lli's comment here: NeoApplications/Neo-Store#273 (comment)
@bt90
Copy link
Author

bt90 commented Aug 14, 2022

According to one of the jitsi devs, adaptive icons are not supported yet.

jitsi/jitsi-meet#12019 (comment)

jooooscha pushed a commit to OlauncherCF/OlauncherCF that referenced this issue Aug 14, 2022
Addition relating to the absence of the application icon in F-droid (although it is present in the app, and perfectly displayed by Android).

See @machiav3lli's comment here: NeoApplications/Neo-Store#273 (comment)
ignoramous pushed a commit to celzero/rethink-app that referenced this issue Aug 17, 2022
also: github.com/NeoApplications/Neo-Store/issues/273#issuecomment-1214153179
@bt90
Copy link
Author

bt90 commented Aug 19, 2022

@machiav3lli does Neo-Store support adaptive icons?

@machiav3lli
Copy link
Member

As long as FDroid doesn't we don't

@bt90
Copy link
Author

bt90 commented Sep 1, 2022

@leoheitmannruiz
Copy link
Contributor

leoheitmannruiz commented Jan 6, 2025

@bt90 In case you're interested and for the sake of completeness: the only way to provide an icon for an app in the main F-Droid repository is using Fastlane/Triple-T metadata in the source code repository of the app. See https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/.

What seemingly caused confusion here is that Neo Store only checks the en-US locale for the icon (and presumably other metadata). en-US is the default locale in the F-Droid ecosystem and all apps should provide metadata in en-US.

Syncthing-Fork didn't provide the icon in en-US but in en-GB. I recently sent a PR moving the metadata to en-US, which was merged: Catfriend1/syncthing-android#1182. You should now see the icon and screenshots :)

The official F-Droid client and f-droid.org also check en-GB and plain en for metadata. That's why the official client and website showed an icon, but Neo Store didn't.

@machiav3lli machiav3lli reopened this Jan 23, 2025
@machiav3lli
Copy link
Member

@leoheitmannruiz thanks for the insights. I should be able to patch things up for next release

@leoheitmannruiz
Copy link
Contributor

For the record: I'm not convinced that additionally checking en and en-GB is a good idea for Neo Store. The whole metadata and locale situation at F-Droid is sadly a little wishy-washy, I find. en-US is the default locale, but then en and en-GB are also checked, but en-US is preferred.

I think I'd like the F-Droid project to commit to either: "en-US is the default locale, all apps have to use it" and update the behavior of their client and their website or "en, en-GB, and en-US are fine, all apps have to use one of them".

I'm definitely not sure though.

I've been wanting to open an issue about this for some time now. I think I'll do so later today or tomorrow. Perhaps you want to wait until I have a response? I'll gladly keep you updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants