Skip to main content

Critical Japanese Character Corruption (Mojibake) on Windows 11 (24H2) - v1.21.93

Comments

6 comments

  • Danny Support Agent
    Beacon of Knowledge Bug Zapper Support

    Hey there!

    Sorry for the delay on this, let me check with the team and I will let you know if I hear anything on it!

    0
  • Danny Support Agent
    Beacon of Knowledge Bug Zapper Support

    We were wondering, does the error still occur if you update from 1.21.93 to current retail (1.21.132)?

    We were not able to reproduce this error on our end. 

    0
  • Rei Matsuoka

    I would like to request a verification of an issue occurring in the classroom. However, I am currently unable to do so because version v.1.21.132 has a critical bug that prevents proper operation.

    Could you please address the bugs in v.1.21.132? If that is not immediately possible, I would appreciate it if you could provide a stable alternative version. I need to confirm that no text garbling (mojibake) occurs, so a version that is both stable and free of encoding issues is necessary.

    0
  • Danny Support Agent
    Beacon of Knowledge Bug Zapper Support

    Hey there!

    What critical bug are you referring to that you believe v1.21.132 has?

    0
  • Rei Matsuoka

    The critical bug I’m referring to is the Code Builder Navigation Issue (documented in my previous report: [Urgent Bug Report] Code Builder Navigation Issue in v1.21.132).

    Currently, this navigation failure is acting as a total blocker. Because the UI/navigation within the Code Builder is broken, I’m unable to perform the necessary steps to reproduce or troubleshoot other secondary bugs in this version. Essentially, we can't fix 'B' until the navigation in 'A' allows us to reach it.

    I’ve prioritized that navigation report because, until it’s resolved, further testing and implementation in v1.21.132 are effectively at a standstill.

    0
  • Kaleb Support Agent
    Bug Zapper Support Beacon of Knowledge

    Hey Rei, 
    Thanks for the confirmation, and confirming that this issue exist in 1.21.132. 
    I've updated the team, and hopefully we can look into this deeper. Thank you for your report! 

    0

Please sign in to leave a comment.