User Profile
Tanaka_Jimha
Former Employee
Joined Aug 05, 2019
User Widgets
Recent Discussions
Re: App does not launch immediately after installation but after a 40 mins delay it launches again
Hi Mo_Velayati, Does your CI/CD pipeline also install the app on users' machines, and how does it do so? Or is the installation driven by the end user. I'm trying to understand the specific scenario in which the app launch is delayed. Thanks, TanakaRe: App does not launch immediately after installation but after a 40 mins delay it launches again
Hi Mo_Velayati Is the delay in launching the app happening only after the first installation/deployment from the CI/CD pipeline or does it take place for all launches other users try to make after the app is initially installed? Cheers, TanakaRe: Error parsing app package
BrianShekkt Is the download page publicly available for our team to investigate? If it isn't can you please file an item in Feedback Hub (Win + F) while reproducing the issue. Please file it under the category Apps > AppInstaller. Please also attach a copy of your .appinstaller file + package, if possible. Thanks, TanakaRe: Error parsing app package
Hi BrianShekkt, Does this fail when clicking on the .appinstaller uri on a webpage? Can you please share what your download uri looks like on the page. Also, there's a known App Installer install/caching issue which can be fixed by a restart, please try and see if a restart of your machine fixes the issue. Cheers, TanakaRe: Appxmanifest Identity Publisher contains ST=Oregon instead of S=Oregon
Hi dmondou Did you confirm that signing fails when you set S=Oregon in the manifest? I chatted with the team and they said the validation uses this CertNameToStr function - CertNameToStrA function (wincrypt.h) - Win32 apps | Microsoft Docs and it says "The string representation follows the distinguished name specifications in RFC 1779 except for the deviations described in the following list: The X.500 key name for stateOrProvinceName (2.5.4.8) OID is "S". This value is different from the RFC 1779 X.500 key name ("ST"). " Unfortunately it looks like ST=Oregon will not work, and you'll need a subject name with S=Oregon.Re: Customizing Visual Studio MSIX packaging project output
Hi MattGregory , The output directory of the packages is defined in the Microsoft.AppxPackage.Targets file at C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage (depending on your version of Visual Studio). If you want to remove the "_Test" suffix you can modify the lines defining the output directory. In my file it was around line 3190 - 3196: To modify the output html file, modify the index.template.html file in the "Landing" subdirectory - C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Landing (depending on VS version). Cheers, TanakaRe: Write to non virtualized %APPDATA% location from MSIX installed binary
Hi davidanthoff, Yes, you can request approval when submitting your package and explain why Julia needs it and is in the same category as Python. The process is outlined here - https://docs.microsoft.com/en-us/windows/uwp/packaging/app-capability-declarations#restricted-capabilities. You can also get approval before you're submitting your app which is probably the better option in your case, the page says "To do so, visit the Windows Developer support page. Select Developer support topic Dashboard issue, Issue Type App submissions, and Subcategory Other. Then describe how you are using the capability and why it is necessary for your product. If you do not provide all the information necessary, your request will be denied. You may also be asked to provide more information. Note that this process typically takes 5 business days or longer, so please submit your request well in advance." Cheers, Tanaka
