Skip to content

initial fastlane structures from IzzyOnDroid#3293

Merged
ahmedre merged 3 commits intoquran:mainfrom
IzzySoft:fastlane
Sep 20, 2025
Merged

initial fastlane structures from IzzyOnDroid#3293
ahmedre merged 3 commits intoquran:mainfrom
IzzySoft:fastlane

Conversation

@IzzySoft
Copy link
Copy Markdown
Contributor

this PR provides you with a "fastlane starter package" – to give it into your hands to define how your app is presented, and make it easy to keep descriptions & graphics in sync with your development. Some notes to sum them up in a place easy to find for you:

  • the IzzyOnDroid Fastlane Documentation can guide you with maintaining the structures here
  • take special care for limits, e.g. per-release changelogs can have max 500 chars, full_description.txt max 4,000 chars, graphics must have specific aspect ratios etc.
  • you can have "bigger graphics" here; the IoD updater takes care to resize/optimize them as needed
  • for the full_description.txt here I've used HTML compressed into a single line, to prevent the fdroid software converting each line break to a <br>. The tags used for this are supported by F-Droid.org as well, and to my knowledge even by PlayStore.
  • whenever you add a new "type" of metadata that has not been there before (e.g. the first changelog, a featureGraphic if it wasn't yet present), please let us know so we can check and enable it.
  • Details on all this in the linked documentation.
  • Once merged, your changes will be synced whenever a new release is pulled in here – to make sure it stays up-to-date with the app itself.
  • Should you have questions, be welcome to ask 😉

The second commit adds the missing IzzyOnDroid badge to the Readme.

And now: Enjoy!

@ahmedre
Copy link
Copy Markdown
Contributor

ahmedre commented Aug 16, 2025

Thanks for opening this PR - I am not using Fastlane today (using GitHub Actions) and this PR is adding resources - will these resources added in the correct folders allow IzzyOnDroid to automatically update the descriptions whenever a new deployment / new version is released?

@IzzySoft
Copy link
Copy Markdown
Contributor Author

I am not using Fastlane today (using GitHub Actions)

No contradiction. You will notice this PR does not include any Fastlane binaries, as those are not needed for the intended purpose (though you could use them of course if you wanted).

will these resources added in the correct folders allow IzzyOnDroid to automatically update the descriptions whenever a new deployment / new version is released?

Exactly that is the purpose of this PR, and about establishing these structures in your repo here, yes! Whenever a new release is being "pulled over", we also create a fresh clone of your repo, and then sync the fastlane tree – to bring over everything you might have changed, while unchanged files stay untouched. Quoting from the initial comment above:

Once merged, your changes will be synced whenever a new release is pulled in here – to make sure it stays up-to-date with the app itself.

@IzzySoft
Copy link
Copy Markdown
Contributor Author

@ahmedre any chance to get this merged? As we need to move on with our repo reorg at IzzyOnDroid, it would help us a lot. Thanks in advance!

@ahmedre
Copy link
Copy Markdown
Contributor

ahmedre commented Sep 20, 2025

I don't feel too keen on having a fastlane folder in the project when we don't support fastlane - but the docs say you're ok with one of either /metadata root or /src//fastlane/metadata/android// (though I guess if the latter is in the root directory it'd be more confusing).

can we go with the /metadata option instead?

@IzzySoft
Copy link
Copy Markdown
Contributor Author

Sure we can – I just stick to the standards, when possible. metadata/ as entry point is also understood by F-Droid. At IzzyOnDroid, we are fully flexible in that regarrd, and can use almost any entry point.

Give me a minute, I adjust that in my PR, as you suggest.

@IzzySoft
Copy link
Copy Markdown
Contributor Author

Done.

@github-actions
Copy link
Copy Markdown

OLD: app-madani-debug.apk (signature: V1, V2)
NEW: app-madani-debug.apk (signature: V1, V2)

          │          compressed          │         uncompressed         
          ├───────────┬───────────┬──────┼───────────┬───────────┬──────
 APK      │ old       │ new       │ diff │ old       │ new       │ diff 
──────────┼───────────┼───────────┼──────┼───────────┼───────────┼──────
      dex │  25.6 MiB │  25.6 MiB │  0 B │  78.2 MiB │  78.2 MiB │  0 B 
     arsc │   2.1 MiB │   2.1 MiB │  0 B │   2.1 MiB │   2.1 MiB │  0 B 
 manifest │   6.1 KiB │   6.1 KiB │  0 B │  29.7 KiB │  29.7 KiB │  0 B 
      res │   1.8 MiB │   1.8 MiB │  0 B │     2 MiB │     2 MiB │  0 B 
   native │  18.8 KiB │  18.8 KiB │  0 B │  36.5 KiB │  36.5 KiB │  0 B 
    asset │ 452.1 KiB │ 452.1 KiB │  0 B │ 808.2 KiB │ 808.2 KiB │  0 B 
    other │ 198.3 KiB │ 198.3 KiB │ +4 B │ 495.1 KiB │ 495.1 KiB │  0 B 
──────────┼───────────┼───────────┼──────┼───────────┼───────────┼──────
    total │  30.1 MiB │  30.1 MiB │ +4 B │  83.6 MiB │  83.6 MiB │  0 B 

@ahmedre
Copy link
Copy Markdown
Contributor

ahmedre commented Sep 20, 2025

thanks, merging - heads up though I am planning to push another update to the apk hopefully this weekend as I iron out issues from the current release

@ahmedre ahmedre added this pull request to the merge queue Sep 20, 2025
Merged via the queue into quran:main with commit f4b1053 Sep 20, 2025
2 checks passed
@IzzySoft
Copy link
Copy Markdown
Contributor Author

Thanks! Activated at our end now. Changes you apply now will be synchronized whenever a new release is being pulled in – which, as usual, should be detected automatically and pulled within 24h of your making it and attaching an APK to it.

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

Successfully merging this pull request may close these issues.

2 participants