You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, the deck doesn’t have an Id parameter. I thought the server would always assign one, but maybe something went wrong somewhere? The problem is that without an Id, the game crashes upon start, as it’s used to retrieve the deck and in general setup the basic info for the game to start. Do you know of any reason why the server would return a deck without Id ?
Also, in the logs provided, the user initally correctly retrieves decks with Ids. It’s only at the second login, that he gets a deck without Ids.
The text was updated successfully, but these errors were encountered:
From Christian
Sometimes the backend reports decks without Ids for the player.
For example, this is what one of the QA guys got:
{ “decks”: [ { “name”: “Default”, “heroId”: “4”, “cards”: [ { “cardName”: “Pyromaz”, “amount”: “4" }, { “cardName”: “Burrrnn”, “amount”: “2" }, { “cardName”: “Izze”, “amount”: “4" }, { “cardName”: “Zhatterer”, “amount”: “4" }, { “cardName”: “Rockky”, “amount”: “4" }, { “cardName”: “Blocker”, “amount”: “4" }, { “cardName”: “Cerberus”, “amount”: “1" }, { “cardName”: “Gargantua”, “amount”: “1" }, { “cardName”: “Zhampion”, “amount”: “2" }, { “cardName”: “Fire-Maw”, “amount”: “1" }, { “cardName”: “Modo”, “amount”: “1" }, { “cardName”: “Werezomb”, “amount”: “2" } ] } ] }
As you can see, the deck doesn’t have an Id parameter. I thought the server would always assign one, but maybe something went wrong somewhere? The problem is that without an Id, the game crashes upon start, as it’s used to retrieve the deck and in general setup the basic info for the game to start. Do you know of any reason why the server would return a deck without Id ?
Also, in the logs provided, the user initally correctly retrieves decks with Ids. It’s only at the second login, that he gets a deck without Ids.
The text was updated successfully, but these errors were encountered: