This is all good on your side. OpenSSL issue is blocking simple workflow and thus documentation. Only decision on it is needed. I bumped the issue on Julia and also linked two related PR’s to the original issue for visibility. Hope we find some good will.
Here are my remarks. It is still partial testing as I am waiting for some non-appbundler bugs to be resolved and still using 1.11.
When 0.6 is run with old build script (depreciated build_app) got error:
ERROR: LoadError: UndefVarError:
Windowsnot defined inMain
Stacktrace:
[1] top-level scope
@ E:\App\meta\build.jl:28
in expression starting at E:\App\meta\build.jl:27
The error looks trivial, but still wanted to post it as I think most existing scripts will run into this error. Did not proceed with further testing with old script.
With new script I used JuliaAppBundle spec. Process completes as expected. Installed app also runs in line with 0.5 installation. This does mean however that zombie process issue #27 still persists, i.e. it is left running after the UI is closed (with windowed=false the black terminal keeps running). Will see if it goes away with JuliaC when I try it.
One small note regarding msix installation wizard, I am missing “Launch when ready” selector and just always launches on finished installation. Launch when ready can be seen in v0.3 announcement video up above.
1 Like
Thank you for your remarks. During my testing, I noticed that applications built with JuliaC did not have a zombie process; perhaps you can confirm that.
Regarding the installation wizard option "Launch when ready”, I just checked and it is indeed no longer present. I also verified with an app I built shortly after the v0.3 release in June and did not see it there either. I wonder if it is because Windows itself changed something, but looking at other MSIX installers, I see it is still present 
It might be worth trying configuration file overrides meta/msix/AppxManifest.xml and meta/msix/MSIXAppInstallerData.xml. You can find them in the AppBundler.jl repository under the recipes folder, placed at those locations where they will be automatically recognised when MSIX constructor is called.
Also, by the way, was the icon in the installer wizard rendered correctly? Meaning there was no blue background like in the following example:
I have been struggling to understand when it appears and when it does not, which should be controlled by
MSIXAppInstallerData.xml, but sometimes it stops working.
Unfortunately, even with JuliaC I still have zombie process left running. However, it takes less RAM than before. Some 11 MB instead of ~23 MB.
To have “Launch when ready” this needs to be true:
AllowUserInteraction="true" in MSIXAppInstallerData.xml.
Logo background is green for me 
That green color is set in general Windows personalization settings as shown below.
Will make PR when fixed, but it still persists even when transparent is swaped for gray.
Seems like v0.3 second video msix installer was made with older AppBundler (presumably 0.2) as it has “Launch when ready option” and good background color. Maybe reverting or modifying msix configuration files from there would make sense. If you have ideas let me know so the fix is easier.
Thanks. I will have a look on AllowUserInteraction="true"
This is frustrating. I have literally reinstalled Windows at one point and found that the background colour is correctly specified by the MSIXAppInstallerData.xml, but then it flips to a blue background after a while.