CLI to change the port visibility doesn't work

[dooriya]

Select Topic Area

Bug

Body

Hi,

We use Codespaces for our getting-started samples (e.g. https://github.com/OfficeDev/TeamsFx-Samples/tree/v3/hello-world-tab-codespaces). And we use the following GitHub CLI to automatically set the port visibility to public in our VSCode task.json:

gh codespace ports visibility 53000:public -c $CODESPACE_NAME

It worked well in the past few months, but recently we found the command doesn't take effect :(.
The port visibility is still private after executing this command, and developers will fail to access the endpoint in as an iframe in Teams.

Currently the workaround is to manually configure the port visibility through VS Code UI. However, this approach is not ideal, as it introduces additional manual steps that we aim to avoid while maintaining a seamless F5 experience.

[dooriya]

Any update on this issue? This is really block our getting-started experience using codespaces.
The port visibility is till private after running command gh codespace ports visibility 53000:public -c $CODESPACE_NAME:

[codise]

I have 100% similar issue. Seems like VS Code does something different than Github CLI or there's some undocumented feature of gh cli.