(August 13, 2019)
Hello everyone!
We are now 8 months out from the launch of Scratch 3.0. As you may have noticed, the Scratch Team has not been super active on this thread (which was created in January 2019) and most of the bugs on this list are pretty much resolved.
That said, we are now going to close this thread. If you still have a bug or problem, please keep using the Bugs & Glitches Forum and we will try our best to look at your issues.
Thank you so much for your helpful feedback, thoughtful critique, and enthusiasm
Scratch on!
<3 pondermake on behalf of the Scratch Team
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Known Bugs & Glitches
Thanks to everyone who has been giving constructive feedback on 3.0! It would help us a lot if you could check this list of known bugs before starting a new thread
Chances are, it has been mentioned by someone in the forums and we are working hard on it!If you have more information about a specific bug or glitch below, you are welcome to make a note in this thread.
Please give as much detail as you can, for example:
- What were you doing when the bug appeared?
- What is the project URL of the buggy project?
- What OS and browser were you using?
This list is a work-in-progress and will grow as we discover new bugs from the community. Will also update when things get fixed!
—————————
Links to other bug threads:
Posted 1/09/2019 by @ceebee: Updates and Bug Fixes
Also, thanks to @banana439monkey for putting the following guides together.
PLEASE READ BEFORE MAKING A TOPIC: A guide to reporting glitches V2
PLEASE READ BEFORE MAKING A TOPIC - MySQL Bugs - The directory of bugs
—————————
If any of these issue is affecting one of your projects, it would greatly help us if you shared:
- The project URL
- What browser and operating system you are using (e.g. Chrome on Mac)
I can’t add new assets to my backpack.
as of 1/04/19Scratchers are not able to load things out of their backpack more than once, or not at all. Some Scratchers are reporting “Error Loading Backpack.”
This issue is one of our critical issues to fix. It is logged, and we are working hard on it!
- https://scratch.mit.edu/discuss/topic/327570/
- https://scratch.mit.edu/discuss/topic/329365/
- https://scratch.mit.edu/discuss/topic/329332/?page=1#post-3378495
I can’t load projects on the project page.
as of 1/08/19
When viewing projects on the project page, the stage appears as a blue error screen.
This has been logged and we are paying attention to the problem.
Many of these issues we were able to connect to various Chrome extensions that would block the project page and editor from loading. We’ve made some changes that have greatly reduced the number of these errors.
Some of these errors are due to incompatible browsers. If you are using anything below these version numbers, we recommend you update or try a different browser:
- Chrome (63+)
- Mobile Chrome (62+)
- Edge (15+)
- Firefox (57+)
- Safari (11+)
- Mobile Safari (11+)
Cloud variables are getting changed or reset.
as of 1/28/19Scratchers are reporting that other people are able to change their cloud variables, or that cloud variables are broken. We don't yet know why this is but if this is affecting you, you can help share the following:
- Your project ID's
- When did this first happen?
- How often/how quickly did this happen? (example: I noticed the cloud var was reset an hour after I shared.)
Project thumbnail is wrong.
Some Scratchers are seeing the default Scratch Cat thumbnail invading their project thumbnails. Their project should instead be showing an accurate thumbnail of the actual project sprites. If this is affecting you, can you please share the project ID?
I’m not able to save my project.
as of 1/08/19Many people have reported problems saving in the editor. If you are having trouble saving right now, it’s possible that our servers are down temporarily. It might also be because you recently uploaded or edited audio files. Sorry that you are having trouble! We are doing our best to address this urgent issue quickly.
What should I do for now?
What you can do to not lose your work is to click “File > Save to your computer” in the editor. Make sure you keep track of where it saves to on your computer.
When you are ready to keep working on it, you can upload it using “File > Load from your computer.” Hope that helps!
I’m having trouble with recorded/uploaded sounds.
as of 1/09/19Recorded, uploaded, and edited audio files are causing a number of problems, including:
- preventing Scratch from saving
- crashing the editor
- producing glitchy or garbled sound
- not uploading properly into or out of backpack
- being unresponsive or freezing Scratch when you try to trim sounds
These issues seem related to the audio file being too big. We've noticed these problems in the web editor and also in the Desktop editor. We are hoping to fix this soon!
The editor freezes or lags randomly.
as of 1/08/19Some Scratchers have reported intermittent freezing in the editor. This is most likely happening when the project periodically auto-saves. We're aware of this and hope to work on a fix soon!
Using the Bitmap Color Picker crashes Scratch.
Added 1/09/2019. We don't yet have a fix for this.
The eraser is not working correctly.
Added 1/09/2019. When erasing, the erased area has a fill or outline. We don't yet have a fix for this.
—————————
Here are some of the top requested features that were in 2.0, and are no longer in 3.0. Because they're not bugs, we probably won't fix them immediately, but rest assured we are thinking about them and plan to address them in the future
It's difficult to center sprites without the 2.0 crosshair tool.
We hear you on this. This is a very popular ask as well! We're invested in trying to make centering things easier in the future, though we might not get to it right away.
—————————
(fixed 1/03/2019!)
The Notes & Credits and Instructions sections take up space even if they are empty.
Before, when projects had either blank Instructions or blank Notes & Credits, the empty section would collapse so you could read the other section more easily. This bug was fixed on 1/03/2019.
(fixed 1/07/2019!)
Loves or favorites aren't showing up in Messages or “What I've Been Doing.”
This is a bug, not something we changed intentionally. We’re aware of this issue and we are working on it!
(fixed 1/04/19)
Project sprites are loading blurry in the stage.
Images look low quality, blurry, foggy, or pixelated. Some people are noticing this particular when they full screen the stage, or they are noticing it on specific computers. People have also noted that this is affecting vector (svg) assets more.
We have made fixes to this, but if you see any other weirdness, please note it here and share what browser you are using. Thanks!
(fixed 1/31/19!! So exciting!)
Lists and variable monitors are covering the nav bar.
When on the project page, some people are seeing monitors on top of the
nav, making it impossible/inconvenient to click on nav links.
(fixed sometime in February!)
I can't export costumes/sounds from the editor.
There's a lot of demand for this 2.0 feature.
(added back around 2/14/19!)
I can't upload gifs as sprites.
In 2.0, you were able to upload gifs to use as sprites. We intend to have this back in the future, we just weren't able to have it for 3.0! Stay tuned.
(fixed sometime in Mar/April)
I could change the slider min/max in 2.0, but I can't in 3.0.
Right now the slider min/max values default to 0 and 100. Ideally, you should be able to change these values. We intend to fix this soon, stay tuned!
(fixed in April)
Loading a Scratch project file creates a new Scratch project.
This is especially troublesome when Scratchers want to work on a “backup” of a project which is already loved/favorited/viewed. We're not sure when we can fix this but it's definitely important to us. In the meantime, you can use the backpack to move assets back and forth. It's not ideal, we know! It might be the best work-around for the time being.
(fixed)
I can’t see my blocks, even though they are running.
as of 1/28/19Some Scratchers have reported that block stacks are missing or invisible, even though the code appears to be run correctly in the project.
This is one of our top priorities. We are investigating this right now!
Otherwise, if they are older assets but were moved to 3.0 backpack, then it is probably the common issue we've heard with 3.0 backpack. Sorry for any inconvenience, either way!
