Fix Play Store Crash Issue
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
My Android app runs flawlessly on every phone I have tested, yet Google Play keeps rejecting it for a “policy violation – broken functionality.” Their reviewer notes claim the app opens but immediately crashes. I need fresh eyes to identify whatever edge-case bug or configuration problem they are hitting, correct it, and guide me through a successful resubmission.
Here is where I am so far:
• Built the project with Cursor (essentially vanilla Android tooling underneath).
• Internal and external testers report no crashes; Logcat shows clean launches.
• The rejection arrives at the review stage only, citing the App Content Policy section on broken functionality.
Your role will be to:
1. Pinpoint the crash scenario Google’s test device encounters—using Logcat, Play Console pre-launch reports, or any other diagnostics you trust (Crashlytics, Firebase Test Lab, etc.).
2. Patch the code or manifest settings causing the fault and confirm stability across API levels.
3. Produce an updated, signed AAB ready for upload.
4. Stay with me through the next review cycle until the app is finally approved.
Acceptance criteria: the build passes Google Play review without the broken-functionality violation, and no launch crashes appear in pre-launch or production crash reports for at least 72 hours post-publish.
If this sounds straightforward for you, let’s get my app over the finish line.
Here is where I am so far:
• Built the project with Cursor (essentially vanilla Android tooling underneath).
• Internal and external testers report no crashes; Logcat shows clean launches.
• The rejection arrives at the review stage only, citing the App Content Policy section on broken functionality.
Your role will be to:
1. Pinpoint the crash scenario Google’s test device encounters—using Logcat, Play Console pre-launch reports, or any other diagnostics you trust (Crashlytics, Firebase Test Lab, etc.).
2. Patch the code or manifest settings causing the fault and confirm stability across API levels.
3. Produce an updated, signed AAB ready for upload.
4. Stay with me through the next review cycle until the app is finally approved.
Acceptance criteria: the build passes Google Play review without the broken-functionality violation, and no launch crashes appear in pre-launch or production crash reports for at least 72 hours post-publish.
If this sounds straightforward for you, let’s get my app over the finish line.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.