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
Describe the bug
A clear and concise description of what the bug is.
When I click radio more block, there is only one block on it.
This block cannot use.
Looks like there's actually several blocks under "more" that aren't being displayed correctly. They're just all overlapped at the top of the screen, so it looks like one block. It displays correctly when used in MicroBit, so I'm wondering if it could be an issue with Arcade's handling of the "more" behavior, rather than an issue specific to the extension itself... Now trying to pin down another arcade extension that utilizes the behavior to confirm.
Good point. And you're right, seems like something is off with the extension's block authoring.
I was also able to confirm that "more" worked correctly in Arcade for a sample extension I had sitting around, so that's some additional confirmation that it's something specific to this extension. Will continue to investigate...
Duplicate Issue(s): #3901 (exact duplicate - closed as completed)
Likely Related: No other related issues found
Suggested Priority: p2
Complexity: low
Copilot Agent Ready: ✅ Yes
Recommendations for Assignee
Analysis
This is a bug in the radio extension where blocks in the "more" submenu are overlapping and appearing unusable when displayed in Arcade. Team discussion (comments from @abchatra and @thsparks) confirmed this is specific to the radio extension's block definitions rather than a general "more" menu issue in Arcade - the "more" menu works correctly for other extensions. The root cause is likely incorrect block annotation syntax in the radio TypeScript files in pxt-common-packages.
Duplicate & Related Issues
Duplicates:
Radio extension bug #3901 (exact duplicate) - Same issue reported by different user, closed as completed but issue still reproduces (as confirmed by @abchatra's comment from March 2025)
Related Issues:
No closely related issues found - other "more menu" and "blocks overlapping" issues are unrelated to this specific extension bug
Location Hints
The radio extension is defined in pxt-common-packages (not pxt-arcade itself), but should be triaged here:
../../node_modules/pxt-common-packages/libs/radio/radio.ts - Contains block definitions with //% block annotations that likely have syntax errors
/home/runner/work/pxt-arcade/pxt-arcade/libs/radio/pxt.json - Points to the pxt-common-packages implementation via additionalFilePath
The issue is in the radio extension's block annotations in pxt-common-packages, specifically in how blocks are marked as "advanced" (which puts them in the "more" submenu). Look for blocks with //% advanced=true annotation and check for missing or incorrect parameters in the block definition syntax.
Next Steps
Can assign to Copilot Coding Agent: ✅ Yes, ready as-is
Reasoning: This is a well-defined bug with clear reproduction steps, existing team analysis confirming the root cause (block definition syntax), and a known location (radio extension in pxt-common-packages). The fix involves correcting block annotations, which is a straightforward code change suitable for automation. Team confirmed this "should be easy fix" in 2022, and it's still reproducible as of March 2025.
Activity
abchatra commentedon Sep 28, 2022
This should be easy fix.
abchatra commentedon Sep 28, 2022
Likely block definition syntax is incorrect for one of the blocks
thsparks commentedon Sep 28, 2022
Looks like there's actually several blocks under "more" that aren't being displayed correctly. They're just all overlapped at the top of the screen, so it looks like one block. It displays correctly when used in MicroBit, so I'm wondering if it could be an issue with Arcade's handling of the "more" behavior, rather than an issue specific to the extension itself... Now trying to pin down another arcade extension that utilizes the behavior to confirm.
abchatra commentedon Sep 28, 2022
Suggestion: You can use https://makecode.com/playground to copy the block definition and see if it repros there.
thsparks commentedon Sep 28, 2022
Good point. And you're right, seems like something is off with the extension's block authoring.
I was also able to confirm that "more" worked correctly in Arcade for a sample extension I had sitting around, so that's some additional confirmation that it's something specific to this extension. Will continue to investigate...

abchatra commentedon Sep 29, 2022
I am going to remove from this release as this is not a regression. However if you have a fix, feel free to cheery-pick to stable tomorrow.
abchatra commentedon Mar 12, 2025
Still repros.
4 remaining items
github-actions commentedon Dec 8, 2025
Recommendation for Triage
Issue Type: bug
Status: info-complete
Label(s): blocks, extension
Duplicate Issue(s): #3901 (exact duplicate - closed as completed)
Likely Related: No other related issues found
Suggested Priority: p2
Complexity: low
Copilot Agent Ready: ✅ Yes
Recommendations for Assignee
Analysis
This is a bug in the radio extension where blocks in the "more" submenu are overlapping and appearing unusable when displayed in Arcade. Team discussion (comments from
@abchatraand@thsparks) confirmed this is specific to the radio extension's block definitions rather than a general "more" menu issue in Arcade - the "more" menu works correctly for other extensions. The root cause is likely incorrect block annotation syntax in the radio TypeScript files in pxt-common-packages.Duplicate & Related Issues
Duplicates:
@abchatra's comment from March 2025)Related Issues:
Location Hints
The radio extension is defined in pxt-common-packages (not pxt-arcade itself), but should be triaged here:
../../node_modules/pxt-common-packages/libs/radio/radio.ts- Contains block definitions with//% blockannotations that likely have syntax errors../../node_modules/pxt-common-packages/libs/radio/shims.d.ts- Contains additional block definitions/home/runner/work/pxt-arcade/pxt-arcade/libs/radio/pxt.json- Points to the pxt-common-packages implementation viaadditionalFilePathThe issue is in the radio extension's block annotations in pxt-common-packages, specifically in how blocks are marked as "advanced" (which puts them in the "more" submenu). Look for blocks with
//% advanced=trueannotation and check for missing or incorrect parameters in the block definition syntax.Next Steps
Can assign to Copilot Coding Agent: ✅ Yes, ready as-is
Reasoning: This is a well-defined bug with clear reproduction steps, existing team analysis confirming the root cause (block definition syntax), and a known location (radio extension in pxt-common-packages). The fix involves correcting block annotations, which is a straightforward code change suitable for automation. Team confirmed this "should be easy fix" in 2022, and it's still reproducible as of March 2025.