🐞 How to Report a Bug

Bug Reports
1

:lady_beetle: How to Report a Bug

Found something that is not working correctly on LanGeek?

Use this category to report bugs, broken features, incorrect content, app problems, or unexpected behavior. Clear bug reports help the LanGeek team review the issue faster and fix it more accurately.

:warning: Important: Do not share private account or purchase information here

Please do not post private information in the community forum.

If your issue is related to purchase, payment, subscription, login, account access, email address, invoices, refunds, or anything that requires checking your account, contact the LanGeek support team directly:

:envelope_with_arrow: info@langeek.co

The forum is public. Do not share:

  • passwords
  • payment details
  • order numbers
  • invoices
  • email addresses
  • screenshots with private account data
  • any other sensitive information

:white_check_mark: Before you create a bug report

Please check these first:

  • Search the community to see if the same bug has already been reported.
  • Make sure you are using the latest version of the LanGeek app or your browser.
  • Try refreshing the page or reopening the app.
  • Remove or hide any private information from screenshots before uploading them.

:compass: Where should I post?

Create your bug report in the correct category:

Problem type Where to post
Website issue Bug Reports → Website Bugs
Android app issue Bug Reports → Mobile App Bugs
iOS app issue Bug Reports → Mobile App Bugs
Dictionary issue Bug Reports → Dictionary Bugs
Not sure Bug Reports

:memo: Use the bug report template

When you create a new bug report, you will see a template like this:

## Where is the problem?

Choose one by changing `[ ]` to `[x]`.

- [ ] Website
- [ ] Dictionary
- [ ] Android app
- [ ] iOS app
- [ ] Other

---

## What page or feature?

**Your answer:**  
<!-- Example: Saved words, search, login, dictionary page for “example” -->



---

## What happened?

**Your answer:**  
<!-- Example: The audio button did not play anything. -->



---

## What should happen?

**Your answer:**  
<!-- Example: The audio should play. -->



---

## What were you using?

**Device:**  
<!-- Example: iPhone, Android phone, laptop -->


**Browser or app:**  
<!-- Example: Chrome, Safari, Android app, iOS app -->



---

## Screenshot

Attach a screenshot if you have one.

---

## Anything else?

**Your answer:**  
<!-- Optional -->

Please fill in as much information as you can. A short report is okay, but reports with details are much easier to review.

:+1: Good bug report example

## Where is the problem?

- [x] Website
- [ ] Dictionary
- [ ] Android app
- [ ] iOS app
- [ ] Other

---

## What page or feature?

**Your answer:**  
Dictionary page for “example”

---

## What happened?

**Your answer:**  
When I clicked the audio button, nothing played.

---

## What should happen?

**Your answer:**  
The pronunciation audio should play.

---

## What were you using?

**Device:**  
Laptop

**Browser or app:**  
Chrome

---

## Screenshot

Attached.

---

## Anything else?

**Your answer:**  
The problem happened after I refreshed the page.

:cross_mark: Not enough information

Try to avoid reports like these:

It does not work.

The app is broken.

There is a problem with the dictionary.

These reports are hard to review because we do not know where the issue happened or how to reproduce it.

A better report would be:

The audio button on the dictionary page for “example” does not play in Chrome on my laptop.

:magnifying_glass_tilted_left: What happens after you report a bug?

After you post, the LanGeek team may:

  • ask you for more information
  • add a status tag such as needs-info, confirmed, fixed, or not-a-bug
  • move the topic to a better category
  • merge it with an existing report if it is a duplicate
  • reply when the issue has been fixed or reviewed

:label: Common status tags

Tag Meaning
needs-info We need more details before we can review it
confirmed We confirmed the issue
duplicate The same issue was already reported
not-a-bug The behavior is expected
fixed The issue has been fixed

:pushpin: Final tip

The best bug reports answer three questions:

  1. Where did it happen?
  2. What happened?
  3. What should have happened instead?

Thank you for helping us improve LanGeek.