microsoft / microsoft/pxt-arcade
404 For Current Project - Work Lost
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 546
- Forks
- 263
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 46
Description
Describe the bug
Working on a project I then attempted to push it to the github repo by pushing the github button at the bottom of the screen (luckily I've only lost 30 minutes worth of work, but still demoralizing).
To Reproduce
Steps to reproduce the behavior:
- Spend time making a game in the web editor
- Attempt to push to github
- Notice that the screen goes white, 404 errors on your CDN version of the app
- Cry a little bit
Expected behavior
The game should continue to work and load from the CDN as much as it did earlier today.
Screenshots
https://github.com/user-attachments/assets/ce495c50-7250-4166-bca7-d62ba7069b11
Desktop (please complete the following information):
- OS: Mac
- Browser Chrome
- Version 149.0.7827.114
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
Incognito has the same error, other games load fine.
CURL that's returning the 404:
curl 'https://cdn.makecode.com/api/gh/kikketer/battleturf?cdn=20260712' \
-H 'sec-ch-ua-platform: "macOS"' \
-H 'Referer: https://arcade.makecode.com/' \
-H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/149.0.0.0 Safari/537.36' \
-H 'sec-ch-ua: "Google Chrome";v="149", "Chromium";v="149", "Not)A;Brand";v="24"' \
-H 'DNT: 1' \
-H 'sec-ch-ua-mobile: ?0'
I have noticed that there's no CDN call like this for the working games, not sure why this one has this whole CDN call.
Visual Studio Code + Git is great for a backup but the asset management can be a little flakey in that scenario, that's why I flip between the two (MakeCode web for assets, VS for code and testing)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in the MakeCode web editor: use the GitHub button, then compare the failing CDN request for the project with requests for working games. Investigate the CDN/API path shown in the issue and verify that pushing a project no longer leads to a white screen or 404, while the game continues to load.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- infrastructure, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100