Details
-
Bug
-
Resolution: Invalid
-
Not Evaluated
-
None
-
5.9.0 Beta 3
-
None
-
UWP 32bit Qt5.9 beta3 + VS Update 3
-
WinRT
Description
This happens with UWP 32bit Qt5.9 beta3 and WinRT 64bit Qt5.8 on top of which I installed the latest branch of Qt Purchasing. I haven't tried UWP armv7 Qt5.9 yet. It happens on UWP armv7 Qt5.9 too.
Building and running the app through Qt Creator works.
Building and running the app through VS works.
But after I associate the app with the store and I get a Package.StoreAssociation.xml, the app crashes at start. In VS debug mode (UWP 32bit) I get:
'BubbleBusterQuest.exe' (Win32): Loaded 'C:\Windows\SysWOW64\webservices.dll'. Symbols loaded. info:LoadListingInformationAsync() invoked. [Windows::ApplicationModel::Store::CurrentAppFactory::LoadListingInformationAsync] Exception thrown at 0x74F0B782 in BubbleBusterQuest.exe: Microsoft C++ exception: CacheOverflowException at memory location 0x052B92B0. Exception thrown at 0x74F0B782 in BubbleBusterQuest.exe: Microsoft C++ exception: CacheOverflowException at memory location 0x052B92B0. ASSERT failure in long __thiscall QWinRTInAppPurchaseBackendPrivate::onListingInformation(struct ABI::Windows::Foundation::IAsyncOperation<class ABI::Windows::ApplicationModel::Store::ListingInformation *> *,enum ABI::Windows::Foundation::AsyncStatus): "Not found (404).", file inapppurchase\winrt\qwinrtinapppurchasebackend.cpp, line 734 Debug Error! Program: ...rQuest-Qt_5_9_0_for_UWP_32bit-Release\debug\AppX\Qt5Cored.dll Module: 5.9.0 File: global\qglobal.cpp Line: 3052 ASSERT failure in long __thiscall QWinRTInAppPurchaseBackendPrivate::onListingInformation(struct ABI::Windows::Foundation::IAsyncOperation<class ABI::Windows::ApplicationModel::Store::ListingInformation *> *,enum ABI::Windows::Foundation::AsyncStatus): "Not found (404).", file inapppurchase\winrt\qwinrtinapppurchasebackend.cpp, line 734 (Press Retry to debug the application) BubbleBusterQuest.exe has triggered a breakpoint.
~~~
I have used the exact set-up in 3 other apps and they are currently in the store working flawlessly ( UWP 32 bit and WinRT 64bit builds ). I don't know why this isn't working for this particular app. Maybe communication with the MS server failed and maybe this issue is 1 in a 100... These issues happen on apps that failed QA at least once. Probably Microsoft is turning on the in-app products while they QA an app, and if QA fails, they turn it off by deleting the in-app products from the servers, hence the 404 error.