Bug Report Guide for the Auto Swiper Extension
Bug Report Guide for the Auto Swiper Extension
When the Auto Swiper extension breaks, the hardest part usually is not the bug. It’s figuring out what to send so we can actually reproduce it. A short, clear bug report with the right details saves back-and-forth and gives our small team a real shot at fixing it quickly.
Key takeaways
- Include your extension version, browser, dating site, and the site's language.
- Turn on Debugging Output in Options, reload the site, reproduce the bug, then export the log.
- Say what you expected to happen and what happened instead.
- A complete bug report helps us fix extension issues faster on supported sites like Tinder, Bumble, and OkCupid.
What to include in every bug report
A useful bug report starts with five basic facts. If you send these up front, we can usually get to the real issue much faster.
Your Auto Swiper version
Please tell us the exact extension version you have installed. For example, v3.44.0. Small version changes can affect how the extension behaves on sites like Tinder, Bumble, or Match.
Your browser and browser version
The Auto Swiper browser extension runs on Chrome and Firefox. If a bug happens in Chrome but not Firefox, that narrows things down right away. Please include both the browser name and version.
Example:
- Chrome 136
- Firefox 127
Which dating site you were using
The extension supports 8 platforms in the browser: Tinder, Bumble, Lovoo, Badoo, Plenty of Fish, Zoosk, OkCupid, and Match. A bug on OkCupid may have a totally different cause than a bug on Badoo.
What language the site was in
This one matters more than most people expect. If Tinder is displayed in German, Spanish, or French instead of English, labels and page text can change. That can affect how the extension reads the page.
What you expected, and what happened instead
This is the part many reports skip, but it helps the most.
Tell us:
- what you expected the extension to do
- what it actually did instead
- when the problem started
Good example: “I expected Auto Swiper to continue swiping on Bumble after applying my age and distance filters. Instead, it stopped after one profile and never moved again.”
Why these details matter for the extension
These details are not busywork. They help us narrow the problem to the right place.
The browser extension supports 8 different dating platforms and runs in Chrome and Firefox. That means the same bug report can point to very different causes depending on the setup.
Version differences can change behavior
If you’re on one extension version and we’re testing another, we may not see the same issue. Even a small update can change how a supported site like Lovoo or Plenty of Fish is handled.
Browser differences matter in Chrome and Firefox
Chrome and Firefox both support the extension, but they do not always behave the same way. A UI action, permission, or page event may fail in one browser and work in the other.
Site language can affect how the extension reads pages
If the dating site is in English on our side but in another language on yours, we may miss the bug unless you tell us. This matters on text-heavy platforms like OkCupid, Zoosk, and Match, where labels can vary by language.
In short, version, browser, site, and language help us figure out whether the problem is tied to the extension, the browser, or the site itself.
How to capture a debugging output log
If you hit a bug in the extension, please send a debugging output log. This gives us a much better view of what happened before, during, and after the error.
Follow this exact flow:
- Open Options in the extension.
- Enable Debugging Output.
- Reload the dating site.
- Start Auto Swiper and let it run until the error happens.
- Wait a bit longer after the error.
- Go back to Options and export the log.
That “wait a bit longer” step helps. Sometimes the useful log entry appears a moment after the visible problem.
Tip: turn on Debugging Output before you reload Tinder, Bumble, Badoo, or any other supported site. If you enable it after the bug, the important log lines may be missing.
A simple bug report checklist you can copy
The easiest way to send a good bug report is to use a short template. Copy this, fill it in, and include the exported log.
Bug report template
- Extension version:
- Browser + browser version:
- Dating site:
- Site language:
- Active filters:
- Steps to reproduce:
- Expected result:
- Actual result:
- Does it happen every time?:
- Debug log attached: Yes / No
Copy-paste version:
Extension version:
Browser + version:
Dating site:
Site language:
Active filters:
Steps to reproduce:
1.
2.
3.
Expected result:
Actual result:
Does it happen every time:
Debug log attached:
Example of a clear expected vs actual result
Expected result: On Tinder, the extension should keep swiping after I start it with age range and minimum photo count enabled.
Actual result: It swipes one profile, pauses, then does nothing until I refresh the page.
That kind of note is much more useful than “extension broken.” If you want more setup help first, see our guide on how to set up Auto Swiper filters.
What makes a bug report actually helpful
Specific bug reports are easier to reproduce. Vague ones usually lead to three extra emails and one long sigh from our side.
Be specific about the moment the error starts
Tell us exactly when it breaks. Does it fail right after pressing start? After 10 swipes on Bumble? Only when a match pop-up appears on Tinder? The moment matters.
Mention filters if they seem related
Auto Swiper can act on filters like age, distance, bio keywords, photo count, and verification status. If the bug only appears when one of those is active, tell us.
Example: “This only happens on Badoo when I enable verified-only and minimum 3 photos.”
Include whether the issue is repeatable
Please say if it happens every time or only once in a while. A bug that repeats on Firefox + OkCupid in Spanish is much easier for us to test than a one-off issue with no pattern.
If it helps, you can also mention whether the same problem appears across multiple supported sites, such as Tinder and Lovoo, or only on one.
What a bug report does not need
We do not need a theory. We need good facts.
Skip guesses about the cause
You do not need to tell us “the API is broken” or “Firefox blocked a script.” You might be right, but the most useful thing is still the setup, the steps, and the exported log.
Don’t send vague notes like "it’s broken"
“It’s broken on Match” does not give us much to work with. “On Match in German, Chrome 136, v3.44.0, the extension starts but never swipes after page reload” is far better.
One honest limit of the product
AutoSwiper does not fix a weak profile or guarantee matches. It automates swiping on supported platforms so you spend less time doing the repetitive part. In the same way, a debug log helps us diagnose extension issues, but it does not replace a clear description of what you expected to happen.
For broader troubleshooting, you may also want our common Auto Swiper extension problems guide or our supported dating sites and browsers overview.
What to do next
If you hit a bug, send one complete report with:
- your extension version
- your browser and browser version
- the dating site
- the site language
- what you expected and what happened instead
- your exported debugging log
That gives us the best chance to reproduce the issue and fix it faster. Start by opening Options, enabling Debugging Output, reproducing the problem, and exporting the log.
