Could you please make the nativeClientId optional in the headless CLI mode?

[m98]

Is this feature request related to a new or existing Amplify category?

auth

Is this related to another service?

CLI

Describe the feature you'd like to request

I followed the Amplify Headless mode documentation to create a headless_pull.sh file.

In the Cognito user pool, I only have one app client which is for the website. There is no native app. But when I write the headless_pull.sh, it says: "auth headless is missing the following inputParams nativeClientId"

But for my case, I don't need any native app client, so I can't have a nativeClientId which is required.

Describe the solution you'd like

I think it would be great if you can make the native app client (nativeClientId) field optional.

Additional context

Even after adding a nativeClientId, I am getting a new error now which I saw it's already tagged as a bug, do you have any workaround for it?
"OAuth properties for the app clients are not matching."

Is this something that you'd be interested in working on?

• 👋 I may be able to implement this feature request

Would this feature include a breaking change?

• ⚠️ This feature might incur a breaking change

[josefaidt]

Hey @m98 👋 thanks for raising this! This does appear to be a duplicate of the linked issue, #7821 , however as a workaround can you try specifying the same client ID for both app and native to see if that mitigates the issue for now?

[m98]

I can confirm that using the same (duplicate) id for both web and native App solved the issue. But I hope the fix does not break it! Because I believe many people already have done this to temporarily fix the issue.

[agnelnieves]

Came into this issue because of the same reason.

[josefaidt]

Closing in favor of tracking the existing issue, #7821

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.