Store Review Experiences
WordCrush was rejected again: local tests and store approval are different results
WordCrush version codes 6 and 10 received App stability rejections. We separate local failures, regression tests and the store’s decision.
Updated: 2026-10-20
The real case
A game that opens on a developer’s device can crash in another review flow. Google Play rejected WordCrush version code 6 on 10 October 2026 after a test crash. Our project record describes a reproducible screen-restoration failure after Android terminated the background process.
What to check
That local failure was addressed and specific emulator tests passed. Google supplied no device or stack trace, so this does not prove the reviewer hit the same failure. A further notice received on the morning of 20 October in Türkiye rejected version code 10 for App stability too.
Test the submitted package through clean installation, background return, process restoration, connectivity changes and core gameplay. Compare findings with Android vitals and pre-launch reports where available. A passing local regression test is useful evidence; approval is a separate result.
- Verify that tested and submitted packages match.
- Test process restoration and background return as well as cold starts.
- Track later decisions separately from local test results.
Confirmed outcome
The 20 October notice confirms a rejection of version code 10. It does not establish the outcome of a later build or submission.
These checks can help reduce avoidable issues; they do not guarantee store approval.
Related game or app
These are real product images from the stores, not evidence of the screens seen during the rejection.
More in this series
Explore the other lessons from our store review experiences.