In order for the team to efficiently identify and fix issues, we need as much information as possible about how and where you have experienced trouble. Here are two checklists to follow when submitting technical issues.
Front-end applications
When struggling with an issue, a faulty configuration should always be considered as a possible cause for the issue you may be experiencing. Have a look at our troubleshooting articles as a start. Rehive offers a wide range of configurability and certain requirements are needed for each flow to work well. App and dashboard errors should point you in the direction of the issue.
If you still struggle to find the issue, please contact your Account Manager and include the following information in your request:
Which app you are experiencing the issue in (dashboard/web app/mobile app - specify whether it is your white-label mobile app or the Rehive test app)
If a mobile app, specify the version number that is experiencing the issue.
Specify the flow and steps taken when experiencing the issue. It is best to include a screen recording and/or screenshots.
The desired outcome of your steps and the actual issue that is being experienced
The user(s) experiencing the issue and any transaction information available.
The aim of this process is to allow our team to identify potential issues in your approach and reproduce the issue as fast as possible with the goal of identifying exactly where the problem lies.
API
When experiencing difficulties with the API or any extensions the best place to start is the developer documentation, if you still struggle to resolve your issue, please request assistance and include the following information:
The ID of the company where the issue is occurring.
The ID of the user (in the company) that is experiencing the issues. Please ensure that this user is the owner of the API token used in your API requests.
The API request/response information:
The request URL: including any arguments or parameters.
The request method.
The request body in JSON format (mask out any private info like passwords).
The headers (please only include the first 8 characters of the token in the Authorization header and mask out the rest)
The response status and body.
The expected outcome of the API request, should it not be obvious what the error is based on the response status and body.
If you are accessing the API via a Rehive-supported SDK, please provide us with the SDK, its version, and a snippet of code illustrating your usage of the SDK. Please be explicit about any errors so that Rehive can investigate and debug based on concrete information.