API Endpoint(s) and/or Zoom API Event(s)
The beta Authorization URL for my prod app that I’m changing to use RTMS streams does not show my new permissions
**The authorization on the left is pointing to a development app the authorization on the right is from our active production app but using the beta authorization URL that I thought allowed me to see and test changes.
Description**
One of my coworkers got the error trying to install the app
But the owning account has permissions to RTMS does every beta account need permissions as well?
Error?
[Error] Failed to stop rtms on startup Error: API hasn’t passed marketplace verification.[error from web: code:40316, msg:‘This api is not supported’]
How To Reproduce
Steps to reproduce the behavior:
1. Try installing the app
2. It will appear disabled because it is missing permissions that cause it to fail to load.
Hi @Canary_Speech! Looking at your app, that Beta Test link may have expired, and it may be using a previous version of the app.
I see the right scopes in the Production version of the app, if you request to share the app for beta testing (while that app review is underway), the new scopes should appear 
1 Like
@michael.zoom we are trying to deploy an update to the existing app.
The UI doesn’t allow me to change anything or request to share the app. When I click the “request extension” button it gives me the error: Your app has been published.
I don’t know how else I was supposed to go about updating the existing app. If you could somehow update the sharing ability that would help. Or, if you could help push our app through the review process to production that would be great.
Please help!
Hi @Canary_Speech
If you have made any changes to your app, you will need to resubmit it for an update review to the Marketplace team. I will also loop in the Marketplace team for additional help here! @yoon.conner
@Canary_Speech
Hi team, please test using the development credential, as the newly added RTMS scopes are not yet live in production.
The app reviewer will also use the development credential to test. Once the update is approved, the scopes will be available in production, and users can authorize the production credential to start using the app.
Ok, we are using the development credential and have been testing. It limits us to the users in our account. I guess having RTMS as part of the update is causing the issues with using the beta test?
We are working on getting RTMS approved for production and the hopefully you can enable the Beta Test for us?
@Canary_Speech
The development authorization URL works only with users within your account or the app reviewer’s. To get it available in production authorization URL, the app needs to pass the review first.
Once your app is approved, users outside of your account can utilize the new features of the app (i.e. use the production authorization url).
I understand. Is there any way to get the Beta Test Url working so we are not just limited to the people on our account?
Hi @Canary_Speech
You can request a beta test URL by following the guidance here:
There is nothing in the document you shared that allows me to request a beta test URL once the app has been published. Here is a snippet from the document:
After you publish your beta app, the authorization URLs become invalid.
To test unpublished changes to your app, use the development version of the app locally.
At the top of your app's build flow, select Development, and in the left navigation pane select Local Test.
In my situation I published an app and found the recording bot to be to slow and cumbersome. So, I changed the app drastically to use RTMS. But, when I went to publish the changes it needed new scopes etc so it has had to go back through the approval process. And there is no way to test the app using the beta test link because it is expired and the “request extension” button has been disabled because the app was published. So, I’m stuck testing with one of the 10 users on my account.
This seems broken!
Thanks for sharing more details @Canary_Speech
I just reached out to the Marketplace and it looks like once the app is approved and published in the Marketplace, you won’t be able to the beta test or to request an extension. This because the beta test uses production credentials and your app is already in production.
The recommendation in this instance is to create a duplicate application and test there or submit your app for review with the Marketplace team and they will be able to test your app to make sure it all works fine.
Let me know if that helps
1 Like
Thank you! That is helpful.
1 Like