question

90730225 avatar image
1 Vote"
90730225 asked MahmutYiit-2081 commented

Why is my package name different from the package family name?

I have associated my app with an app on the store. However, when I associate, the package name that gets generated is:

AssistXEducationLLC.ClassPolicyNext_5.0.0.0_x86__mq2ssdmyrpmy0

However, when I publish my package and upload it, the store expects:

Invalid package family name: AssistXEducationLLC.ClassPolicyNext_mq2ssdmyrpmy0 (expected: AssistXEducationLLC.ClassPolicyNext_0nrwxyh4sza08)

My package family name as shown in the manifest is correct, so why the mq2ssdmyrpmy0?

65479-vspackagename.png65480-msstoreerror.png



partner-center-general
vspackagename.png (52.7 KiB)
msstoreerror.png (38.6 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The package family name is the combination of YourProjectName and TemporaryKey. And the Temporaraykey is a hash value of the Publisher. PFN(Package family name) gets automatically populated as a combination of Package name and the Temporarykey. It just changes with the value of Publisher changing. But it will always be a hash value not a meaningful name.

Could you please try to choose the right certificate manually in Visual Studio and then package the app again?


0 Votes 0 ·

Since the certificate I used is expire, I re-created the certificate and performed the associate process. However, I am having the same problem. Is there any improvement regarding this problem?

0 Votes 0 ·

0 Answers