I have a UWP application which we want to publish through side loading and the Windows store. We purchased a trusted code signing certificate. The subject of the certificate does not match the Package/Identity/Publisher assigned to us for our store app. When I set the appxmanifest Package/Identity/Publisher to match the certificate's subject the store rejects the application, but side loading. If I set the Package/Identity/Publisher to what the store assigned to us, add EnableSigningChecks=false to the .csproj file, and upload; the store still rejects the application with "Invalid package publisher name". It seems to use the subject from the certificate instead of what is in the .appxmanifest file.
I want the app's package name to be the same between the side loaded and store application so that a user could side load the application, but then later upgrade from the store. Currently the side loaded and store app would install side by side since Windows would consider them as different applications.
How can I use the trusted certificate with the different subject from Package/Identity/Publisher to create a side load and store app which resolve to the same package name so that they are considered the same application? Can Microsoft modify my app's Package/Identity/Publisher to match my certificate?