- Store
- App Store
- Rule
- Guidelines 4.8 and 2.1
- App
- Househand
- When
- October 14, 2026
- Status
- Resolved: approved and live October 15, 2026
What came back
Househand build 9 came back with three problems in one rejection.
- 4.8, Login Services. The app offers Google sign-in, so it has to offer Sign in with Apple too.
- 2.1, the tracking prompt. The reviewer couldn’t find the App Tracking Transparency prompt.
- 2.1(a), an error. Google sign-in failed on an iPad.
The ATT prompt nobody reached
We asked for tracking permission after the first job was logged, on the theory that a prompt makes more sense once the app has done something for you. Our own compliance check used to recommend that delay.
The reviewer never logged a job, so never saw the prompt, so it was “not found”. The fix was to ask at launch, before the ads SDK starts. Apple also asked for a screen recording from a physical device showing a fresh install, the prompt, and what happens after it. A simulator recording doesn’t count. We now keep that recording linked in the review notes for every later submission.
Sign in with Apple
This one is in the guidelines in black and white, and we missed it. We added Apple sign-in through Firebase’s AppleAuthProvider. Three switches have to agree: the Sign in with Apple capability on the app id, the entitlement in the build, and the Apple provider turned on in the Firebase console. Miss the last one and the button looks fine and fails.
Google sign-in on iPad
The Google sheet opened, and the failure came after it, when the Firebase credential was exchanged. We hadn’t found the root cause when we resubmitted build 11 the same day, and it was approved anyway, so we still can’t tell you what fixed it. While looking, we found anonymous sign-in switched off in Firebase even though the code used it, which no test of ours would have caught.
What to check before you submit
- Ask for ATT on first launch. Don’t hide it behind anything the reviewer might skip.
- If any third-party login is in the app, Sign in with Apple has to be there too.
- On a fresh install, tap every sign-in button once, on an iPhone and on an iPad.
- Compare the sign-in providers your code calls with the ones switched on in the Firebase console.
Our preflight check now treats a gated ATT prompt as an error, and it checks the Sign in with Apple entitlement and the Firebase providers. It can’t tap the buttons for you.