Google Play Release

[d4rken]

Do we? Do I? want this?

• Graphic Assets
• Screenshots
• Description texts (could use the ones provided by @IzzySoft)
• Can we automate releases via fastlane

[dragonGod97677]

I agree on description text and automate release

[IzzySoft]

I'd strongly suggest including at least some screenshots with your Fastlane structure. People are much more like taking a closer look if they have some visual impression. Should you use Fastlane binaries to automate playstore release, the very same screenshots would be deployed there as well (including icon and featureGraphic, if you included them). So "one ring to rule them all" 😉

[d4rken]

Of course, 2 screenshots are mandatory for gplay anyways 😉.

My fastlane skills are a bit rusty, ideally I would like to have this all very automated, more automated than my other apps, seeing as this a fresh project where things can go a bit wrong at the start 😁

Does fastlane support bundle signing + upload? 🤔
Last time I set fastlane app, we could all still use APKs 🥲

[IzzySoft]

I've no idea about details on what the fastlane binaries can achieve, sorry – I work with the structures/metadata only. As bundles are now rather mandatory at Play (and devs have to hand over their private parts… ahem, signing keys – and thus should better use diffoscope¹ on the resulting APKs to make sure nothing was added), I'd expect it to support them, though.

My fastlane skills are a bit rusty

If you let me know and can cross-check once the structures are up, just send me a ping then. I'll have to do that anyway to tell my updater what to pick and how to handle it.

---

¹ _{F-Droid uses diffoscope for reproducible builds}

[d4rken]

As bundles are now rather mandatory at Play (and devs have to hand over their private parts… ahem, signing keys – and thus should better use diffoscope¹ on the resulting APKs to make sure nothing was added), I'd expect it to support them, though.

Yeah huge dislike from my end too. Actually rushed out a (yet to be released) alpha pre-deadline to still get grandfathered into the APK only option...

If you let me know and can cross-check once the structures are up, just send me a ping then. I'll have to do that anyway to tell my updater what to pick and how to handle it.

Will do ❤️

[IzzySoft]

Hehe… heard of several devs applying for the "grandfathering option". A pity such a thing is necessary.

Looking forward to your ping then!

[dragonGod97677]

Ill provide screenshots when the permissions tab is sorted out.

[IzzySoft]

Just let me know when they are there in Fastlane so I can tell my updater ow to handle them. Thanks!

[d4rken]

@dragonGod97677 what do you think about the current permissions tab?

[dragonGod97677]

@dragonGod97677 what do you think about the current permissions tab?

It's perfectly fine, I'll create a issue ticket when theres need a adjustment or something

[d4rken]

@dragonGod97677 v0.9.0 currently building, I think we can take a few screenshots for Google Play now, what do you think?

[dragonGod97677]

Permission Pilot Screenshots.zip
Here's the screenshots, I've done some oopies so.... i have to re-zip it and reupload it

[d4rken]

@IzzySoft https://github.com/d4rken-org/permission-pilot/tree/main/fastlane/metadata/android/en-US/images does that work for you?

[d4rken]

v1.0 is building

[IzzySoft]

@d4rken thanks, but the structure needs a little adjustment. Can you create a phoneScreenshots directory inside images/ and move the screenshots there (leaving icon & featureGraphic where they are)? See my Fastlane Cheat Sheet for details on the structure etc.

[d4rken]

Like this? 8a2d406

[IzzySoft]

Perfect, yes! I've already placed them here manually so you don't need to wait for the release to have them showing up – they will with the next sync today at around 6 pm UTC. Thanks a lot!

[IzzySoft]

PS: as for https://github.com/d4rken-org/permission-pilot/tree/main/fastlane/metadata/android/en-US/changelogs – file names there should be <versionCode>.txt so they show up for the matching release 😉 If you let me know once those are there, I can enable them as well.

[d4rken]

PS: as for https://github.com/d4rken-org/permission-pilot/tree/main/fastlane/metadata/android/en-US/changelogs – file names there should be <versionCode>.txt so they show up for the matching release wink If you let me know once those are there, I can enable them as well.

A default shows up by default for all other releases 😉
I won't be creating manual release notes for for most Google Play release.
Trying to keep overhead for updating the app low.
Have not found a good way to automate this.

[IzzySoft]

OK, no prob – was just mentioning it as the corresponding directory was there. If you usually put a summary like on v0.9.0-RC0 I could instead add a changelog link to the app listing in general, so users can follow that. Just if you want, no pressure.

[d4rken]

If you usually put a summary like on v0.9.0-RC0 I could instead add a changelog link to the app listing in general, so users can follow that. Just if you want, no pressure.

The changelogs on Github are generated, v0.9.0 looks nice because i did some features via PRs (required for the generation) instead of direct pushes to main.

I have not found a nice way to generate changelogs based on both PRs and commits.

If the app becomes more popular I will be a bit more tidy and do more things via PRs so changelogs should be nicer 😁.

I think a link to the Github releases would be great, they are the main "truth" for release notes. Google Play release notes will always only be a subset of that.

[IzzySoft]

OK, added the link then. Might also serve as motivation 😛