@Leo Following our previous resolution on the "design spam" issue - where we demonstrated our unique implementation, custom code, and community features - we're now facing a new submission (ID: fa69f469-2043-4069-a8be-249916c564ed) that's being blocked by similar template responses.
The new rejection claims:
That we don't have ATT implementation (we do, with screenshots)
That we need to change "Enable Location" to "Continue" (less transparent for users)
That the app should work without location (impossible for an Islamic prayer app to get prayer times, as told we did make Quran available without login and prayer times but we cannot calculate prayer times without location)
We've provided detailed evidence for each:
Screenshots showing working ATT implementation
Two-step location permission process with proper iOS system prompts
Clear explanation why location is required for Islamic prayers:
Prayer times must be calculated based on sun position
Qibla direction needs user location relative to Mecca
All Islamic prayer apps require this for religious accuracy
But just like our previous "design spam" situation, we're getting template responses that completely ignore:
Our provided screenshots
Working implementations they claim don't exist
Religious requirements that make some suggestions impossible
Previous verification of our unique features
After your help resolving the earlier "design spam" issue, this feels like déjà vu - providing clear evidence but getting template responses that don't acknowledge it.
Any guidance on breaking through this cycle would be incredibly appreciated, especially given how we resolved the previous situation.
If we need to make another appeal to the App Review Board for this please let us know and I'll get to that right away.
