Zoom App returning "invalid signature" errors after reactivation - Need manual platform fix

Meeting SDK
1

Hello,

We have a published Zoom marketplace app that uses recall.ai to join meetings hosted by external customers. We’re experiencing persistent “invalid signature” errors that appear to require manual intervention on the Zoom platform side.

Timeline:

  1. The original app owner account was deleted, causing the app to become invalid

  2. During this period, “invalid signature” errors occurred as expected

  3. We assigned a new owner to reactivate the app

  4. We waited about 2 weeks before resuming use of the app

  5. We resumed using the reactivated app, expecting it to work properly

  6. However, “invalid signature” errors persisted for approximately 65% of all meetings

  7. We have now stopped using this app again due to these errors

Current Situation:

  • The app credentials appear to be configured correctly

  • The errors affect both internal and external meetings

  • recall.ai has confirmed this appears to be an internal Zoom platform issue requiring manual intervention

App Information:

@yoon.conner Would you be able to help us resolve this urgently? This is impacting our production service and customer experience.

Thank you for your assistance.

2

Hi @yamaryokw
Thanks for reaching out to us and welcome to the Zoom Developer forum!
Have you made sure that the client ID and client secret of the app when you assigned it to the new owner, remain the same ?

3

Hi Elisa, thanks for the quick response.

We didn’t explicitly diff the values before/after the ownership transfer, but as far as we can tell the Client ID has not changed (it’s still lHJkeHV7QvqEHlQXFRCJww). When we reconfigured the bot, we copied both the Client ID and the Client Secret directly from the Marketplace production app page into our service, so it’s unlikely we’re using incorrect values.

Happy to provide any additional details you need.

Thanks!

— Ryo

4

Thanks for confirming that @yamaryokw
If you can, can you provide an example of an invalid signature or are you able to confirm is correctly constructed:

5

Hi Elisa, thanks — here’s an example that was flagged as invalid signature.

  • Zoom meeting ID: 74080895687

  • Failure time (UTC): 2025-10-08T07:29:01Z

  • Signature (as captured):

    eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhcHBLZXkiOiJsSEprZUhWN1F2cUVIbFFYRlJDSnd3IiwibW4iOiI3NDA4MDg5NTY4NyIsInJvbGUiOiIwIiwiaWF0IjoxNzU5OTA4NTExLCJleHAiOjE3NTk5MTU3MTEsInRva2VuRXhwIjoxNzU5OTE1NzExLCJ2aWRlb193ZWJydGNfbW9kZSI6MX0.q5K__NW4jOm1o_gZgJ1ZCz28T0ZPuJBvRCkuCmIfP7k&apiKey=lHJkeHV7QvqEHlQXFRCJww
6

Hi @elisa.zoom— just checking in. Were you able to review the failing signature I shared above?

7

Hi @yamaryokw
I created an internal ticket for our Engineering team to review this issue and will get back to you with an update soon (ZSEE-183904 internal ticket number for reference)

1 Like
8

@elisa.zoom Thanks. Any update from your Engineering team?

9

Hi @yamaryokw
We are currently looking into this issue and waiting for an update from Engineering team. I will get back to you as soon as I have a more definite answer
Thank you for your patience

1 Like