What really happen with Windows phone OS?

[JackyH]

Dear all,

I'm dev for WP for over one year. At the first time I really love the os but now it makes me feel so terrible. So many kinds of problems occur:
- CRASH CRASH and CRASH..... After publishing well, the updated version of some apps crashed for unknown reason. For example, some users run well but others can not open the app after updating from store. I tried to fix and ask MS supporters but still have no ideas.

- It's hard to dev an app, but harder to submit successfully cause facing many kind of issues from certification. I'm very shock for the problems that I faced: the first time I submitted RELEASE.XAP file => FAIL (testers can not open the app), I fixed everything I can to resubmit again but still fail (about 7 times). Totally, it took me about 1 month to submit but still fail and fail. FINALLY, I do nothing else but submit DEBUG.XAP again and SUCCESS => WHAT the hell are they doing with my app?

I'm so disappointed with WP and MS.

 

[Laura Knotek]

I've moved your thread to the Developers Corner forum, since your concerns would probably be addressed better by fellow developers, rather than regular users.

 

[Adarsh Urs]

Dear all,

I'm dev for WP for over one year. At the first time I really love the os but now it makes me feel so terrible. So many kinds of problems occur:
- CRASH CRASH and CRASH..... After publishing well, the updated version of some apps crashed for unknown reason. For example, some users run well but others can not open the app after updating from store. I tried to fix and ask MS supporters but still have no ideas.

I do not know you are aware of Crash reports on dev center dashboard. Dev Center dashboard -> Reports -> Crash Counts -> Export top stack traces from the last 30 days. It gives you the complete crash details of your app, like Exception type and where is crash occurring (file and function name etc). Please check that once....

- It's hard to dev an app, but harder to submit successfully cause facing many kind of issues from certification. I'm very shock for the problems that I faced: the first time I submitted RELEASE.XAP file => FAIL (testers can not open the app), I fixed everything I can to resubmit again but still fail (about 7 times). Totally, it took me about 1 month to submit but still fail and fail. FINALLY, I do nothing else but submit DEBUG.XAP again and SUCCESS => WHAT the hell are they doing with my app?

I'm so disappointed with WP and MS.

By default VS creates app's in debug mode. You have to rebuild and test the app in Release mode before submitting it to store? Did you do that?

 

[MasterKelli]

The thing is that Windows Phone 7 was more stable than Windows Phone 8. Windows Phone 7 had locked core and everything else was tightly controlled C#. It of course prevented to use some deep level APIs but overall the OS was working better. Now with Windows Phone 8 the OS seems to be much more prone to crashing and is taking more resources to run. Windows Phone 7 never had any lagging or crashing, WP8 has those regularly. Of course WP8 has much more features so in that way it is a great improvement and opening the APIs has brought lots of developers because they can now more easily port their Android and iOS games to WP8.

But still, WP8 is a great OS and it is your responsibility as a developer to build high quality apps that work on all devices.

 

[Catholic Tech Geek]

It would help if I had some debug information to work with. Adarsh Urs is right: you can get stack traces from the last 30 days from your dev center dashboard and those stack traces contain the exceptions that caused the app in question to crash. From there, you can see where in your code the crash occurred and remedy it.

 

[JackyH]

I do not know you are aware of Crash reports on dev center dashboard. Dev Center dashboard -> Reports -> Crash Counts -> Export top stack traces from the last 30 days. It gives you the complete crash details of your app, like Exception type and where is crash occurring (file and function name etc). Please check that once....



By default VS creates app's in debug mode. You have to rebuild and test the app in Release mode before submitting it to store? Did you do that?

You dont read what I said? Submit RELEASE.XAP -> FAIL, but submit DEBUG.XAP -> DONE, that happened to me.

 

[Adarsh Urs]

You dont read what I said? Submit RELEASE.XAP -> FAIL, but submit DEBUG.XAP -> DONE, that happened to me.

That's why I asked you have you build the app in release mode before submitting it. If you don't build the app in release mode release.xap remains as old, whatever the changes you made in the app won't effect release.xap. But VS by default is in debug mode, so everytime you build the app, debug.xap updated with all the changes you did in the app.

My assumption is that after you fix the bugs on your app, you might have forgot to build it in release mode. That's why release.xap got rejected ('coz it is still the old version).
But debug.xap has all the fixes, so it got through the certification process.

 

[JackyH]

That's why I asked you have you build the app in release mode before submitting it. If you don't build the app in release mode release.xap remains as old, whatever the changes you made in the app won't effect release.xap. But VS by default is in debug mode, so everytime you build the app, debug.xap updated with all the changes you did in the app.

My assumption is that after you fix the bugs on your app, you might have forgot to build it in release mode. That's why release.xap got rejected ('coz it is still the old version).
But debug.xap has all the fixes, so it got through the certification process.

I did, built and checked carefully in two mode. But only success with file xap built in Debug when submit to Store. That's so strange for me. I chatted with supporters 3 times without any solutions.

 

[Catholic Tech Geek]

Ok, the first thing you can try is (while on Release configuration) clean the solution and rebuild the solution. If that doesn't do it, delete the bin and obj folders inside each project folder in the solution (while Visual Studio is not running) and then reopen the solution and build the solution. That should do it.

 

[Adarsh Urs]

I did, built and checked carefully in two mode. But only success with file xap built in Debug when submit to Store. That's so strange for me. I chatted with supporters 3 times without any solutions.

You should have Googled for the solution instead of contacting support.
If you did, have you found any one facing/faced the issue?

As catholic said delete the bin folder and build the protect in release mode, it may work. If not re-install WP SDK or entire VS. Because it's a strange issue , I never see any one come across this problem....

 

[JackyH]

Thank you all for your suggestion, It took me nearly 1 month for solving the problem, I'll try and share if I find good solution.

 

[anon(5604227)]

You can use external bug-tracking system like BugSense. For applications with little users is free.

With one service like that you can track all your crashes, instrument them (send extra data when the program crashes) to solve them better.

In my experience, WP has some annoying random crashes, more if you use async/await, but except very little situations, problem is in your code. You can do a wrong thing in one place that will end with a crash in the other side of your code.

The only thing I recomend is a good bug tracking system and patience, a lot of patience. ;-)


Sent from my Surface Pro 3 using Tapatalk

 

[xkinn]

Dear all,

I'm dev for WP for over one year. At the first time I really love the os but now it makes me feel so terrible. So many kinds of problems occur:
- CRASH CRASH and CRASH..... After publishing well, the updated version of some apps crashed for unknown reason. For example, some users run well but others can not open the app after updating from store. I tried to fix and ask MS supporters but still have no ideas.

- It's hard to dev an app, but harder to submit successfully cause facing many kind of issues from certification. I'm very shock for the problems that I faced: the first time I submitted RELEASE.XAP file => FAIL (testers can not open the app), I fixed everything I can to resubmit again but still fail (about 7 times). Totally, it took me about 1 month to submit but still fail and fail. FINALLY, I do nothing else but submit DEBUG.XAP again and SUCCESS => WHAT the hell are they doing with my app?

I'm so disappointed with WP and MS.

There's a reason windowscentral have Beta Tester's Subforum, right?