Epic games
I was trying to import Overcooked 2 from Epic. I logged into my account and then Launchbox freaked out and gave me a big error message that said this.
The given key 'code' was not present in the dictionary.
App: LaunchBox
Version: 11.17
Type: System.Collections.Generic.KeyNotFoundException
Site: Void ThrowKeyNotFoundExceptionT
Source: System.Private.CoreLib
at Unbroken.LaunchBox.Windows.Integrations.EpicGames.EpicAccount.GetExchangeToken(Object sid)
at SetterClient.DestroyDrivenIndexer(String res, SetterClient )
at Unbroken.LaunchBox.Windows.Integrations.EpicGames.EpicAccount.Login()
at Unbroken.LaunchBox.Windows.Desktop.ViewModels.EpicGamesImportParseViewModel.RunPreparedProccesor()
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.LogoutInterfaceAuthentication()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ThreadHelper.ThreadStart()
Recent Log:
12:34:10 PM Exception
Comments (47)
-
-
Issue
#6296was marked as a duplicate of this issue. -
Issue
#6298was marked as a duplicate of this issue. -
Issue
#6301was marked as a duplicate of this issue. -
Issue
#6302was marked as a duplicate of this issue. -
Issue
#6306was marked as a duplicate of this issue. -
Epic Games added requirements to their API that weren’t previously there. We have code change in place and should be out in beta release soon.
-
- changed status to resolved
Correction will be in next beta release.
-
Issue
#6307was marked as a duplicate of this issue. -
Issue
#6312was marked as a duplicate of this issue. -
This correction made it into the 11.18 beta 3 release
-
Issue
#6316was marked as a duplicate of this issue. -
Issue
#6318was marked as a duplicate of this issue. -
Issue
#6319was marked as a duplicate of this issue. -
Issue
#6323was marked as a duplicate of this issue. -
Issue
#6328was marked as a duplicate of this issue. -
Issue
#6326was marked as a duplicate of this issue. -
Issue
#6332was marked as a duplicate of this issue. -
Issue
#6331was marked as a duplicate of this issue. -
Issue
#6336was marked as a duplicate of this issue. -
Issue
#6335was marked as a duplicate of this issue. -
Issue
#6334was marked as a duplicate of this issue. -
Issue
#6337was marked as a duplicate of this issue. -
Issue
#6340was marked as a duplicate of this issue. -
Issue
#6342was marked as a duplicate of this issue. -
Issue
#6341was marked as a duplicate of this issue. -
Issue
#6345was marked as a duplicate of this issue. -
Issue
#6344was marked as a duplicate of this issue. -
Issue
#6347was marked as a duplicate of this issue. -
Issue
#6348was marked as a duplicate of this issue. -
Issue
#6349was marked as a duplicate of this issue. -
Issue
#6350was marked as a duplicate of this issue. -
repo owner Issue
#6351was marked as a duplicate of this issue. -
repo owner Issue
#6352was marked as a duplicate of this issue. -
repo owner Issue
#6353was marked as a duplicate of this issue. -
Issue
#6356was marked as a duplicate of this issue. -
Issue
#6354was marked as a duplicate of this issue. -
repo owner Issue
#6362was marked as a duplicate of this issue. -
repo owner Issue
#6361was marked as a duplicate of this issue. -
repo owner Issue
#6360was marked as a duplicate of this issue. -
repo owner Issue
#6358was marked as a duplicate of this issue. -
repo owner Issue
#6355was marked as a duplicate of this issue. -
Issue
#6365was marked as a duplicate of this issue. -
Issue
#6366was marked as a duplicate of this issue. -
Issue
#6370was marked as a duplicate of this issue. -
Issue
#6374was marked as a duplicate of this issue. -
Issue
#6379was marked as a duplicate of this issue. - Log in to comment
Thanks for letting us know. We will look to getting an update on this in the next release.