应用程序在本地和测试版中运行，但在官方商店版本中崩溃了吗？ [英] App works locally and in Beta, but crashes for some in official Store version?

问题描述

嘿伙计们，我有一个YouTube应用程序，目前在商店（myTube）。在最近的更新后，应用程序在打开视频时就开始崩溃。它只适用于某些人。

但奇怪的是，当有问题的人加入测试版时，它适用于他们。测试版与官方版本的版本相同，代码相同，声明的功能相同。

根据DevCenter崩溃报告，我的方法中存在一个名为 的MediaElement.MediaOpened事件中的NullReferenceException。我有一段时间没有更改代码，所以我不确定为什么它会在此更新后开始发生。

通常如果应用程序崩溃，它应该让用户选择向我报告问题，但是对于这个特定问题，向我报告的选项不会来起来。此选项没有出现的唯一其他时间是存在StackOverflowException，
或OutOfMemoryException。

任何想法为什么该应用程序将在本地和测试版中工作，但不是官方商店应用程序？

编辑：当我上周一提交更新时，开发中心未能签署XAP。我重新提交了相同的XAP并签名工作。然后在更新后问题开始。开始得到糟糕的评论，这是一个糟糕的问题。

---

Ryken Productions

解决方案

beta应用程序是否有可能与发布的应用程序具有相同的ApplicationID，但您的Beta应用程序使用Isolated存储与生产应用程序略有不同？ 每个应用程序IsolatedStorage是ApplicationID的键。这是我能想到的唯一
的事情，测试版应用可能会修改并影响生产应用。

如果您更新应用并且不修改ApplicationID（即发布为一个新的应用程序），你的更新的应用程序使用IsolatedStorage结构略有不同，然后用户手机上的IsolatedStorage的现有内容可能会混淆它。另一种方法是将
存储在隔离存储的开头，因此当更新发生时，应用程序初始化时可以检查Iso存储的版本以确定其结构是否需要更新。

另见
此链接。

希望这会有所帮助，

Mark

Hey guys, I have a YouTube app that's currently out on the Store (myTube). After a recent update, the app started crashing whenever they opened a video. It only happens for some people.

The weird thing is though, that when people who had the problem join the beta, it works for them. The beta is on the same version as the official version, with identical code, and the same declared capabilities.

According to the DevCenter crash reports, there is a NullReferenceException in my method called in MediaElement.MediaOpened event. I haven't changed the code in there in a while, so I'm not sure why it started happening after this update.

Usually if the app crashes, it should give the user the choice to report the problem to me, but with this particular issue the option to report to me doesn't come up. The only other times that this option doesn't come up is when there is a StackOverflowException, or an OutOfMemoryException.

Any idea why the app would work locally and in the beta, but not as an official Store app?

EDIT: When I submitted the update last Monday, the Dev Center failed to sign the XAP. I resubmitted the same XAP and signing worked. Then after that update is when the problem started. Starting to get bad reviews, kind of a sucky issue.

---

Ryken Productions

解决方案

Hi,

Is there a possibility that the beta app has the same ApplicationID as the released one, but your beta app uses Isolated Storage slightly differently than the production app?  The per-app IsolatedStorage is keyed to the ApplicationID. That's the only thing I can think of that the beta app might modify and affect the production app.

If you update your app and do not modify the ApplicationID (i.e. publish as a new app), and your updated app uses IsolatedStorage structures slightly differently, then the existing contents of IsolatedStorage on the user phone might confuse it. One way around this is to store the app version at the beginning of isolated storage, so when an update occurs, the app upon initialization can inspect the version of Iso storage to determine if its structures need to be updated.

See also this link.

Hope this helps,
Mark

这篇关于应用程序在本地和测试版中运行，但在官方商店版本中崩溃了吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！