Xbox iOS app crashes on startup

Every time when I open the Xbox iOS app, it crashes. It makes the app completely unaccessable.

Please fix this major bug!

:)

 

Smartglass Won't Load IOS

Quick update:

New IOS Version (10.3) and the latest XB1 Smartglass update (released 29th March).

No change, app still crashes on startup.

 

Xbox iOS app crashes when Network Extension API enabled

If iOS device has app using Network Extension APIs enabled, Xbox app will crash immediately on launch. Unable to capture any useful information in iOS device log (only app started then terminated in a second) nor do I notice any crash log.

 

Hey Straed,

I have the same issue as you have! Could you tell us which device you are using? My App is not working for a month or longer. Since the first time the App crashed after starting we had 2 or 3 updates for the App and an IOS update but still it is not working.
I am using IPhone 6S and do always all the updates. I thought maybe it is a Problem about the IPhone 6s but a friend has the same and his xbox App works perfectly.

Sorry for my bad English

 

Hey there Straed and Florianmsn,

Can you please tell us which iPhone you're using and what version iOS you're using? Is it a beta version or standard released version?

_______________________________________________________



Xbox Forums Staff

Be sure to check out the Xbox Forum Guidelines for the Do's and Don'ts as well as the Xbox
Insider Program Forums for help with Xbox Insider Program troubleshooting. Achievement issues? Check our sticky

HERE for the best info.

 

Hey Mister Mascot,

i have the iphone 6s running IOS 10.3.1. Till today i used the standard version but from now on the Beta App. Misses Quinzel is helping me already here: iOS Smartglass will not open anymore

 

Me too here!

I use iPhone 7 Plus(iOS 10.3.1) and it worked totally fine a couple of months ago.

When I tried to run it and failed to log in(later I knew there was Xbox Live outage), never run properly again just crash and crash.

I upgraded iOS 2 times it occurred even hard reset and restore but not fixed.

It seems a known issue for MS but it's simply not fixed yet.