microsoft / microsoft/msstore-cli
How to update a paid app
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 163
- Forks
- 22
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Part of GitHub Actions, I am trying to build and update a paid app in the store.
I understand that this is not possible directly at the moment, so I wonder what other options I have?
Right now, I build like this:
msstore package MyApp --arch x64 --version "1.0.${{ github.run_number }}.0"
Then publish to flight like this:
msstore publish MyApp -id 123 -f 123 -i MyApp\AppPackages
Then I would manually "Start update" process and select the package from the TestFlight as a source, instead of manually compiling and uploading.
However, it always ends up as a flight version, and not as the package version that I packaged (package file name is correct)
Is there a way to fix this package version via flights, or a different way to automate the new paid app version release?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the msstore package and msstore publish commands in the issue, then follow the resulting package through the flight and “Start update” process. Determine whether the packaged version can be retained for a paid app and document a supported automated release path or the limitation that prevents it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- ci-cd, cli, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100