Xbox Integration error due to a Microsoft Change
Not sure why this is happening, it doesn’t stop LaunchBox from working but it endlessly scans for storefront libraries until I close the error screen.
Comments (104)
-
-
Issue
#8251was marked as a duplicate of this issue. -
Issue
#8245was marked as a duplicate of this issue. -
Issue
#8258was marked as a duplicate of this issue. -
Issue
#8257was marked as a duplicate of this issue. -
Issue
#8256was marked as a duplicate of this issue. -
Issue
#8255was marked as a duplicate of this issue. -
Issue
#8254was marked as a duplicate of this issue. -
Issue
#8252was marked as a duplicate of this issue. -
Issue
#8246was marked as a duplicate of this issue. -
Issue
#8244was marked as a duplicate of this issue. -
Issue
#8243was marked as a duplicate of this issue. -
Issue
#8242was marked as a duplicate of this issue. -
Issue
#8241was marked as a duplicate of this issue. -
For a temporary solution please try the following:
With LaunchBox closed:
Navigate to the folder you installed LaunchBox in.
Go to the Data folder inside of this folder
Open the Settings.xml file
Look for "EnableAutomatedImports" tag. (It should be around line 54 - may not be exact depending in your build)
If it is Set to "true" change it to “false”
Save and close the file
Reopen LaunchBox -
- changed status to open
-
- changed title to Xbox Integration error due to a Microsoft Change
-
The temporary solution works. Thanks!
-
Looks like Microsoft changed something on their end, which breaks our integration piece for Xbox games. We’ll look into it and hopefully solve it for the next beta. A temporary solution could be to go into the Manage Storefronts window and change the Xbox dropdown to None.
-
Issue
#8262was marked as a duplicate of this issue. -
Issue
#8261was marked as a duplicate of this issue. -
Issue
#8260was marked as a duplicate of this issue. -
Issue
#8259was marked as a duplicate of this issue. -
Issue
#8264was marked as a duplicate of this issue. -
Issue
#8263was marked as a duplicate of this issue. -
Issue
#8266was marked as a duplicate of this issue. -
Issue
#8265was marked as a duplicate of this issue. -
Issue
#8269was marked as a duplicate of this issue. -
Issue
#8267was marked as a duplicate of this issue. -
Issue
#8272was marked as a duplicate of this issue. -
Issue
#8271was marked as a duplicate of this issue. -
Issue
#8270was marked as a duplicate of this issue. -
I didn’t realize there was already an issue,
#8273is also a duplicate but I can’t close it on my side. -
Issue
#8273was marked as a duplicate of this issue. -
Issue
#8278was marked as a duplicate of this issue. -
Issue
#8277was marked as a duplicate of this issue. -
Issue
#8276was marked as a duplicate of this issue. -
Issue
#8275was marked as a duplicate of this issue. -
Issue
#8283was marked as a duplicate of this issue. -
Issue
#8282was marked as a duplicate of this issue. -
Issue
#8280was marked as a duplicate of this issue. -
Issue
#8290was marked as a duplicate of this issue. -
Issue
#8289was marked as a duplicate of this issue. -
Issue
#8288was marked as a duplicate of this issue. -
Issue
#8287was marked as a duplicate of this issue. -
Issue
#8286was marked as a duplicate of this issue. -
Issue
#8285was marked as a duplicate of this issue. -
This fix worked for me, no need to disable auto imports completely:
Looks like Microsoft changed something on their end, which breaks our integration piece for Xbox games. We’ll look into it and hopefully solve it for the next beta. A temporary solution could be to go into the Manage Storefronts window and change the Xbox dropdown to None.
-
Issue
#8293was marked as a duplicate of this issue. -
Issue
#8291was marked as a duplicate of this issue. -
Issue
#8294was marked as a duplicate of this issue. -
Issue
#8295was marked as a duplicate of this issue. -
Issue
#8297was marked as a duplicate of this issue. -
Issue
#8296was marked as a duplicate of this issue. -
Issue
#8298was marked as a duplicate of this issue. -
I got the same error
-
Issue
#8303was marked as a duplicate of this issue. -
Issue
#8302was marked as a duplicate of this issue. -
Issue
#8301was marked as a duplicate of this issue. -
Issue
#8300was marked as a duplicate of this issue. -
Issue
#8304was marked as a duplicate of this issue. -
Issue
#8305was marked as a duplicate of this issue. -
Issue
#8307was marked as a duplicate of this issue. -
Issue
#8306was marked as a duplicate of this issue. -
Issue
#8308was marked as a duplicate of this issue. -
Issue
#8309was marked as a duplicate of this issue. -
For anyone experiencing this issue, this has been solved as of 13.9 beta 3, which can be downloaded by upgrading to beta builds. We are currently targeting the official release of 13.9 sometime next week.
-
Issue
#8311was marked as a duplicate of this issue. -
Issue
#8312was marked as a duplicate of this issue. -
Issue
#8316was marked as a duplicate of this issue. -
Issue
#8314was marked as a duplicate of this issue. -
Issue
#8313was marked as a duplicate of this issue. -
- changed status to resolved
Corrected in 13.9 beta 3
-
Issue
#8320was marked as a duplicate of this issue. -
Issue
#8319was marked as a duplicate of this issue. -
Issue
#8318was marked as a duplicate of this issue. -
Issue
#8317was marked as a duplicate of this issue. -
Issue
#8324was marked as a duplicate of this issue. -
Issue
#8323was marked as a duplicate of this issue. -
Issue
#8322was marked as a duplicate of this issue. -
Issue
#8326was marked as a duplicate of this issue. -
Issue
#8330was marked as a duplicate of this issue. -
Issue
#8335was marked as a duplicate of this issue. -
Issue
#8343was marked as a duplicate of this issue. -
hey brian can you check GoG as well? when I enter my profile name it errors, I did the fix of xbox games to make sure it wasnt the Xbox games do in it, when turning off the xbox games, and steam show all it was fine until I did GOG
Object reference not set to an instance of an object. App: LaunchBox Version: 13.8 Theme: Default Type: System.NullReferenceException Site: System.Collections.Generic.Dictionary`2[System.String,Unbroken.LaunchBox.Windows.Processes.AutoImportGame] ScanForGames(Boolean ByRef) Source: LaunchBox at Unbroken.LaunchBox.Windows.Desktop.Processes.Scanning.ScanForGames(Boolean& hasExpiredCredentials) at PolicyResolver.CalculateFailureDescriptor(Boolean& hasExpiredCredentials, PolicyResolver ) at Unbroken.Queues.RefFacadeQueue.GetDistributedModel() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.UpdateAbstractBridge(Object ) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CalculateLiteralAdapter() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() Recent Log: 6:00:32 PM Exception
-
-
Issue
#8347was marked as a duplicate of this issue. -
Hi dan, The error still indicates you are on 13.8. Update to the latest beta and let us know if you are still experience this error.
-
FYI, the suggested fix at the top didn’t work for me. The other fix suggested halfway down this page didn’t work either. When will the beta be distributed
-
hey brian yes I am still getting the error on 13.9-beta-5
Object reference not set to an instance of an object. App: LaunchBox Version: 13.9-beta-5 Theme: Default Type: System.NullReferenceException Site: System.Collections.Generic.Dictionary`2[System.String,Unbroken.LaunchBox.Windows.Processes.AutoImportGame] ScanForGames(Boolean ByRef) Source: LaunchBox at Unbroken.LaunchBox.Windows.Desktop.Processes.Scanning.ScanForGames(Boolean& hasExpiredCredentials) at ParamsValue.GetInterfaceInterpreter(Boolean& hasExpiredCredentials, ParamsValue ) at Unbroken.Mappers.ComposerDecoratorMapper.SelectInvalidEvent() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.PopAbstractTests(Object ) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.InstantiateAdvisableCode() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() Recent Log: 9:37:08 PM Exception
-
@Ben Baldwin The beta was released on 12/5. You need to be sure in your Updates setting in LB you have opted in for betas to get it.
-
Issue
#8349was marked as a duplicate of this issue. -
Issue
#8350was marked as a duplicate of this issue. -
Issue
#8351was marked as a duplicate of this issue. -
Issue
#8353was marked as a duplicate of this issue. -
Issue
#8354was marked as a duplicate of this issue. -
Just FYI the following fix doesn’t solve the problem (the flag is already set to false): “Look for "EnableAutomatedImports" tag. (It should be around line 54 - may not be exact depending in your build)
If it is Set to "true" change it to false” -
Updating from LaunchBox 13.8 to 13.9 today fixed the problem. Thank you!! You guys rock.
-
Issue
#8363was marked as a duplicate of this issue. -
Issue
#8361was marked as a duplicate of this issue. -
Issue
#8391was marked as a duplicate of this issue. -
Issue
#8399was marked as a duplicate of this issue. -
Issue
#8400was marked as a duplicate of this issue. -
Issue
#8471was marked as a duplicate of this issue. - Log in to comment
Issue
was marked as a duplicate of this issue.#8248
EDIT: LB version 13.9 corrects this issue.
A new beta should be dropping soon with a fix. In the mean time users can do the following as a workaround:
With LaunchBox closed:
Navigate to the folder you installed LaunchBox in.
Go to the Data folder inside of this folder
Open the Settings.xml file
Look for "EnableAutomatedImports" tag. (It should be around line 54 - may not be exact depending in your build)
If it is Set to "true" change it to false
Save and close the file
Reopen LaunchBox