Invalid redirect (4700) during oauth flow

App Marketplace
1

Description
We have received reports from users of an “invalid redirect” error when they attempt to authorize our app in the marketplace.

As the developer, I am also now experiencing the issue, though had no issue when the app was first published and approved. I am not seeing the issue in our development environment, using the development credentials

Error
Invalid redirect: https://app.scoir.com/oauth/zoom/result (4,700)

Which App?
Scoir Office Hours

How To Reproduce (If applicable)
Steps to reproduce the behavior:

  1. Open “Publishable URL”
  2. See error

Additional context
I created a new zoom account (basic) and am not seeing the issue. Our belief is that it’s related to the user accessing the oauth flow, not the marketplace app settings.

2

Hey @dayne,

Thanks for reporting this, we will work on fixing it asap. (/ZOOM-162618)

-Tommy

3

Hey @tommy,

Thanks for looking into this. I’m wondering if there is any progress in resolving the underlying issue or if there is more information that’d be helpful from our end.

Thanks,

  • Dayne
4

Hey @dayne,

All I need was the app name which you provided. Apologies for the delays, I have just prioritized this.

If you want an immediate work around, you can create a new OAuth app.

Thanks,
Tommy

5

Hey @dayne,

Please check to see if it works now. :slight_smile:

Thanks,
Tommy

6

Hey Tommy,

Same result as before. I’ve tried both logged out and already logged into zoom, both methods are receiving the same “Invalid redirect” error page

7

Hey @dayne,

Your app is named Scoir Office Hours right? I have requested priority to fix it.

Thanks,
Tommy

1 Like
8

@tommy

We still haven’t heard about any fix for our app. Is there any progress or someone I should be talking to to help triage the underlying issue?

9

Hey @dayne,

It should have already been fixed. Are you still seeing the issue?

I tested installing your app and did not see a redirect url error.

Thanks,
Tommy

10

@tommy

Sorry for the slow response, just getting back to working on this. Yes, I’ve been told this is still occurring, with the last instance being reported to us today.

I personally am still able to recreate it

11

Hey @dayne,

I have just sent you a private message.

Thanks,
Tommy