I get an error when updating UWP APP using TrySilentDownloadAndInstallStorePackageUpdatesAsync: The specified account does not exist
I try to upgrade according to the sample code here, while using StoreQueueItem.StatusChanged to obtain progress information, sometimes I get this status information (using personal hotspots will be more prone to this phenomenon):
{
"ExtendedError":null,
"PackageInstallExtendedState":14,
"PackageInstallState":4,
"UpdateStatus":{
"PackageFamilyName":"AppName",
"PackageDownloadSizeInBytes":2260223,
"PackageBytesDownloaded":2260223,
"PackageDownloadProgress":0.95,
"TotalDownloadProgress":0.95,
"PackageUpdateState":3
}
}
It looks like Paused, but why Paused? Do I need to call TrySilentDownloadAndInstallStorePackageUpdatesAsync again to install?
At the same time I see some error logs in the event viewer (Applications and Services->Microsoft-?Windows->Store->Operational):
- Source: Store-SDK, Event ID: 2004, Task Category: In-App Purchase, Detail: SendStoreRequestWithUris( nullptr,UriHelperV7::InternalStoreEndpointExtensionUrls, UriHelperV7::InternalStoreEndpointExtensionUrlsIds::GetUserCollectionForProducts, cv, jsonCollectionsParameters.Get(), nullptr, collectionsJsonString.GetAddressOf()) Error:
The specified account does not exist
. Function: Windows::Services::Store::Internal::StoreContextServer::GetProductsByKinds Source: \storecontextserver.cpp (4460)
- Source: Store-SDK, Event ID: 2004, Task Category: In-App Purchase, Detail: ChkHr(hrGoldenTicket) Error:
The specified account does not exist
. Function: Windows::Services::Store::Internal::StoreContextServer::SendStoreRequestWithUris Source: \storecontextserver.cpp (4065)
- Source: Install-Service, Event ID: 2008, Task Category: Service, Detail: [Error] ResumeWithFlagsQueueItemId = {9369AD17-2AA2-42A8-8F76-335AFAB88741} Error: The operation completed successfully. Function: InstallQueue2::ResumeWithFlags Source: onecoreuap\enduser\winstore\installservice\libqueue2\installqueue2.cpp (432)
How should I solve this problem?
The problem has been solved. The root cause is that I used test flight. The official version does not have this problem. This problem only appears in the test flight version.