O365 MSIX package upload to Intune - The selected app package does not appear to have an app ID.

%3CLINGO-SUB%20id%3D%22lingo-sub-1430089%22%20slang%3D%22en-US%22%3EO365%20MSIX%20package%20upload%20to%20Intune%20-%20The%20selected%20app%20package%20does%20not%20appear%20to%20have%20an%20app%20ID.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430089%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20created%20a%20O365%20MSIX%20package%20using%20the%20MSIX%20packaging%20tool%20on%20a%20clean%20Windows%2010Home%20VM%20in%20order%20to%20try%20to%20deploy%20it%20using%20Intune%20to%20Windows%20Home%20machines%20as%20the%20C2R%20Office%20install%20in%20Intune%20is%20not%20available%20to%20deploy%20to%20Windows%2010%20Home%26nbsp%3B%20(id%20prefer%20not%20to%20have%20to%20deal%20with%20home%20but%20this%20is%20a%20consequence%20of%20the%20quick%20changes%20to%20WFH%20%2F%20COVID).%3C%2FP%3E%3CP%3EWhen%20I%20try%20to%20upload%20the%20MSIX%20package%20as%20a%20LOB%20app%20is%20reports%20that%20%22The%20selected%20app%20package%20does%20not%20appear%20to%20have%20an%20app%20ID.%22%20-%20im%20new%20to%20MSIX%20so%20im%20unsure%20how%20to%20fix%20this.%20I%20checked%20all%20fields%20in%20the%20package%20tool%20and%20everything%20is%20filled%20in.%20I%20look%20at%20teh%20manifest%20file%20and%20tried%20to%20add%20an%20%3CAPPLICATION%20section%3D%22%22%20with%3D%22%22%20an%3D%22%22%20id%3D%22%22%20element%3D%22%22%20but%3D%22%22%20wouldnt%3D%22%22%20work.%3D%22%22%3E%3C%2FAPPLICATION%3E%3C%2FP%3E%3CP%3EHow%20can%20I%20fix%20this%20error%20and%20get%20an%20ID%20into%20the%20package%20plus%20is%20what%20im%20trying%20going%20to%20work%20anyway%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1434025%22%20slang%3D%22en-US%22%3ERe%3A%20O365%20MSIX%20package%20upload%20to%20Intune%20-%20The%20selected%20app%20package%20does%20not%20appear%20to%20have%20an%20app%20ID.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1434025%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F646041%22%20target%3D%22_blank%22%3E%40PhilRiceUoS%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3EWhen%20the%20MSIX%20Packaging%20Tool%20generates%20a%20package%20it%20creates%20Application%20elements%20that%20represent%20the%20entry%20points%20to%20your%20application%20and%20each%20has%20an%20App%20ID.%20You%20can%20see%20the%20entry%20points%20that%20were%20detected%20by%20the%20tool%20in%20the%20%22First%20launch%20tasks%22%20page.%20If%20you%20don't%20see%20your%20app's%20entry%20point%20here%2C%20you%20can%20add%20them%20with%20the%20%22Browse%22%20button.%3C%2FP%3E%0A%3CP%3EPlease%20let%20me%20know%20if%20that%20helps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELuis%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1441499%22%20slang%3D%22en-US%22%3ERe%3A%20O365%20MSIX%20package%20upload%20to%20Intune%20-%20The%20selected%20app%20package%20does%20not%20appear%20to%20have%20an%20app%20ID.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1441499%22%20slang%3D%22en-US%22%3E%3CP%3Eyes%20%2C%20I%20have%2Fsaw%20those%20in%20the%20manifest%20file%20but%20it%20still%20gives%20me%20the%20error%20of%20no%20App%20ID.%20Ive%20not%20had%20a%20whole%20lot%20of%20time%20to%20work%20on%20this%20since%20posting%20but%20I%20did%20try%20creating%20a%20MSIX%20file%20using%20Advanced%20Installer%20(converting%20MSI%20to%20MSIX)%20and%20noticed%20that%20the%20publisher%20CN%2C%20Application%20name%2C%20version%20etc%20where%20all%20pulled%20from%20the%20MSI%20and%20it%20made%20me%20think%20that%20is%20probably%20the%20issue%20-%20I%20put%20my%20own%20details%20in%20those%20fields%20when%20creating%20the%20MSIX%20first%20time%20round%20and%20it%20likely%20checks%20to%20see%20if%20they%20are%20registered%20in%20the%20Store%20(which%20they%20are%20not).%3C%2FP%3E%3CP%3EWould%20that%20sound%20like%20the%20cause%20of%20the%20issue%20-%20Ive%20not%20had%20a%20chance%20to%20try%20uploading%20on%20of%20those%20to%20Intune%20to%20test.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

I have created a O365 MSIX package using the MSIX packaging tool on a clean Windows 10Home VM in order to try to deploy it using Intune to Windows Home machines as the C2R Office install in Intune is not available to deploy to Windows 10 Home  (id prefer not to have to deal with home but this is a consequence of the quick changes to WFH / COVID).

When I try to upload the MSIX package as a LOB app is reports that "The selected app package does not appear to have an app ID." - im new to MSIX so im unsure how to fix this. I checked all fields in the package tool and everything is filled in. I look at teh manifest file and tried to add an <Application section with an ID element but wouldnt work.

How can I fix this error and get an ID into the package plus is what im trying going to work anyway?

2 Replies
Highlighted

Hi @PhilRiceUoS,

When the MSIX Packaging Tool generates a package it creates Application elements that represent the entry points to your application and each has an App ID. You can see the entry points that were detected by the tool in the "First launch tasks" page. If you don't see your app's entry point here, you can add them with the "Browse" button.

Please let me know if that helps.

 

Luis

Highlighted

yes , I have/saw those in the manifest file but it still gives me the error of no App ID. Ive not had a whole lot of time to work on this since posting but I did try creating a MSIX file using Advanced Installer (converting MSI to MSIX) and noticed that the publisher CN, Application name, version etc where all pulled from the MSI and it made me think that is probably the issue - I put my own details in those fields when creating the MSIX first time round and it likely checks to see if they are registered in the Store (which they are not).

Would that sound like the cause of the issue - Ive not had a chance to try uploading on of those to Intune to test.