Backpack error after changing interface to neo

when i open the backpack i get a small box in the left top corner!! like in picture!

what about empty the backpack, then add blocks to backpack again?

Nope its not empty i have 34 blocks sets in there the red circle it to show the size of the window of the backpack... it wont open bigger nor can i selec anything from in it...

Ive been stuck like this for 4 days nows this is crazy that i cant reset the layout of backpack to original placement on the page.. its stuck in the a small box in left top corner..

The only workaround we know of is to do as @Kevinkun suggests, empty the backpack, then reload AI2. You will lose the blocks in your backpack unless you are able to "Paste All Blocks From Backpack" (right click on white space in Blocks Editor). Alternatively, await a fix from MIT, which could be some time.

1 Like

thats what i just did and its ok now i copied all from it and placed them on a empty app screen then re palced them into the empty backpack Worked! thxs both of you

IT keeps coming back!! the bug reapears every 2 times i reopen the website MIT... something is wrong here!! i cant be always be empty and refill every 2 times i work

Now i just tried from another computer and same thing happens so its not my side the problem its on ur sied of the server!!

Well, we know that (but it manifests itself client side).

However, the issue does not usually recur.

What browser are you using, are you signing out of / into AI2 each time ? Is your companion app up to date ?

Instead of relying on the BackPack so heavily, download the required blocks onto your hard drive as .PNG files, using the builtin Blocks Editor facility.

Name them appropriately, to make locating them easier when you want to drag them into a new app's Blocks Workspace.

This isn't a neo issue but a decoding issue with the backpack. My guess is that you are placing extension blocks into the backpack, and on a separate project without the extension it fails to load correctly. This was introduced when we updated the blocks editor in January, and we had patched it previously. I can run some tests to see if it's regressed again.