Annotate Tester Guide

Welcome to the testing team! This guide contains all the instructions you need to get started with testing the Annotate app. If you have any questions about joining, importing your data, reporting bugs, or anything else, please feel free to ask in the help channel.

1. Disclaimers

2. Installation

iOS Testers

Please download Expo Go from the App Store. If you haven't already, send me a direct message with your email address so I can invite you. You will receive an email invitation to join "funkycqts-team". Once you click the link and log in to Expo Go, the app should load.

Android Testers

I will provide a link to download the .apk file in the testing channel. You simply need to trust the developer (that's me!) and download it to install the app on your device.

Please make sure you update your app after downloading new builds. Read the updating section for instructions.

3. Getting Started

Once you have downloaded the app:

Please note that as you join, your book covers will take some time to initially load and settle. This is completely normal and by design, so don't worry! Once most of the covers have loaded, you will be able to easily identify any that are genuinely missing.

You can double-check if a cover is actually missing (or just still loading) by tapping on a book to view its dedicated page and seeing if the cover appears there.

4. Updating the App

How to Update (Android)

  1. Open your app.
  2. Wait at least one minute.
  3. Force close your app.
  4. Open it again.

How to Update (iOS)

  1. Force close Expo Go.
  2. Ensure you are logged in (check the top-right button).
  3. If you are not logged in, tap Log In, then select "funkycqts-team".
  4. Do not open the project from "Recently Opened". Please clear your "Recently Opened" list.
  5. Tap on Annotate from the "Projects" section.
  6. Select the main branch and tap open.

5. How to Report a Bug

Tap the hamburger menu (the three horizontal lines) on the left side of your top bar, then tap Bug Reports. Fill in the mandatory fields and submit it. Your report will automatically be forwarded to the respective Discord channels.

To ensure we get all the necessary information, please try to answer the following questions in your report:

If possible, please attach a screenshot in the Discord channel when your bug report comes in. Make sure you report using your Annotate or Discord username so I can tag you if I have any follow-up questions. Adding your Annotate username to your server nickname is also incredibly helpful!

Once a bug is marked as fixed, it would be fantastic if you could retest it. If that is too much work, no problem at all — I will just go with my judgment that it has been resolved.

If you are ever unsure whether something is worth reporting, please submit a ticket anyway! We would much rather receive a report for something minor than miss an issue altogether.

There are no "bad" tickets. If something has already been fixed, isn't an issue, or doesn't need any action, we will simply move the ticket to the Done section. Every report helps us improve the app, and we genuinely appreciate the time and effort you put into testing. When in doubt, report it!

6. Missing Information in Books

If any of your books are missing covers, are the wrong editions, missing publisher data, etc., you can report this in the app by doing the following:

  1. Go to the book page.
  2. Tap the three dots on top.
  3. Fill in the missing information (optional).

You can also add a book if it's missing via the search page. Please try to include as much information as possible to ensure our librarians handle your ticket correctly. If you notice any of the database issues below, please report them to the librarians so they can be corrected: