CODEWITHSUNDEEP
uwpwin-universal-app
Seaky
Seaky

Reputation: 249

uwp app is reported to crash on launch but runs good on my computer

I submit my app to the Microsoft Store but Microsoft Store Team reports my app to crash on launch. However, when I build my app in either Debug mode or Release mode, it runs perfectly. I just don't know how to reproduce the crash which makes me unable to figure out what's going on within my app. And Microsoft team doesn't give my any other information about the crash.

Can anyone help me figure out why my app crashes? Or can anyone give me some hints on how to fix such crash?

My app does crash sometimes but that's about the frequency of once out of at least 20 builds. I submitted my app 3 times but they reports crash every time. So I don't think the crashes might share the same reason.

This is my project link.

Since it crashes on launch, it might have something to do with the OnLaunched function here.

And these are the links to the functions that I called in OnLaunched:

Settings.Init

MusicLibrary.Init

MediaHelper.Init

Upvotes: 0

Views: 826

Answers (2)

Avnish kumar
Avnish kumar

Reputation: 78

I think, you have to first create appxupload bundle for x86 architecture only in release mode. Run & test Side-load version, Then submit to store. I also facing same issue in past due to some Nuget packages.

Upvotes: 0

Anran Zhang
Anran Zhang

Reputation: 7727

App will work fine when it's local debug, but it will crash and be returned when it's submitted to the app store.

When the Microsoft Store reviews an app, it usually tests with the app’s minimum running platform, so once your app uses an API that is not included in the minimum running platform, the app will crash immediately.

For example, if you use the property Button.CornerRadius to add rounded corners to the button, but before 1809, most of the controls did not have the property of CornerRadius. Once the application using this property runs on the Windows 10 platform below 1809, then it will crash.

So you'd better set up a virtual machine, load a system mirror of the lower system version, then package the application and put it in system for testing.

But sometimes, even if you know the cause of the problem, it is still difficult to locate the specific attribute of the control. Therefore, the quickest way is to modify the minimum runnable version of your application and modify it to the same level as your local computer system version.

But if you need to be compatible with more platforms, this requires targeted testing.

Best regards.

Upvotes: 1

Related Questions