I will fix app store rejection push notifications app submission capacitor apple store


About this gig
Rejected by Apple or Google? I fix app store rejection and Play Console policy issues, then get your app live.
WHAT YOU GET
- The real reason for your app store rejection, explained in plain English
- Metadata, privacy policy, Data Safety form and permission declarations corrected
- Code fixes for crashes, Guideline 2.1 completeness and missing in-app account deletion
- Target API 36 and 16 KB page size updates so Play accepts your upload again
- A rebuilt, signed AAB or IPA resubmitted for you
- A written reply to the review team where an appeal is the right move
WHO IT IS FOR
Founders, agencies and no-code builders whose Flutter, React Native, Capacitor, FlutterFlow or native app was rejected, suspended or removed.
HOW IT WORKS
1. Send your rejection email and app details
2. I diagnose the real cause and confirm scope
3. I fix, rebuild and resubmit
4. I stay on it until the review decision comes back
NOT INCLUDED
Building a new app from scratch, ASO or keyword work, or reinstating a permanently terminated developer account.
Message me with your rejection notice before ordering and I will tell you which app store rejection package you need.
Get to know Joshua Lency
Mobile App Developer, 12 and 20 Testers, Closed Testing, App Fix, App Publishing
- FromFrance
- Member sinceOct 2026
- Avg. response time3 hours
Languages
English, French, German, Spanish, Italian
FAQ
Can you guarantee my app gets approved?
No, and be careful with anyone who does. The decision is Apple's or Google's. What I guarantee is that the stated rejection reason is properly fixed and your app resubmitted correctly. Most rejections are fixable; a few policy terminations are not, and I tell you which you have before you pay.
What do you need from me to start?
The rejection or suspension email in full, your app name and platform, and what the app does. For code-level work I need the source repository. For resubmission I need Play Console Release Manager or App Store Connect App Manager access, granted on-platform.
My app was rejected under Guideline 2.1. Can you fix that?
Yes. Guideline 2.1 covers crashes, placeholder content, broken links and dead demo accounts, and it is the single most common rejection reason. I reproduce the crash on the device model the reviewer named, fix it, and supply working review notes and demo credentials.
Google Play says my app does not target API 36. Is that this gig?
Yes. Play blocks uploads that do not target Android 16, and the extension window has closed. I raise targetSdk to 36, fix what breaks, including edge-to-edge insets and back navigation, rebuild and upload. Same for the 16 KB page size requirement on native libraries.
My app was built with Lovable, Bolt, Base44 or FlutterFlow. Can you help?
Yes, this is a large part of the work. AI-built and no-code apps are most often rejected under Guideline 4.2 for thin WebView functionality or 4.3 as a near-duplicate. I fix the build, add real native behaviour, and rewrite the submission so it reads as a distinct app.
How long does it take?
Delivery times are listed per package. Resubmission itself is fast; the store review queue is not, and that part is outside my control. Apple is usually quicker than Google on policy appeals. I give you a realistic timeline after reading your rejection notice.
Will you need my developer account login?
Never your password. Google Play uses Release Manager invites and App Store Connect uses App Manager invites, both tied to my own account and revocable by you at any time. If you would rather not grant access, I deliver the fixed build and written steps instead.
What if the app gets rejected again for a different reason?
Reviewers sometimes surface a second issue once the first is cleared. If the new reason falls within the scope of your package, I fix it within your included revisions. If it is a genuinely different problem, I quote it separately and tell you honestly which it is.

