Change the package name

[Artem13327]

This should be done so that the applications are not confused with https://f-droid.org/packages/com.andrew.apollo/. However, it will be necessary to continue releasing updates with the old package name for some time with a notification that you need to use a new application so that old users understand that you need to download an application with a new package name

[nuclearfog]

I'll change the package name but I'm not sure if the izzysoft repo https://apt.izzysoft.de/fdroid/index/apk/com.andrew.apollo can handle this.

[Artem13327]

This should be asked from @izzysoft. Maybe it's just worth releasing an update with both the old and the new package name and adding a notification in the old one that you need to switch to the new application

[IzzySoft]

Well put, Artem – and yes, if a change of the applicationId is really needed, that should be the way to address it. Ideally giving me a forewarning so I am prepared. Let me check how the updater is set up for this app…

AutoUpdateMode: Version %v
UpdateCheckMode: Tags

OK, checking latest releases – but no specification of the file name. That would mean if you put both APKs on the same tag, my updater would simply fetch one randomly – which would be not good. So:

I guess you want to keep the file name to Apollo.apk for the future? Then I'd set that now. On the release having both APKs, my updater would then fetch the new one and yell at me that the packageName does not fit (while it will not publish the new one) – which then would serve as a signal to me to pull the "other one" manually and re-configure your app in my repo. I'd then give it an overlap for a month or so before removing the old variant, so whoever has it installed has sufficient time to get the warning and to take proper action.

One thing not to forget: changing the package name means essentially it's a new app – so no "simple update", but uninstall/reinstall. Please have a migration path available if needed (like an export/import feature to transfer data over to the new one).

[nuclearfog]

I'll change the package name in the next release but I'll keep the filename.

[IzzySoft]

OK. Will you also provide the second variant for that release (using a different filename then of course), as suggested? Otherwise there are no means to send out notifications to existing users that they need to switch. Some might not notice at all, and complain that updates have stopped (hey, some of them will complain to me, so I have a special interest here, too :see_no_evil:).

[Artem13327]

@IzzySoft the package name has been changed. Do something with https://apt.izzysoft.de/fdroid/index/apk/com.andrew.apollo

[IzzySoft]

Too late, that's already gone. There was no second APK (as discussed above), so I simply renamed everything on my end. Your app is now online with the new package name; be welcome to pick a badge and link there e.g. from your Readme :wink:

[Artem13327]

@nuclearfog

[nuclearfog]

Sorry, but I've lost the signing key for the old APK

[IzzySoft]

Ah, that's why no "last hint" with the old name, I see. Well, as it's a new package name one has to perform a fresh install anyhow. But what Artem meant by pinging you (at least that's my guess) was mostly that my previous comment was rather addressed to you than to him, and you might wish to accept my "badge offer" :wink:

While on it: what do you think about establishing Fastlane structures here? That way you'd be in control of the app description and graphics used. I could send you a "starter package" via PR – and you could always refer to my Fastlane Cheat Sheet for guidance when needed.

[Artem13327]

@nuclearfog

[nuclearfog]

Yes that would be great!

[IzzySoft]

There you go then!

[Artem13327]

I think we can close