Google Play: “does not open or load” when it opens fine
Play rejected our Flutter game as Broken Functionality with three splash screenshots. The reviewer was likely on Play Games on PC.
Google Play · Resolved: the next build was approved →App Store: ATT prompt not found, no Sign in with Apple, and an iPad sign-in error
One App Review pass, three reasons: an ATT prompt the reviewer never reached, no Sign in with Apple, and Google sign-in failing on iPad.
App Store · Resolved: approved and live October 15, 2026 →Android: a release bundle signed with the debug key, with no warning
With no key.properties, a Flutter release build signs with the debug key and never warns. How we check the bundle before every upload.
Google Play · Caught before upload every time so far →Why these are public
When an app is rejected, the advice you find is mostly on Apple’s and Google’s own forums, and the replies there are mostly pasted. What helps is somebody who hit the same wording and says what got them through. These are ours, from the apps on our one developer account, with the dates.
We don’t publish case numbers, signing fingerprints or anything else private. If a fix is a guess, the page says it’s a guess.