-
Notifications
You must be signed in to change notification settings - Fork 72
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
[BUG] Null check operator used on a null value #126
Comments
Hello @VeArnold Thanks for this bug report. All your args look good and valid. Details: So I published a new version (3.6.1), with validation on that, Please update if it solves the problem. |
Hi @YehudaKremer! Thanks for the fast response. It fixed it to the degree that there's no weird error now, however, I am a bit confused about why the publisher field is required? In the 2.5.4 changelog it says:
What if I just want to create a "non-configured" MSIX package? I haven't used the package in a while, but back in November just running |
You can create msix without any configuration and args. (try it, run But, You need to set the |
Thanks again for the quick response, though this new Y/n prompt seems to cause some issues. I was previously able to run it without any prompts, or errors. Now regardless of whether I choose Y or N, it errors. With choosing Y:
With choosing N:
Thus I don't see how there is an option to run it with out any args/flags or configuration. |
Do you run this with CI/CD automation? or normal usage? |
@YehudaKremer Well something in-between, I ran it in a CI/CD environment, but SSH'ed into it. (regardless it used to work fine with CI/CD) |
The new versions of this package have a default configuration for normal use. By default, the msix is signing with the test-certificate, the All of those options are fully documented on the main documentation page. |
@YehudaKremer Thanks again for the answer. However, adding the
Thus I don't really understand what you mean. The In that sense, as the final clarification, previously Now it seems the minimum way to get it to work to any degree at all, is to have |
In addition, it would be nice if this change referenced in 3.6.1 could also account for the |
@YehudaKremer Hi thanks, I think I managed to get it to work, the issue seems to appear if you've already tried to package once and then go for another spin. In a fresh env, it's OK. Thanks! |
I'm very happy to hear that! But anyway, if this or another problem appears again, please let me know, I will spawn some ci/cd automation and check it. |
ℹ️ Info
Version:
msix-3.6.0
💬 Description
Can not successfully build an unsigned package with version 3.6.0 of the tool.
a) I want to run the
flutter build windows
step separately, thus I added the--build-windows
false flagb) The CI/CD pipeline gets stuck at the prompt to install the certificate, so I added the
--install-certificate
flagc) As I just want an unsigned package, I added the
--sign-msix
flagHowever, this results in the following traceback:
Note that the same happens with my old project (which used to work), and also a totally clean new Windows Flutter project. In addition, also happens if I just use:
flutter.BAT pub run msix:create --build-windows false --sign-msix false
📜 Pubspec.yaml
Attached is the very basic Pubspec file.
The text was updated successfully, but these errors were encountered: