App Version Management
Developers can use AddAppVersion to create a new version of an existing application. This section walks through the process of creating new versions of applications and to delete development versions on the OS1 platform.
Here’s how the OS1 platform manages versions:
We support up to 2 development versions:
- The first version is in the development state, which means it is actively being worked on by developers.
- The second version is at the READY TO PUBLISH state, having been tech review approved but not yet published. This approach is designed so that developers can continue their new development work while the QA team validates the ready to publish version in preparation for publication.
LIVE VERSIONS
The OS1 platform accommodates up to 2 LIVE versions. This setup is strategic, allowing for a phased rollout of new versions.
NOTE
To create a new version, an existing version should be at least in the READY TO PUBLISH state. See the Submit for Review guide for more details on how to move the app to the READY TO PUBLISH state.
Endpoint
POST /developer/apps/{appId}/versions
Attributes
Attribute | Description |
|---|---|
version* | The new version of the app. |
parentVersion | The latest READY TO PUBLISH version will be used as the base version if the parent version is not provided. |
Example Request
The following shows an example CreateVersion request. The request creates version 2.0.0 for an app.
Response:
Upon successful execution, the API will return details of the new version, including the GUID for the newly created version.
DeleteAppVersion deletes an app version currently in the development phase.
Note: A version in any state after DEVELOPMENT cannot be deleted.
Endpoint
DELETE /developer/apps/versions/{versionId}
Response:
When successful, the API will return a 200 response code, indicating the version was deleted successfully.
Note: Ensure the version you're trying to delete is in the DEVELOPMENT state. Deleting versions in any other state will trigger an error response.