This might be tied to a performance problem on the code server when trying to import projects with higher levels of complexity. The loading alert fades too quickly, leading to retries on the load or import requests .
The code server also seems to lack the patience to complete attempts at project deletion.
Just now saw this, sorry for the delay. I'll poke at it this evening or tomorrow morning. Btw. Do you want to volunteer to be moved to the new code server (code2) which uses a different backend. We are going to deprecate the existing code server.
Note: If we move you, you will login the same way you do now, you will just see "code2.appinventor.mit.edu" in the browser bar.
I've copied your account from code to code2 (snapshot around 22:15
ET). When you login now, you should see your projects on
code2. Project IDs will have changed.
You were a great test case for my account migration code, both because
of the large number of projects that you have and because of the
inconsistencies (like duplicate names).
Everything should have copied over, including projects with duplicate
names (internally, this isn't a problem because projects are
manipulated with their project ids, not their names).
If you are still logged in, you will need to logout and login again to
switch over to code2.
I didn't delete anything from code, so if the copy was bad, let me
know and I'll switch you back until I figure out what went wrong.
Our plan is to shutdown code in the January 2026 timeframe, migrating
any remaining active accounts to code2.
I found all my projects on code2, under my Google login.
Sending projects to the trash side worked, but Deleting from trash gives no feedback. The entries are still in the trash project list, but I can get a 500 error retrying the delete from trash later.
To test the speed of the code2 server, I loaded a dog of a project from
(it had a global init bush with fan-out in the dozens, causing minute-long delays on project opening on the code server.
It opened quite snappily on the code2 server.
Of course, that might just be due to pre-clutter empty database performance, or that new server smell.