Troubleshooting
The guide helps developers troubleshoot app and solutions errors using the following APIsL
- GetVersionsDiff: Retrieves the fileId containing the diff between two versions of an app or a solution.
Endpoint: GET /developer/logs/{listingId}
Path Parameters
Parameter | Description |
---|---|
listingId path | The app or solution listingId. |
type* query | Specifies the type of log. Available values: APP, SOLUTION |
The following returns the event logs for the vehicle-trackers app.
Async Response
The Get Versions Diff APIs support asynchronous responses under specific conditions. This enhancement ensures efficient processing when comparing different versions between two solutions. For comparisons between two applications, the response remains synchronous.
Developers can use the following endpoint to get the HTML diff.
Path Parameters
Parameter | Description |
---|---|
versionId1 | The first version of the app or solution. |
versionId2 | The second version of the app or solution. |
type query | Specifies the type of version IDs. Available values: APP, SOLUTION |
Response details
If versionId1 and versionId2 are both app types, then the API returns an HTML diff.
Developers can use the following endpoint to get the HTML diff.
Path Parameters
Parameter | Description |
---|---|
tenantId | The tenant of the app or solution. |
versionId | The version of the app or solution. |
Response details
If the versionId is an app type, then the API returns an HTML diff.
Endpoint: GET /developer/diff/{statusId}
Developers can use this endpoint and pass the statusId to get the HTML diff for solutions.
Path Parameters
Parameter | Description |
---|---|
statusId | The unique Id of the diff or permission status. |
Response details
Upon success, the API will return a 200 status with an HTML diff.
However, if there is no diff, then the the API returns a NOT FOUND or FAILURE status. A failure can occur if the solutionId provided does not belong to any solution or an error occurred while creating the file.
Endpoint: GET /developer/onboarding/logs
Developers can use the GetOnboardingActivity retrieve detailed onboarding logs for a given date range based on the following parameters:
- tenantId: The id for the tenant.
- itemId: The appId or solutionId.
- versionId: The appversion or solutionversion
Example request
The following example requests logs using a tenantId and date range.
Example response
The response contains an array of logs with two onboarding activity objects for the OS1Dev tenant within the specified date range.
The first activity log shows a FAILED status due to the Solution manifest file missing, while the second object represents a successful solution onboarding.