You pasted a code into the DevPlay coupon page and it didn't pay. One of seven things happened β here they are in order of likelihood, with the fix (or the bad news) for each.
CRK codes live about three weeks. Every code currently circulating in "active" lists that predates October has expired: MISSEARTHBREAD26 died Sep 14, CRKREBIRTHLIVE Aug 17, the July 6 wave before that. Check the code against our expired table β if it's there, it's dead everywhere, no matter what the list you copied from claims.
Codes are case-sensitive: MISSEARTHBREAD26 works, misearthbread26 doesn't. O's vs 0's and I's vs 1's are the classic traps. Copy-paste beats typing β every code on our pages has a copy button.
One redemption per account, forever. If you redeemed it in June on this account, it will never pay again β the reward is already in that account's mailbox history. A code can be simultaneously "expired for you, still live for your friend" only if your friend hasn't used it and it hasn't died globally.
The DevPlay page has two fields. The ID field wants the number from Settings β Info (often 50000-something); the code field wants the word-string. Swap them and the page may justβ¦ do nothing. Plain numbers are never codes. Full walkthrough: how to redeem, and Devsisters' own coupon help article β documents the same flow officially.
Rare, but real: a handful of event codes have been region-locked, and OvenBreak/Witch's Castle codes never work in Kingdom (different games, different systems β Pocket Gamer explicitly warns about this confusion). If a code is verified live globally and still fails, this is the remaining suspect.
A successful redemption mails the reward β it doesn't pop a toast. Restart the game, open the mailbox, and check the countdown on each mail. If the box was empty for a redeemed code, restart again before concluding failure.
Generators and comment-section "gift codes" invent plausible strings. If a code appears nowhere on our daily-checked list or the official channels, it doesn't exist. That's also why we don't list "community codes" without evidence β a code that can't be verified can't be recommended.
A quiet epidemic: mobile autocorrect lowercases or "corrects" all-caps codes, and the coupon page's response to a wrong-case string is just "invalid" β the same message a typo gives. Two habits end this class of failure permanently: always paste (every code listing on this site has a copy button for exactly this), and if you must type, dismiss the suggestion bubble before it commits. The code field is case-sensitive to the letter.
Codes are one-per-account, so a code can be simultaneously dead for your main and "already redeemed" for your alt β and if your alt redeemed it but your main never did before it expired, your main simply missed it. The related trap: pasting the alt's User ID while redeeming "for" the main. The coupon page pays whichever ID you paste, full stop. Guest accounts add a third layer (see the redeem guide's guest-account section) β rewards mailed to a device-local account are only as safe as the device.
The coupon page's messages map to causes pretty cleanly once you stop treating them as verdicts: "expired" means the string matched a real, closed code (your typing was right β the internet was wrong); "invalid" means the string didn't match anything, which points at typos, case, or fabrication; "already redeemed" means it matched and your account already used it β check the mailbox history before re-trying. A silent no-op is almost always the field swap. Match the message to the cause and you skip straight to the right fix above.
The rarest case: a code dropped today, you copied it from a dated source, it still says invalid. Work the checklist in order β case (paste, don't type), fields (ID in the ID box), account (the ID you pasted is the account you meant) β and if all three hold, region or a delayed rollout are what's left: wait a few hours and retry before concluding anything. A same-day invalid on a Tier-1-verified code is almost always propagation lag, not death. Give it hours, not conclusions β and today's status page will tell you if anything real changed in the meantime. Nine times out of ten, though, the answer is one of the seven above β in exactly the order they're ranked.
Then yesterday was inside the window and today isn't β codes die on their schedule, not on the day you heard about them. The other common version: your friend redeemed it weeks ago while it was live, and you're trying it now after reading an undated list. Both stories end at the same place: check the code against a dated verdict (every page in our calendar carries one) rather than a friend's memory of the internet.
| Symptom | Most likely | Do this |
|---|---|---|
| "This code has expired" | #1 | Check the expired table; wait for the next drop |
| "Invalid code" | #2 or #7 | Copy-paste from a verified source |
| "Already used" | #3 | Nothing β it worked; check old mail |
| Page accepts, nothing arrives | #4 or #6 | Re-check both fields; restart the game |
β Failure modes reviewed November 1, 2026 against the DevPlay coupon flow and current public reports.