App does not launch immediately after installation but after a 40 mins delay it launches again

%3CLINGO-SUB%20id%3D%22lingo-sub-1972161%22%20slang%3D%22en-US%22%3EApp%20does%20not%20launch%20immediately%20after%20installation%20but%20after%20a%2040%20mins%20delay%20it%20launches%20again%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1972161%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20a%20really%20strange%20issue%20and%20I%20can't%20figure%20out%20the%20root%20cause.%3C%2FP%3E%3CP%3EWe%20have%20a%20WPF%20app%20that%20gets%20packaged%20into%20MSIX%20using%20Azure%20pipelines.%20A%20self%20signed%20certificate%20is%20using%20for%20signing%20the%20package%20which%20is%20created%20by%20me.%20If%20I%20push%20my%20code%20to%20the%20repo%20and%20trigger%20the%20pipeline%2C%20the%20MSIX%20artifact%20installs%20and%20launches%20without%20any%20issues%20for%20every%20software%20developer%20in%20our%20team%20but%20if%20someone%20else%20pushes%20code%20to%20the%20repo%2C%20the%20MSIX%20artifact%20%3CSTRONG%3Ewould%20install%20but%20not%20launch%3C%2FSTRONG%3E%20for%20them%20for%20approximately%2035-40%20minutes%20after%20installation%20and%20then%20magically%20start%20launching%20after.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20only%20happens%20to%20the%20developers%20(except%20me%20the%20publisher%20of%20the%20certificate)%20who%20have%20access%20to%20the%20source%20code%20and%20can%20trigger%20the%20pipeline%20by%20updating%20the%20repo.%20We%20have%20distributed%20the%20MSIX%20installer%20to%20end%20users%20numerous%20times%20and%20no%20one%20has%20had%20any%20issues%20launching%20the%20app%20after%20installation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20experienced%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3EMo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1972161%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMSIX%20LIMITATIONS%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMSIX%20MSIXINTERACTION%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1991831%22%20slang%3D%22en-US%22%3ERe%3A%20App%20does%20not%20launch%20immediately%20after%20installation%20but%20after%20a%2040%20mins%20delay%20it%20launches%20again%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1991831%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F896369%22%20target%3D%22_blank%22%3E%40Mo_Velayati%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20the%20delay%20in%20launching%20the%20app%20happening%20only%20after%20the%20first%20installation%2Fdeployment%20from%20the%20CI%2FCD%20pipeline%20or%20does%20it%20take%20place%20for%20all%20launches%20other%20users%20try%20to%20make%20after%20the%20app%20is%20initially%20installed%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECheers%2C%3C%2FP%3E%0A%3CP%3ETanaka%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1995038%22%20slang%3D%22en-US%22%3ERe%3A%20App%20does%20not%20launch%20immediately%20after%20installation%20but%20after%20a%2040%20mins%20delay%20it%20launches%20again%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1995038%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F387730%22%20target%3D%22_blank%22%3E%40Tanaka_Jimha%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20Tanaka%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20happens%20every%20time%20someone%20except%20me%20(Author%20of%20the%20self-signed%20cert)%20pushes%20code%20and%20therefore%20triggers%20the%20pipelines.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3EMo%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

This is a really strange issue and I can't figure out the root cause.

We have a WPF app that gets packaged into MSIX using Azure pipelines. A self signed certificate is using for signing the package which is created by me. If I push my code to the repo and trigger the pipeline, the MSIX artifact installs and launches without any issues for every software developer in our team but if someone else pushes code to the repo, the MSIX artifact would install but not launch for them for approximately 35-40 minutes after installation and then magically start launching after.

 

This only happens to the developers (except me the publisher of the certificate) who have access to the source code and can trigger the pipeline by updating the repo. We have distributed the MSIX installer to end users numerous times and no one has had any issues launching the app after installation.

 

Has anyone experienced this?

 

Best,

Mo

5 Replies

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,

Tanaka

@Tanaka_Jimha 

 

Hi Tanaka,

 

This happens every time someone except me (Author of the self-signed cert) pushes code and therefore triggers the pipelines.

 

Best,

Mo

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,

Tanaka  

@Tanaka_Jimha 

 

We distribute the .msix and the .cert manually. We put the files on a shared drive and end users install it from there.

The interesting thing is that no matter where we install the .msix from, the issue still remains. And it only happens to the Developers who have access to the source code and can trigger the pipelines, not the end users. Even if the developers download the files directly from the pipeline drop location, they still see the issue.

 

Best,

Mo

@Mo_Velayati 

Are you able to file a feedback item on the affect devices so we can get more information to investigate?  Meanwhile you can also look for more information in the event logs.


Event Viewer (Local) > Applications and Services Logs > Microsoft > Windows > AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational

 

John Vintzel (@jvintzel)
PM Lead, MSIX