I can not install it

[ruizlenato]

Request a new application package from the developer. This package may conflict with an installed package or depend on items that are not installed here (package dependencies). It may also have been created for another type of architecture (0x80073CF3)

[ziplock9000]

It's just worked fine for me.

[icedterminal]

AHA! SOLVED IT! @MahdiGhiasi , I am not sure what is going on here.

For some reason the install process just fails because the dependencies are not handled with the browser invoked request. At all. I do not understand why as I don't care much to learn about the development of UWP. That said here is what I ended up doing to make it install.

1. nuget houses the latest version of Store Engagement here
2. Use an archive manager to extract the relevant .appx packages. You'll need x86 and x64.
   • \SDK\Windows%20Kits\10\ExtensionSDKs\Microsoft.Services.Store.Engagement\10.0\Appx\
3. Download the UI Xaml
4. Install them all.

add-appxpackage -path "C:\Microsoft.Services.Store.Engagement.x64.10.0.appx" -DeferRegistrationWhenPackagesAreInUse
add-appxpackage -path "C:\Microsoft.Services.Store.Engagement.x86.10.0.appx" -DeferRegistrationWhenPackagesAreInUse
add-appxpackage -path "C:\Microsoft.UI.Xaml.2.1.appx" -DeferRegistrationWhenPackagesAreInUse

4. Reboot your computer just in case an app is currently using the previous version of the Store Engagement services. The update registration will happen upon login.
5. Download the Xpo app.
6. Double click to run it. The app should install just fine.

I am leaving my original comment below.

---

I just experienced this myself. First time I have ever encountered this error. I do apologize for the long reply but I wanted to share what I have looked into with great detail.

Edition         Windows 10 Enterprise
Version         20H2
Installed on	‎10/‎25/‎2020
OS build	19042.630
Experience	Windows Feature Experience Pack 120.2212.31.0

The error the box presents in full is:

App installation failed with error message:
Windows cannot install package 36835MahdiGhiasi.Xpotify_2.1.6.0_x64__yddpmccgg2mz2 because this package depends on a framework that could not be found.
Provide the framework "Microsoft.Services.Store.Engagement" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 10.0.19011.0, along with this package to install.
The frameworks with name "Microsoft.Services.Store.Engagement" currently installed are:
Microsoft.Services.Store.Engagement_10.0.18101.0_x86__8wekyb3d8bbwe
Microsoft.Services.Store.Engagement_10.0.18101.0_x64__8wekyb3d8bbwe
Microsoft.Services.Store.Engagement_10.0.19011.0_x86__8wekyb3d8bbwe
(0x80073cf3)

As you can see, the error says the package requires Microsoft.Services.Store.Engagement_10.0.19011.0_x64 but is missing. It also claims the only package with version 10.0.19011.0 is x86. This is a newly built system with a recent install of Windows (one month). When I look at staged packages through Terminal, I get:

PS C:\Users\icedterminal> get-appxpackage -allusers *Microsoft.Services.Store.Engagement*


Name                   : Microsoft.Services.Store.Engagement
Publisher              : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture           : X86
ResourceId             :
Version                : 10.0.18101.0
PackageFullName        : Microsoft.Services.Store.Engagement_10.0.18101.0_x86__8wekyb3d8bbwe
InstallLocation        : C:\Program
                         Files\WindowsApps\Microsoft.Services.Store.Engagement_10.0.18101.0_x86__8wekyb3d8bbwe
IsFramework            : True
PackageFamilyName      : Microsoft.Services.Store.Engagement_8wekyb3d8bbwe
PublisherId            : 8wekyb3d8bbwe
PackageUserInformation : {S-1-5-18 [S-1-5-18]: Staged}
IsResourcePackage      : False
IsBundle               : False
IsDevelopmentMode      : False
NonRemovable           : False
IsPartiallyStaged      : False
SignatureKind          : Store
Status                 : Ok

Name                   : Microsoft.Services.Store.Engagement
Publisher              : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture           : X64
ResourceId             :
Version                : 10.0.18101.0
PackageFullName        : Microsoft.Services.Store.Engagement_10.0.18101.0_x64__8wekyb3d8bbwe
InstallLocation        : C:\Program
                         Files\WindowsApps\Microsoft.Services.Store.Engagement_10.0.18101.0_x64__8wekyb3d8bbwe
IsFramework            : True
PackageFamilyName      : Microsoft.Services.Store.Engagement_8wekyb3d8bbwe
PublisherId            : 8wekyb3d8bbwe
PackageUserInformation : {S-1-5-18 [S-1-5-18]: Staged}
IsResourcePackage      : False
IsBundle               : False
IsDevelopmentMode      : False
NonRemovable           : False
IsPartiallyStaged      : False
SignatureKind          : Store
Status                 : Ok

The only package version available is 10.0.18101.0 in both x86 & x64. I have no idea why an older package is being used as default and which apps call for it. I went and looked at the WindowsApps directory manually and 10.0.19011.0_x86 was no where to be found. It claiming the most recent 32 bit package was there is false. Annoyingly, these are system packages that apps rely on. The AppX deployment service bars removing them manually with the current running install. Your only option is to update them. Which itself was a minefield for me to figure out as documentation states if an app requires something, dependencies should be installed automatically (either through request are packaged with). Which I can only assume it has done in the past because I have used this app on 1909 and 2004.

If the dependency isn't bundled or fails the request to download, you can update this package manually. You can only update! You cannot have two different versions side by side. The install fails. You'll user PowerShell/Terminal as an Admin:

add-appxpackage -path "C:\Microsoft.Services.Store.Engagement.x64.10.0.appx" -DeferRegistrationWhenPackagesAreInUse
add-appxpackage -path "C:\Microsoft.Services.Store.Engagement.x86.10.0.appx" -DeferRegistrationWhenPackagesAreInUse

Now check to see if the packages are updated accordingly

PS C:\Users\icedterminal> get-appxpackage *Microsoft.Services.Store.Engagement*


Name              : Microsoft.Services.Store.Engagement
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 10.0.19011.0
PackageFullName   : Microsoft.Services.Store.Engagement_10.0.19011.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.Services.Store.Engagement_10.0.19011.0_x64__8wekyb3d8bbwe
IsFramework       : True
PackageFamilyName : Microsoft.Services.Store.Engagement_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok

Name              : Microsoft.Services.Store.Engagement
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X86
ResourceId        :
Version           : 10.0.19011.0
PackageFullName   : Microsoft.Services.Store.Engagement_10.0.19011.0_x86__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.Services.Store.Engagement_10.0.19011.0_x86__8wekyb3d8bbwe
IsFramework       : True
PackageFamilyName : Microsoft.Services.Store.Engagement_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok

After this is completed, you end up with issue #109. Back to square one. Logs give some more information but don't give a definitive resolution.

Creating Resiliency File C:\ProgramData\Microsoft\Windows\AppRepository\81f6c8fe-d9a4-4e27-9d59-5425249ebca1_S-1-5-21-2327577338-2198052142-994085587-1001_2.rslc for Add Operation on Package 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_~_yddpmccgg2mz2.

Bundle Uri https://xpomusic.com/get/appx/XpoMusic-2.1.6.0.AppxBundle contains packages:
"XpoMusic_2.1.6.0_x86.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_x86__yddpmccgg2mz2
"XpoMusic_2.1.6.0_x64.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_x64__yddpmccgg2mz2
"XpoMusic_2.1.6.0_ARM.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_arm__yddpmccgg2mz2
"XpoMusic_2.1.6.0_scale-100.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_split.scale-100_yddpmccgg2mz2
"XpoMusic_2.1.6.0_scale-125.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_split.scale-125_yddpmccgg2mz2
"XpoMusic_2.1.6.0_scale-150.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_split.scale-150_yddpmccgg2mz2
"XpoMusic_2.1.6.0_scale-400.appx": 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_split.scale-400_yddpmccgg2mz2.

Successfully added the following uri(s) to be processed: 
https://xpomusic.com/get/appx/XpoMusic-2.1.6.0.AppxBundle
https://xpomusic.com/get/appx/XpoMusic-2.1.6.0.AppxBundle\XpoMusic_2.1.6.0_x64.appx
https://xpomusic.com/get/appx/XpoMusic-2.1.6.0.AppxBundle\XpoMusic_2.1.6.0_scale-100.appx
https://xpomusic.com/get/appx/Dependencies/x86/Microsoft.UI.Xaml.2.1.appx.

AppX Deployment operation failed for package 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_~_yddpmccgg2mz2 with error 0x80073CF9. The specific error text for this failure is: Unspecified error

The error code in here in this report isn't helpful at all. Suggestions for this say use wsreset.exe or re-register all installed apps. That does nothing. And then lastly:

Deployment Add operation with target volume C: on Package 36835MahdiGhiasi.Xpotify_2.1.6.0_neutral_~_yddpmccgg2mz2 from:  (XpoMusic-2.1.6.0.AppxBundle)  failed with error 0x8000FFFF.
See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues.

I have done as much troubleshooting as a I can but can not get this app to install on any of the three machines I have at my disposal.