Issue with optional JWT secret field when creating App Settings page

App Development
1

Hi everyone,

While creating the App Settings page in the developer hub, I noticed that the field “JWT secret” is marked as optional in the documentation. It says that if left empty, the client secret will be used by default.

However, in practice, the system does not allow saving the configuration without entering a value in this field. Instead, it shows the error:

Expected string, received null

Screenshot attached:

Has anyone faced this issue? Is it a bug in the developer hub, or do I need to provide a fallback value manually to proceed?

image
image630×536 31.5 KB

Thanks in advance!

1 Like
2

Hi! Thank you for reporting. I can reproduce this. Looks like when adding and saving a new App Settings page it works correctly but editing an existing one has incorrect validation. The team will be fixing it promptly. Meanwhile, as a workaround, can you delete the extension and add it again?

3

This topic was automatically closed after 60 days. New replies are no longer allowed.