ovr-platform-util set-release-channel-build fails when targeting the default Production channel

We are using ovr-platform-util "set-release-channel-build" command in our release pipeline to push our latest builds to Oculus dashboard. We have no issue with our internal channels, but it's impossible to push to the default production channel of the app.

This channel was present by default when creating the app in Oculus dashboard, and we use it to release to our users so it's not possible to switch to a different one.

Things we tried:

- Creating a test channel with spaces and parenthesis in the name: the set-release-channel-build command works on the test channel

- Deleting an unused internal channel called "Production" to avoid potential name conflicts: no changes

- Calling the set-release-channel-build command using "Production" to see check if oculus use a different name internally for the default production channel: no changes

We noticed that unlike all other channels in the dashboard, this one does not show a user count. All other channels have one, so there might be something to it, like the Oculus API not treating it as a regular channel?

Would really appreciate some feedback from Meta/Oculus on this as it's impossible for us to have a functional release pipeline for our Quest app at the moment.