Screenshot File Naming Guidelines for F-Droid

I’m having trouble submitting screenshots for my app to the F-Droid directory. The app itself is published correctly, including the description and builds, but the screenshots aren’t. In the repository they’re located in the fastlane/metadata/android/en-US/images/phoneScreenshots folder and are named 01.png and 02.png.

At fastlane/supply/README.md at 2.28.7 · fastlane/fastlane · GitHub , it says “image names are irrelevant,” but at All About Descriptions, Graphics, and Screenshots | F-Droid - Free and Open Source Android App Repository , it’s strictly stated that the names must be 1.[ext], 2.[ext], etc.

I’ve read that F-Droid uses a metadata structure inspired by Fastlane (and is compatible with it in terms of directories and locales), but it doesn’t adhere entirely to it: in particular, they require strict sequential numbering for screenshots without leading zeros (1.png, 2.png, etc.). This is intended to simplify parsing and sorting in their fdroidserver system.

Is this true, and could screenshot filenames starting with zero prevent them from being uploaded to F-Droid, or is there another issue with the Fairphone Checkup app?

Is there any official evidence for this?

The names do not matter

The published version has no fastlane: GitHub - WeAreFairphone/FP2-Checkup at 2.2.2

Future relased versions will…

The names do not matter

@Licaon_Kter, there’s no direct evidence for this either? I’m not sure if the example from the official manual should be taken literally.

The published version has no fastlane

Can an app be published without having files formatted according to the Fastlane syntax in the repository? Was it added manually without reference to the Fastlane files in the app repository?

Future relased versions will…

Do I need to somehow initiate this process, or did it just happen naturally in the two and a half years since the last release?

Since which version of fdroidserver have screenshot file names become unimportant?

As an F-Droid Contributor, could you check the F-Droid GitLab CI build logs for community.fairphone.checkup?

Can you tell me if the parser sees our files and why it ignores them?

The files are used from the tree of the release.

If you updated some files in the last 2-3 years, please make a new proper release so these are used.