-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure during setup: is not a supported archive file format. .zip is the only supported archive file format.
#171
Comments
is not a supported archive file format. .zip is the only supported archive file format.
Interesting. This doesn't seem to be an issue on the task itself, but rather an issue on PowerShell extraction the task to be run. It seems like it is using PowerShell v1.0, and our tests are running on pwsh v7. |
Could it be related to the fact that I'm using I'm also building a new AMI with pwsh v7, so I can try that out as well. |
The changes were minimal, actually. Lots of refactoring to support ADO and share most of the code/logic. We are due to shipping a 1.1, but that would be more on MacOS, so unlikely to be related. Let me know if pwsh7 fixes this. |
updating to pwsh7 seems to have fixed it, but now msstore-cli is failing to run because it needs dotnet 8 installed. Building a new AMI. |
Yes, we are working on getting it AOT compiled, which will remove the .net runtime requirement as it would ship as part of the exe itself. |
hey @azchohfi I'm seeing the following error message now:
What's it looking for when it says |
sorry for pinging you again @azchohfi do you have any idea whats going on here? |
TLDR: remove "-i":
@AnalogJ the publish command is the right one, but I see that you are running:
You need to pass the argument, not the option. Since you are not providing one, it is using the current path, which probably doesn't have a project file it can work with, or an MSIX. I see how the documentation might be confusing. The MSIX publishing scenario was added later, since the publish command's intent is only publish the app, but it is complimentary to the init command, which finds, builds, packs, and publishes your project. We support: I think the best course of action is to update own documentation, as I agree that it can be clearer. If someone, like you, is looking only for publishing an MSIX, it is misleading into thinking that you need to use the inputDirectory option (which should be used only if you want to change the default output directory to search for the built MSIX, depending on the type of project). https://learn.microsoft.com/en-us/windows/apps/publish/msstore-dev-cli/publish-command |
so I tried the following commands:
and I got the same error:
Then I thought that maybe it would make sense to "cd" into the correct bin director before starting the publish (but note how I left the argument blank):
and I got the following output:
Now I'm trying with the filename as an argument:
but It'll be about 30 minutes before I find out if it works or not :( |
Nice, got a new error now!
results in:
Looks like the main error is: |
I found microsoft/msstore-cli#14 which seems to imply that i need to call I eventually created the following pubspec.yaml file: msix_config:
display_name: Fasten Health
publisher_display_name: Fasten Health, Inc
identity_name: FastenHealthInc.FastenHealth
msix_version: 1.0.8.0
publisher: CN=94E2XXXX-XXXX-XXXX-XXXX-XXXXXXXXB278
msstore_appId: 9PLXXXXXXXXP
store: true
then I tried running Still getting running
|
Hey @azchohfi just checking in, is there a documented way to deploy a stand-alone msix to the Microsoft Store using the cli? |
Hey @azchohfi sorry to keep bothering you -- I'm just trying to figure out if this is working as intended and if I need to look for another tool to help me publish artifacts to the windows store. Since this is unrelated to the setup-msstore-cli, I can open an issue in the other repo |
Init is for project configuration, not for MSIX. It writes the app id in the project file, whatever that is, so you don't need to pass it all the times. If you want to publish MSIX, just pass the --appId or -id option. The documentation was not updated with this new param. Our miss, sorry. I'll send a fix for the docs. |
confirmed! adding the --appId flag worked. Thanks so much @azchohfi! |
Hi,
I'm trying to run
setup-msstore-cli
on a Github Actions Self-hosted runner.I'm getting the following error message:
It seems to be failing during package extraction, but I'm not sure which tool is missing in my self-hosted runner image (the extension seems to be blank).
Here's the relevant part of my GH Actions workflow
The text was updated successfully, but these errors were encountered: