Invalid package identity name and Invalid package family name

Question

when submitted my app in dev center, i got the info:

Invalid package identity name: GCProW10 (expected: NeerSoftwareTechnologyI.43024035B1E0F)
Invalid package family name: GCProW10_4c1znmvt0khkg (expected: NeerSoftwareTechnologyI.43024035B1E0F_4c1znmvt0khkg)

any suggestion?

Answer 1

Hi iconcool,
Your appxmanifest is probably incorrect. You could select the project name within Solution Explorer and navigate to project -> Store->Associate App with the Store  right click your project->store->Associate App with the Store.
Select the existing store application or create a new one and your local package.appxmanifest will update .For the appxmanifest, you could compare the difference between before and after the association.
For more information about this , you can read this document: Windows Store: Error updating package – Invalid package family name

Best Regards

Daisy  Tian

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 2

Thank you very much,  you give me a way in Visual Studio, but my don't use it, I converted a installmyapp.exe to Appx with Desktop App Converter.

any suggestion?

Answer 3

Thank you very much,  you give me a way in Visual Studio, but I don't use it, I converted a installmyapp.exe to Appx with Desktop App Converter.

Answer 4

I package the Appx through DAC with the following commands:

DesktopAppConverter.exe -Installer C:\myapp\PackageFiles\ -AppExecutable “myApp.exe”-Destination C:\myapp -PackageName "myAppforW10"  -Publisher "CN=xxxx-1xxx-xx9B-xxC5-xxxxxF6DAF2C"  -Version 4.3.0.0 -PackageArch "x86"  -PackagePublisherDisplayName "myCompany" -MakeAppx -Sign -Verbose

The following errors are shown:
Invalid package identity name: myAppforW10(expected: myCompany.1234567EED192)
Invalid package family name: myAppforW10_4c1znmvt0khkg (expected: myCompany.1234567EED192_4c1znmvt0khkg)
This package’s manifest (Package/Properties/DisplayName) uses a display name that you have not reserved: myAppforW10

For the first question, I tried to solve the problem by adding -AppId parameters,  But I tried a lot of solutions to fail.
The second problem is that there is no method for setting up "package family name".

Please do not recommend Visual Studio packaging, I use other packaging programs for EXE installation packages, and some people recommend MakeAPPx.exe packaging, the problem is that after installation of SDK, I can not find MakeAPPx.exe at all.

Answer 5

Hi Newera,

> This package’s manifest (Package/Properties/DisplayName) uses a display name that you have not reserved: myAppforW10
It seems that you didn’t reserved the app name which you used (myAppforW10) in Dev Center before . Please make sure your PackageName which in the commands and the reserved name in the Dev Center are exactly the same.

> I tried to solve the problem by adding -AppId parameters
Could you change the Package/Properties/DisplayName to your reserved name in Dev Center and try again?

>Please do not recommend Visual Studio packaging
If you have Visual Studio 2017 and you do not need to add complicated features to your installer, consider using Visual Studio DAC template instead. The latest version of Visual Studio provides a new version of the packaging project that eliminates all of the manual steps that used to be necessary to package your app. The steps in the document : Package an app by using Visual Studio (Desktop Bridge)

> the problem is that after installation of SDK, I can not find MakeAPPx.exe at all.
First of all, you can find MakeAppx from the following location:
Based on your installation path of the SDK, this is where MakeAppx.exe is on your Windows 10 PC:
x86: C:\Program Files (x86)\Windows Kits\10\bin\x86\makeappx.exe
x64: C:\Program Files (x86)\Windows Kits\10\bin\x64\makeappx.exe

Actually to solve your problem, please check the following steps:
  1. You should first make sure you’ve set up the environment based on the following document: Package an app using the Desktop App Converter

  2. Then you can change the PackageName directly from your DAC command line by set this option: DesktopAppConverter.exe -PackageName <String>.
Alternatively you can also change the PackageName to the reserved name in your manifest file and then use MakeAPPx.exe to package your app. You can refer to Package an app manually (Desktop Bridge) and Create an app package with the MakeAppx.exe tool for more details about the steps.

Best Regards
Daisy  Tian

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 6

Where can i choose "project -> Store->Associate App with the Store"?   is Visual studio?

Answer 7

Hi Newera,
Yes, this is Visual Studio method. The most common and recommended packaging method is VS, so we offer you the VS method at the beginning. 
Then you explain that you were packing with DAC, if you still want to use DAC, could you try modifying appxmanifest to package again?You could refer to my above comments on DAC packaging and MakeAPPx.exe packaging.
Best Regards
Daisy  Tian

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].