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
{{ message }}
This repository has been archived by the owner on Oct 27, 2020. It is now read-only.
Yesterday at a meet I learned of a serious Blockly bug that is impacting young teams. Although I haven't experience it myself, the impact of this is serious enough that I think it needs addressed ASAP.
Apparent Sequence of Events:
Team writes code
Someone opens up Blockly on a Mac/iOS device, makes a change, saves it
Code runs fine on the robot
Coder reopens Blockly. All programs are gone.
According to a description/workaround on Reddit, the issue involves spaces being replaced by " " at some point in that cycle. I know Safari isn't recommended, but solving this sounds pretty simple and the consequences of doing something that appears to work are severe. With some effort is is possible to recover the programs, but novice teams are more likely to just start over and/or just get discouraged.
The text was updated successfully, but these errors were encountered:
Spaces in identifier names within the downloaded file were replaced with their equivalents. No other spaces were affected. The problem occured while saving from an iPad. The .xml importer could not interpret the file after this. No error was thrown.
I am attaching an example of the corrupt file. To be clear, only the affected file cannot be opened.
Yesterday at a meet I learned of a serious Blockly bug that is impacting young teams. Although I haven't experience it myself, the impact of this is serious enough that I think it needs addressed ASAP.
Apparent Sequence of Events:
According to a description/workaround on Reddit, the issue involves spaces being replaced by " " at some point in that cycle. I know Safari isn't recommended, but solving this sounds pretty simple and the consequences of doing something that appears to work are severe. With some effort is is possible to recover the programs, but novice teams are more likely to just start over and/or just get discouraged.
The text was updated successfully, but these errors were encountered: