# Invalid signature only for app reviewer

**URL:** <https://devforum.zoom.us/t/invalid-signature-only-for-app-reviewer/69645>\
**Category:** Meeting SDK\
**Tags:** web-meeting-sdk\
**Created:** [May 27, 2022, 7:15am UTC](https://devforum.zoom.us/t/invalid-signature-only-for-app-reviewer/69645 "2022-05-27T07:15:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oren](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/oren/32/38052_2.png) [@Oren](https://devforum.zoom.us/u/Oren)\
**Post date:** [May 27, 2022, 7:15am UTC](https://devforum.zoom.us/t/invalid-signature-only-for-app-reviewer/69645/1 "2022-05-27T07:15:03Z")

</div>

- We are working with the websdk version 2.4.0
- We are submitting the app to approval and the reviewer keeps getting the “invalid signature” issue, yet we are unable to reproduce on our end, all works fine for us.
- We are unable to provide the invalid signature for this reason above
- We added a user role toggle in case of an invalid signature error and it “works” but this seems like its not the solution but some kind of patch, we are fairly certain we are determining the role correctly.
- We are using an SDK app and as said, seems to work fine on our end

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [May 28, 2022, 1:46am UTC](https://devforum.zoom.us/t/invalid-signature-only-for-app-reviewer/69645/2 "2022-05-28T01:46:12Z")

</div>

Welcome, @Oren,

Thank you for posting in the Developer Forum. Have you tried to decode the signature to identify what the issue may be? This forum post offers guidance on decoding and inspecting the correctness:

> [@Invalid Signature with Sample Web App](https://devforum.zoom.us/t/invalid-signature-with-sample-web-app/4005/69):
>
> Hey @rackermann, After [base64 decoding](https://www.base64decode.org/) your signature, you have the string copy at the end of your JWT Key. Please double check you are setting the correct API Key. Thanks, Tommy
