errors

We're not entirely sure what's going on here, but we've just had a flood of e-mails from users who are reporting that our app is crashing when they try to use it. Coincidently they all appear to be AT&T variants of Windows Phone. We're currently testing the app to establish exactly what's happened but first tests seem to show that when loading over the AT&T mobile network, the app fails, Wi-Fi connections and other networks appear to be unaffected.

More →
2
loading...
0
loading...
0
loading...
0
loading...

One story that has gone mostly unmentioned, due to the non-drama, is how smoothly the NoDo updates have been going for thousands now--meaning we're not having the botched updates we saw with the February/pre-NoDo update.

Still, on the rare occasion there are still a few errors happening (though we haven't heard anyone complain yet to us). Specifically there are two errors that seem to affect a small amount of users that have the following codes:

  • 800705B4: The timer ran out on what we were trying to do.
  • 80180080: We couldn't update your phone because your operating system might be corrupt.

For those, Microsoft has released a special tool, preventing users from fiddling with their hard disk space and/or hard-resetting their phone. If you do have the above mentioned errors, head to Microsoft support to grab the special tool and get 'er fixed already.

Source: Microsoft Support; Thanks, Kevin W, for the heads up

More →
0
loading...
0
loading...
0
loading...
0
loading...