Currently, we frown upon this practice, unless it is an issue which we have introduced and needs to be resolved.
Our best practice recommendation for modifying applications which have already been approved for production access is:
- Create a new application in the RingCentral Developer Portal. We recommend keeping the same name, but adding some version to it (for your own tracking).
- Example: myApp_v1.0.1 (if you are making a patch change which is non-breaking)
- Example: myApp_v1.1.0 (if you are making a minor change which is non-breaking)
- Example: myApp_v2.0.0 (if you are making a major breaking change to your app)
- Update this application with the same information as your original application, but include the changes you need for the application code modifications you are introducing.
- Develop the application code to suit the new changes and use-cases you are addressing.
- Test your application and simulate production-level API requests to satisfy the graduation requirements listed on the "Status & Review" page for your app in the Developer Portal.
- Once the "Apply for Production" button is enabled, apply for production and we will review your request the following business day.
- Once your approval request has been approved and you have your production API keys, add these new keys to your application's environment variables for deployment.
- After you have successfully deployed the updated application code, suspend the former application in the Developer Portal.