Skip to content

Thygrrr#26219

My feedback

3 results found

  1. unable to submit deck friendly play

    1,229 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Thygrrr#26219 commented  · 

    After consistent trouble (see log file earlier this week), my gf suggested I whip out Wireshark because I was unable to play direct challenge and I am massively disappointed in Arena at the moment.

    Guess what - today it worked for me, but TO ADD INSULT to INSULT now it fails for my brother (it was the exact opposite just yesterday)

    I just want to play :(
    I think about asking for a refund. This is several nights of play, which I bought hundreds of euros of cards for, just gone without as much as an excuse or proper acknowledgement.

    Nobody reaching out to ask for logs.
    Nobody reaching out to ask for a reproduction.
    Nobody acknowledging recepit or logs.
    Nobody asking questions about logs and patterns.

    Just a shrug in the patch notes.

    It's as if your QA team does not care.

    An error occurred while saving the comment
    Thygrrr#26219 commented  · 

    When the error occurs, even after a restart of the client, I can often not log in or stay connected for the first relaunch.

    Only 2nd relaunch works. PLEASE FIX THIS. I want to play with my brother. Ranked and Play queue is boring.

    An error occurred while saving the comment
    Thygrrr#26219 commented  · 

    It got WORST with the recent release.
    As a test, I tried to turn of IPv6, that didn't do anything.

    Attached is a log file that shows the timeout in line 303

    [Social.Chat] Received message prefixed with challenge command sequence, ignoring.

    Timeout

    [UnityCrossThreadLogger]==> LogBusinessEvents {"id":"e7fe236e-30d2-40cf-81e4-4ba86e612a0a","request":"{\"Type\":1912,\"TransId\":\"e7fe236e-30d2-40cf-81e4-4ba86e612a0a\",\"Payload\":\"{\\\"Title\\\":\\\"Network Error\\\",\\\"CurrentSceneName\\\":\\\"Home\\\",\\\"Duration\\\":\\\"00:00:02.4489807\\\",\\\"Message\\\":\\\"Unable to submit deck. Please try again later.\\\",\\\"EventType\\\":31,\\\"EventTime\\\":\\\"2023-11-16T19:40:23.971392+01:00\\\"}\"}"}

    [Social.Chat] Message received by recipient.

    [Social.Chat] Canceled challenge to Jazzman: Canceled

    An error occurred while saving the comment
    Thygrrr#26219 commented  · 

    Among friends and other users, we have the recurring, intermittent error that we cannot play Direct Challenge matches against friends in our friend list.

    Bug Description:
    In a Direct Challenge, the "Waiting for Server" spinner upon clicking play (after deck selection) lasts longer than usual (normal is < 500 ms), usually around 3-5 seconds.
    Then a popup informs **"Network Error: Unable to submit deck. Try again later"**.

    Frequency:
    This bug occurs persistently, and has begun occurring in the last 2 weeks. At least one of (us) four players appears to be affected on any given evening, for the majority of that evening. More people seem affected, see reddit.com/r/MagicArena

    Reproduction:
    1. Challenge a friend on your friends list to a direct match, Bo3 or Bo1.
    2. The error occurs after Deck Selection. If it doesn't occur, it may be possible to play a number of games without encountering it. Once it has occurred once, it will keep occurring.

    Observations:
    The bug does NOT affect normal Play Queue and Ranked Queue.

    After closing the "Network Error: Unable to submit deck. Try again later", popup, MtG Arena is in a broken connection state afterwards, and generally requires restart to play even non-challenge games. The UI may present as if choosing another deck is possible, but it won't work. Sometimes, you get the "Reconnect" dialog for connection loss.

    Once the bug has occurred, for a reasonably long amount of time (hours, not minutes), it is impossible to play direct challenge games on the affected computer. We have, so far, not been able to successfully play a single game including an affected player on the same day.

    The next day, it may be fine. It may also have been fine earlier the same day, often up to the very moment of first failure.

    This bug can occur in 3 flavors:
    - Challenger experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
    - Challengee experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
    - BOTH experience the bug

    It appears random as to who is affected. We only tested in the afternoon and evenings CET.

    The bug has been "cycling" beetween the four of us, but sometimes two of us had it, and it also occurs between other pairs of players (see reddit).

    Logs:
    I don't have a log file at the moment (becuase the bug is not reproducible on my machine today - but on a friend's machine, it is, we literally can't play!). The logs themselves don't say much - literally just "Timeout" after the Social Component mentioned the incoming challenge request.

    Stuff I can personally confirm/reproduce: This exact bug keeps recurring for at least 4 users so far, on very different systems. Likely many more are affected, just look for "unable to submit deck" on reddit.com/r/MagicArena . I can say that all our computers and major or mid-size ISPs are in Germany, and although I use 1.1.1.1 as DNS, the others use their ISP's default DNS. (We assumed this to be some sort of routing issue.)

    Workarounds do not seem to exist:
    - Router restart doesn't help.
    - Computer restart doesn't help.
    - Restarting Arena doesn't help.
    - netsh winsock reset and ipconfig /renew /all won't help.
    - selecting a different deck does not help, in fact, a deck that was perfectly fine to play may encounter the bug just as well, and then be no longer able to "Submit".
    - windows firewall reset won't help
    - superstition remedies such as resetting sleeves or avatars do not help, regardless of what people on Reddit claim. (there may have been a bug in the past that had this issue)

    An error occurred while saving the comment
    Thygrrr#26219 commented  · 

    Among friends and other users, we have the recurring, intermittent error that we cannot play Direct Challenge matches against friends in our friend list.

    Bug Description:
    The "Waiting for Server" spinner upon clicking play (after deck selection) lasts longer than usual (normal is < 500 ms), usually around 3-5 seconds.

    Then a popup informs "Network Error: Unable to submit deck. Try again later".

    Frequency:
    This bug occurs persistently, and has begun occurring in the last 2 weeks. At least one of (us) four players appears to be affected on any given evening.

    Reproduction:
    1. Challenge a friend on your friends list to a direct match, Bo3 or Bo1.
    2. The error occurs after Deck Selection. If it doesn't occur, it may be possible to play a number of games without encountering it. Once it has occurred once, it will keep occurring.

    Observations:
    The bug does NOT affect normal Play Queue and Ranked Queue.

    After closing the "Network Error: Unable to submit deck. Try again later", popup, MtG Arena is in a broken connection state afterwards, and generally requires restart to play even non-challenge games. The UI may present as if choosing another deck is possible, but it won't work. Sometimes, you get the "Reconnect" dialog for connection loss.

    Once the bug has occurred, for a reasonably long amount of time (hours, not minutes), it is impossible to play direct challenge games on the affected computer. We have, so far, not been able to successfully play a single game including an affected player on the same day.

    The next day, it may be fine. It may also have been fine earlier the same day, often up to the very moment of first failure.

    This bug can occur in 3 flavors:
    - Challenger experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
    - Challengee experiences the bug (other player will be in Waiting for Opponent screen until forced draw, cancel button does not work)
    - BOTH experience the bug

    It appears random as to who is affected. We only tested in the afternoon and evenings CET.

    The bug has been "cycling" beetween the four of us, but sometimes two of us had it, and it also occurs between other pairs of players (see reddit).

    Logs:
    I don't have a log file at the moment (becuase the bug is not reproducible on my machine today - but on a friend's machine, it is, we literally can't play!), but it doesn't say much - literally just "Timeout" after the Social Component mentioned the incoming challenge request.

    This bug keeps recurring for at least 4 users so far, on very different systems.

    All our computers and (different, major and mid-size) ISPs are in Germany, though I use 1.1.1.1 as DNS, not sure about the others but they usually use their ISP's default DNS. We assumed this to be some sort of routing issue.

    Workarounds do not seem to exist:
    - Router restart doesn't help.
    - Computer restart doesn't help.
    - Restarting Arena doesn't help.
    - netsh winsock reset and ipconfig /renew /all won't help.
    - selecting a different deck does not help, in fact, a deck that was perfectly fine to play may encounter the bug just as well, and then be no longer able to "Submit".
    - superstition remedies such as resetting sleeves or avatars do not help, regardless of what people on Reddit claim. (there may have been a bug in the past that had this issue)

    Thygrrr#26219 supported this idea  · 
  2. 1,864 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Thygrrr#26219 supported this idea  · 
  3. 542 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Thygrrr#26219 supported this idea  · 

Feedback and Knowledge Base