Crux QA Bug Portal
Signed in as

Report a bug

The more detail you give, the faster we can reproduce and fix it.

Already reported? Check All reports first so we don't log the same bug twice.
Get a serious area to test before filing. Severity is still assigned by a developer.
Drop files here, or browse
Images and video. Up to 50 MB each.
Uses your description, screenshots, and recordings to draft the report for review.

Pick every mode you saw this in. The first one you pick is the main mode.

Crux QA - Read Me First

Goal: file actionable bug reports that give devs enough to reproduce + fix without follow-up questions.

How this portal works

File a bug

Use the Report form: summary, category, game mode, and a screenshot. Build, platform, device, and OS are required, but they are remembered from your last report and pre-filled, so you set them once. The portal stamps the ID, the timestamp, and your name (from your access code) on submit. There is no spreadsheet row to fill.

File from inside the app (fastest)

While playing, a four-finger tap grabs a screenshot of whatever is on screen and opens this portal with that shot already attached and the form ready, so you can file the moment you see something wrong.

Track your bugs

My reports lists every bug you filed with its live status and the build it was fixed in. All reports shows everyone's bugs, search it before filing so the same thing is not logged twice.

Verify a fix

When a dev marks your bug Ready for QA it appears under Needs verification. Reinstall the named build, retest, and mark it Fixed or Not fixed. You have the final say, not the dev.

The hunt

Every confirmed bug earns points by severity and rarity, every fix you verify earns a point, every playable you fully check (answer every item) earns a point too, and each live game mode you actually play that day is worth 2 points. Your Hunt tracks your rank, streak, and badges; the Leaderboard ranks the whole team.

1. What you're testing

Crux is a daily-puzzle iOS app (TestFlight only right now). One new puzzle per mode per day, reset at midnight UTC.

Currently 49 live puzzle modes + a few non-game surfaces (Daily Coin Toss, Daily Wager, Mystery Box, Daily Wheel, Season Pass, Crux Plus subscription).

Three currencies:

  • Coins (yellow) - earned for solving, used for shop items + IAP-adjacent purchases
  • Gems (red diamond) - premium currency, spent on hints + cosmetics + powerups
  • Bolts (lightning) - free-hint credits; usually 1 per day per mode

For testing convenience, all players currently have ~100k coins / 10k gems / 55 bolts.

2. Brand voice - when something reads wrong, that IS a bug

Crux has a deliberate, calm tone. Voice contract violations should be filed.

OK / expected:

  • Titles: Title Case With A Period.
  • Italics / emotional copy: lowercase italic, also with a period.
  • Section names: THE LOBBY, THE LOUNGE, THE GALLERY, THE CONCIERGE (these are room names, fine)

Always wrong - file it:

  • Em-dashes in any text a player sees
  • Exclamation marks (almost never, one tactical max)
  • Hype words: "amazing", "epic", "let's go", "great job", "awesome"
  • Chatbot phrases: "Oops", "Sorry about that", "Looks like", "Let me"
  • Hotel-staff metaphors (banned literal terms): "guests", "check in", "checked in", "check out", "front desk", "night porter", "linens", "the bellhop", "fresh keys"
  • Inline emoji in copy strings
  • Marketing-speak ("unlock now", "limited time")

If a string feels off, it usually is. File a Minor with the exact string + screen + voice rule it violates.

3. Bug classes that keep biting - pay extra attention here

Modal traps:

Open any popup, try X button, backdrop tap, system-back gesture, swipe-down, leave it open for ~15s. Every modal should be escapable from every state (loading / success / error).

Currency display drift:

Watch your gem/coin counter after every hint spend, claim, purchase. It should match server state immediately. File if the displayed number disagrees with what just happened (going negative is a CRITICAL).

Hint behavior:

T1 / T2 / T3 hints should each do something distinct + visible. If a tap closes the modal but nothing happens on the board, file. If buying the same hint twice charges twice but reveals the same letter, file.

Save & resume:

Mid-puzzle hit back, leave the app, force-quit. Come back. Your progress (typed letters, revealed letters, timer offset) should restore exactly.

State sync:

Claim a reward, does the lobby card update? Solve a puzzle, does the archive show "completed"? UI should reflect server state without needing a force-restart.

Multi-touch / rapid tap:

Double-tap buy buttons, mash hint pills, two-finger tap on counters. Should never double-charge or leak state.

Tutorial visuals:

Every mode has a 3-step tutorial. Check the illustration actually shows what the text describes (we've shipped wrong flags / missing drag indicators recently).

Layout on tiny + tablet:

Top bar / chrome / modals on iPhone SE (narrow) AND iPad (wide). Common: pills overlap, scrollbar overlaps grid, buttons clip to bottom edge.

4. Test devices + states to cover (rotate through these)

Don't just test on one device, bug coverage depends on the matrix:

  • iPhone 15 Pro Max (primary, but most things will look fine here)
  • iPhone SE / smaller (narrow viewport, most layout bugs surface here)
  • iPad (different padding rules, scrollbars, larger touch targets)

States worth deliberately triggering:

  • Keyboard open on text-input modes (Heat Cue, Flag Streak, Bracket City, Think 21, Passport, Tradle, Almanac)
  • Settings, Reduce Motion enabled, animations should snap, not crash
  • Settings, Colorblind Mode (Deuteranopia / Protanopia), green tiles should turn orange/blue
  • Settings, Sound off, should silence sfx without breaking anything
  • Airplane mode mid-action, should show plain-spoken error, never freeze
  • Background the app mid-puzzle for 5 min, return, state should be intact

5. Severity guide

SeverityWhat it covers
CriticalCrash, unplayable mode, blocked progress, data loss, broken currency or purchases
HighMode mechanic broken (hint does nothing, button no-op, wrong scoring), tutorial misleading
MediumNoticeable functional or visual defect with a usable workaround
LowVoice violation, copy typo, color contrast, small layout or polish issue

6. What a clean report needs

The form captures most fields for you. Spend your effort on the parts only you can write: the summary, the steps, and what you expected versus what you saw.

Write these well:

  • Summary (<=80 chars): one-line headline a dev can read in 2 seconds
  • Description: 1-3 sentences, what you saw vs what you expected
  • Steps to reproduce: numbered, terse. A dev should be able to follow them blindly
  • Severity: a developer assigns it during triage using the guide above
  • Game mode: pick the exact mode; use Lobby / Modal / Settings / Shop / Onboarding for non-game surfaces

The form already handles:

  • Build, device, OS: pre-filled from your last report, just confirm they still match
  • ID, timestamp, reporter: stamped automatically on submit

Strongly preferred:

  • Screenshot or recording: attach one. Visual bugs without an attachment are very hard to triage (the four-finger-tap capture does this for you).
  • Error code: if a toast or banner shows an error code or message, copy the EXACT text into the description

7. Before you file

  • Force-quit + relaunch the app, does it still happen?
  • Update to the latest TestFlight build, the bug might already be fixed
  • Search All reports in this portal, has someone already logged it?
  • Note your build number, fixes ship several times a day; "build 264 crashed" beats "today the app crashed"
  • Repro from a fresh device state if you can (uninstall + reinstall is a valid last resort)

8. Quick mode taxonomy (helps you describe what failed)

  • Word find / swipe: Word Hunt, Hex Hunt, Squaredle, Rooftop, Word Flow, Word Fall, Eighteen Words (form as many words as you can from the letter set before the timer runs out)
  • Word guess: Chordle, Quordle, Connections (Quartet), Bracket City (Peel), Tradle, Waffle, Room 5x6 + Room 6x7, Don't Wordle (Letter Swap)
  • Crossword: Broadsheet, Quick Crossword
  • Geography / knowledge: Almanac, Passport, Capitals (Match), Flags (Streak), Landmarks (Postcards)
  • Numbers / logic: Number Match (Take Ten), Mathle (Equation), Think 21, Wordoku (Grid), Letter Merge, One Line (Zip), The Parcels (Shikaku, draw rectangles so each number gets its acreage), Pipes (rotate each segment until the whole grid links into one leak-free network from the source), Kings (Star Battle, place one crown per row, column, and colored region so no two crowns touch, even diagonally), Crucible (merge elements to craft your way to the daily target), Reckoner (a 75-second arithmetic sprint, four choices per problem), Directions (slide arrow tiles along their lanes to clear the board at par or better)
  • Color / sensory: HueSort, Heat Cue (Thermostat), Hue Mix (mix two paint swatches, pick the resulting color from three options), Paintcision (mix paint drops freehand to match three target colors at 80% or better)
  • Sorting: Word Sort
  • Trivia / music / verse: The Attribution (who really said it), The Refrain (complete the lyric), The Polyglot (guess the language), Meter (tap the stressed beats so the line scans), The Ladder (a ten-rung general knowledge ladder with one life and two safe milestones)
  • Meta / economic: Daily Wager, Daily Coin Toss

9. Reach out

  • Critical bugs that block your testing: ping the dev channel right away, don't only file
  • Same root cause across several modes? Mention it in the description, devs may consolidate
  • Not sure it's a bug? Ask before filing, sometimes the behavior is intended

Updates

Notable changes we have shipped. Check here when you start a session.

    Tips for filing great bugs

    A few habits make your reports faster to file, easier to fix, and worth more points. None of this is hard. It just adds up.

    File fast

    Keep a laptop open beside you

    Type the description on a laptop, not the phone. You can write a clear, detailed report much faster with a real keyboard, and detail is the part that matters most. Play on the phone, file from the laptop.

    Four-finger tap opens the portal instantly

    Found something while playing? Tap with four fingers anywhere inside the game. That grabs a screenshot of what is on screen and opens this portal with the shot already attached and the form ready. File the moment you see the bug, before the details fade.

    What matters most, in order

    1. A detailed text description (most valuable)

    Write what happened in plain words and fill in the other fields. A clear written report is the single most useful thing you can give a dev. This is what gets a bug reproduced and fixed without a back-and-forth.

    2. Screenshots, second

    A screenshot confirms what you saw and pins down the screen and state. Attach one whenever it helps. It backs up your words, it does not replace them.

    3. Video, last

    Only attach a video when text and screenshots truly cannot convey it, for example a timing or animation bug where the motion is the problem. Do not lead with video. It is slow to record, slow to review, and usually unnecessary.

    Earn maximum points

    Fill in every field

    Completely filling out all the fields earns a bonus. A complete report is easier to triage and score, so it is worth more to you and to the team.

    These fields are remembered for you

    Four fields are required and autofill from your last submission so you are not retyping them every time: Build / version, Platform, Device, and OS version. They carry over, so just glance at them and confirm they are still correct rather than typing them again. The summary, category, mode, steps, expected, and actual always start fresh.

    What graders look for

    A precise, specific title. Clear numbered steps to reproduce. A sensible severity guess. Expected versus actual stated plainly. The closer your report is to "a dev could fix this without asking you anything," the higher it scores.

    Verify on the right build

    Always enter the build you actually reproduced on

    The build number is the most common source of wasted time. A wrong build causes false "still broken" and "cannot reproduce" loops, because the dev checks a different build than the one you saw the bug on. Enter the build you actually had in front of you.

    Where to find the build number

    It is in TestFlight next to the app, and in the app's own Settings or About screen. It looks like 1.4.2 (231): the version, then the build number in parentheses. Copy it exactly.

    How duplicates and merging work

    The earliest report wins

    When the same bug is filed more than once, we keep the earliest report as the main one and mark the newer ones as duplicates of it. The earliest report is the canonical report, and its reporter keeps the credit. That is why checking All reports and filing early both matter.

    A duplicate is locked to the main report

    A report marked as a duplicate is closed for you: you cannot verify it, because it is tracked and verified on the main report instead. Open it and it will point you to the main one. This keeps one bug in one place rather than split across several threads.

    Duplicates score zero points

    A duplicate earns no leaderboard points, so the same bug filed several times never multiplies anyone's score. The way to climb is to find new bugs, not to re-file known ones.

    Hide duplicates for a cleaner view

    Use the Hide duplicates toggle on All reports to collapse the merged duplicates so you see one row per distinct bug. Open a main report to see who else filed it and when, without leaving the list.

    Think a duplicate mark is wrong? Refute it

    If your report was marked a duplicate but you believe it is actually a different bug, you can refute the duplicate from your report and say why. A developer will take another look and either unmerge it or explain the match.

    FAQ

    Should I file a duplicate if I am not sure it is already reported?

    Check All reports first and search the summary. If you do not find it, file it. A near-duplicate is better than a missed bug, and devs can merge duplicates.

    What if I cannot reproduce it again?

    File it anyway with everything you saw, and note that it was intermittent and you could not reproduce it on demand. An intermittent bug is still a real bug, and your notes may be the only clue.

    Do screenshots need annotation?

    A quick circle or arrow on the problem area helps, but it is not required. A plain screenshot plus a clear description is fine.

    It might be intended behavior. Do I still file?

    If something feels wrong or confusing, file it or ask in the dev channel. Sometimes it is intended, but a confusing design is worth knowing about too.

    My reports

      All reports

      Check here before filing so we don't log a bug twice.

        Bug classes

        Groups of reports that share one root cause. A class closes when the whole group is fixed.

          Top bug hunters, ranked by severity-weighted points. Playing a live mode that day is worth 2 points. Climb the board.

            Every tester, side by side. See who leads each metric at a glance.

            A direct line to the orchestrator. Ticks show delivery: one for sent, double gray once it is read, double blue once work has started.

            No messages yet Say hi, or send a heads up. The orchestrator replies here.

            Suggest an improvement

            Propose a game improvement. These are reviewed by the developer, and only approved ones get built. This board is separate from bug reports.

            Suggestions board

            Reviewed by the developer. Only approved suggestions get built.

              Design Decisions

              Some things that look like bugs are actually intended. This page explains those decisions and the reasoning behind them. Have a read before filing, so you know what is by design and what is worth reporting.

              Decisions

              Intended behavior, explained.

                Raise an issue or share feedback

                Share an observation or something that felt unclear (like "the streak system is unclear"). This is for feedback, not strictly a bug or a feature request. The developer reads each one and decides what to do with it.

                Issues board

                The developer reviews each issue and marks it planned, fine as-is, or resolved.

                  Verify the playable ads

                  These are the little playable ads for our games. Open each one, give it a quick try, and tick off what works. If something is off, tap Fail and add a quick note. Your checks go straight to the developer.

                  Playables

                  Loading the playables…

                  Creative Issues

                  Notes testers left on the playable ads, gathered into one list to work through. Read the note, fix the creative, then tap Mark fixed to clear it from the queue.

                  Open issues

                  Loading the creative issues…

                  Community ratings

                  Everything the testers rated and checked on each playable, gathered together and ranked with the best-rated first. The top rows are the ones to push to AppLovin and Meta first. Tap a card to see each tester's checks and notes.

                  Ranked playables

                  Loading the ratings…