Closed CampelloManuel closed 1 year ago
You can't publish it since I control the package name.
I can look into automating it with fastlane.
@CampelloManuel can you email me an address which I can grant access for the play store?
you can send it to
jonas at cowboyprogrammer.org
Sent. Soon I'll make a release so you can use that for the play store.
@spacecowboy the release 7.1.0 is ready. I'd like to publish it on the play store. How do we proceed ?
I haven't enabled the play store developer console thing on my google account, because I have never worked with the play store as a developer before.
I can do it if it is needed. I do have some personal apps that I may publish anyway...
no, wait, I'll fix #460 and then we will publish it
When we publish the app on the play store, I would like it to remain free, as in "without a price". If you want we can integrate some crowdfunding platform, but I think it should remain optional. I see that you have other free apps on the play store, so this will not be a problem, I imagine ?
When we publish the app on the play store, I would like it to remain free, as in "without a price". If you want we can integrate some crowdfunding platform, but I think it should remain optional. I see that you have other free apps on the play store, so this will not be a problem, I imagine ?
Of course it should remain free.
Also I'm thinking we should add a gradle flavor with another applicationId ending in .play
. It's good practice to have a different applicationId in different stores.
This will also enable me to generate new release keys to be used for the app, and share those with you.
Oh, I see. I'm afraid I deleted the play
flavor when I was removing non-free components and dependencies. I'll try to add it back, before the next release.
It's good practice to have a different applicationId in different stores
May I ask why ?
It's good practice to have a different applicationId in different stores
May I ask why ?
It's convenient to be able to install from both stores at the same time. Usually only something a developer wants to do.
But ensures that people don't install from F-Droid, and then get errors from Play store saying it can't update the app or vice-versa.
But primarily it's so I can use a new key on the play store.
I added a new playStore
build variant with package id = com.nononsenseapps.notepad.play
.
Now, about this key you have to make,
is this something you can do on the repository before compiling,
or do I have to create a new github release ?
I can make a new release (7.1.4) even now, if you need it.
I've published 7.1.3 on the play store: https://play.google.com/store/apps/details?id=com.nononsenseapps.notepad.play
The automatic pipeline just needs a bit more because I accidentally used the wrong key for the first pipeline. The correct key will be possible to be used on Jan 25th so I'll merge after that
https://github.com/spacecowboy/NotePad/actions/runs/3981806695/jobs/6830841756
Ok. Once you merge that, we can release the new 7.1.4.
To publish future updates on the play store, what do I need to do ? Do I just have to run a script, or is there more to it ?
Ok. Once you merge that, we can release the new 7.1.4.
To publish future updates on the play store, what do I need to do ? Do I just have to run a script, or is there more to it ?
Nothing at all. Make a tag and push it. The fastlane pipeline will be configured to run on (all) tags.
By releasing the 7.1.5 update on the play store I confirm that:
@spacecowboy is there something I need to do on the repository to prepare for the play store ? Are you going to handle the publishing process ? If you want, I can try to do it, but I have never published on the play store before, so I have to setup everything.