I am receiving this message for no apparent reason.
To explain in more details, my package contains of one UWP app and one very small Win32 app. When I submit the full package to the Microsoft Store I am getting the error above. It also appears in the package flight if I submit the full package. However if I submit just the UWP app package it passes the package flight.
So the problem appears to be caused by the Win32 app or by the package project if it is possible at all. But those have been unchanged for years and are that simple that I really cannot see any possibility for the error.
So the problem appears to be a server side bug and I have no idea what to do about it. I have been suggested to write to firstname.lastname@example.org . But they don't provide any technical answers, they have never confirmed or denied that there is a bug on the server upon my persistent questions to get that answer and now they don't even reply to emails anymore.
Aside from something we all have learned the hard way - it is better to give up on Windows developing sooner rather than later - does anyone have any suggestion?
Just a side comment, this comes at a point when Microsoft will allow any kind of unsafe apps into the Store. At the same time this same company tries to tighten the security rules for existing apps and introduces the bugs that make the app updates impossible. You have to be naturally gifted to achieve this level of incompetence, that is not for ordinary people.