Review Process

To enable the Apple App Store and Google Play review process, we have implemented a hidden test user feature in the 95octane mobile app. This allows internal testers and reviewers to access the app without having to go through the Google or Apple sign-in process, while still keeping it hidden from regular users.

Authentication Mode

Specifically for review process, there is a hidden authentication mode that can be accessed by double-clicking on the 95octane logo on the login screen. This will automatically sign-in using a preconfigured email and password, allowing reviewers to access the app and test its features without needing to create an account or use third-party sign-in options.

Enablement

The test user feature can be enabled or disabled via the userEnabled property in the response of the GET /init API endpoint. By default, this property is set to false, meaning that the test user feature is disabled for regular users. When set to true, it enables the test user feature, allowing reviewers to access the app using the hidden authentication mode.

Rules

  • The test user feature is intended for use during the Apple App Store and Google Play review process, and should not be used by regular users.

  • The test user feature should be enabled only when necessary for the review process, and should be disabled at all other times to prevent unauthorized access to the app.

  • The credentials for the hidden authentication mode should be kept secure and should not be shared with anyone outside of the review process to prevent unauthorized access to the app.

  • Data should be seeded for the test user to ensure that reviewers can access and test all features of the app without any issues. This includes creating a test user account with preconfigured email and password, and seeding it with relevant data such as rides, routes, and other necessary information to facilitate testing of the app's features during the review process.

  • Data generated during tests should be reset in production environment after 2 days. This ensures that any test data created during the review process does not persist indefinitely in the production environment, which could lead to clutter and potential confusion for regular users. By resetting the data after a specified period, we can maintain a clean and organized production environment while still allowing reviewers to thoroughly test the app's features during the review process.