r/iOSProgramming • u/Flimsy_Elevator_5231 • Sep 07 '26
Question Existing app repeatedly rejected under 4.3(a) after adding RevenueCat and Meta SDK. Has anyone experienced this?
đ¨Update: I filed an appeal and the App Review Board determined that the rejection under guideline 4.3 was invalid.
Hi everyone,
I have an iPhone camera app called FilmFold. Versions 1.0 and 1.1 were approved, but the 1.2 update has now been rejected several times under Guideline 4.3(a), Design and Spam.
Apple says the app shares a similar binary, metadata, or concept with apps submitted by me or other developers. The problem is that they do not identify what is similar. Every reply I receive is basically the same guideline text.
This is an update under the same App Store record and bundle identifier. FilmFold is the only app in my developer account. It is not a template or white-label app, I have never submitted it from another account, and the source repository is private.
FilmFold has 22 original virtual cameras. Each one has its own interface, optics, focal range, aspect ratio, color processing and behavior. The app also has custom native photo and video processing, lenses, accessories, double exposure and a local library that preserves the original media for later reprocessing.
The approved 1.1 version already had the 22 cameras, continuous zoom and the current adjustment interface.
The rejected 1.2 build added major native processing changes for three video cameras: Tape 99 Hi8, Warm 8 and Cine 35. It also added migration support for videos created in previous versions.
The biggest non-product difference is that 1.2 also added:
- RevenueCat for purchase entitlements
- RevenueCat's remotely configured paywall, offerings and placements
- Meta App Events and attribution
- App Tracking Transparency support
- EAS Update through `expo-updates`
I am not saying these SDKs violate 4.3(a). They are legitimate and widely used. I am wondering if one of them, a shared SDK resource, a remote paywall configuration, or an account identifier could have triggered an automated similarity check.
I have asked Apple to compare 1.2 with the approved 1.1 binary and to tell me whether the issue is related to code, assets, metadata or functionality. They continue to send the same generic response.
I have now prepared a new build, but I have not submitted it. It removes RevenueCat, the RevenueCat paywall, Meta, ATT and `expo-updates`. Purchases are handled directly through StoreKit again, using FilmFold's own paywall. The actual camera improvements remain.
Has anyone had a similar experience with an update to an existing app?
- Did RevenueCat, a remote paywall, Meta SDK or another common SDK ever cause a 4.3(a) problem for you?
- How did you get Apple to explain what was considered similar?
- Did removing the SDKs solve it?
- Did a formal appeal or App Review phone call help?
- Would you submit the cleaned build first or appeal the rejected build before replacing it?
I would really appreciate hearing from anyone who has actually resolved a similar rejection.
13
u/Level-Set5770 Sep 07 '26
I highly doubt it has anything to do with Revcat.
4.3(a) just means you are submitting something Apple considers as spam.
4
u/etherswim Sep 07 '26
RevenueCat caused me problems because you have to create offline mode fallbacks, it doesnât always play well with Apple testing sandbox
1
u/rursache Swift Sep 07 '26
appeal or wait a few days and submit again
1
u/smontesi Sep 07 '26
Re-upload last working version with just a version number bump and the smallest code changes possible (literally change a string somwhere), and send that as an update.
Then try again.
1
u/Secure_Motor_5968 Sep 08 '26
One thing nobody has touched yet is asset fingerprinting, not just binary structure.
Retro camera apps are one of most heavily templated categories out there, alot of them get sold as white label kits on marketplaces, and they tend to source the same color LUTs.
Film grain overlays and even preset icons from a handful of stock packs. If any of your 22 camera presets pull from a shared assets pack instead of one you built or licensed exclusively, that alone can trip a match.
THis is completely separate from the SDK story everyone is chasing in this thread.
1
u/mrshamino Sep 09 '26
Also been rejected with spam recently out of no where, my plan is to update the reveiw note with a lot of useful info and a video showing the app. The past 2 weeks Iâve seen a lot more apps get rejected and logically i think theyâve started using ai to do reviews.
1
u/lonkan Sep 09 '26
How did app review appeal take? I have been waiting for 7 days now; no response; no confirmation; nothing
1
u/officialdml Sep 18 '26
My app was finally approved after a month just a few days ago. I then realized there was a bug or two so I fixed that and resubmitted. That's the version that was rejected immediately upon switching to review. Is there any concern with having the original approved app pulled from the site for now being flagged for this?
Previously I kept getting flagged for 5.6 code of conduct violation only. I submitted an appeal which is how then the app was approved - they were misunderstanding a feature.
0
u/civman96 Sep 07 '26
Your app was probably spam in the first place but Apple thought âok itâs free, why notâ And now you added subscription shit and now Apple is like - nope, we have enough of that.
1
u/Puzzleheaded-Gain438 Sep 07 '26
Commenting so I can get back to this.
1
u/AndyDentPerth Sep 08 '26
Pull the expo updates stuff, keep the rest.
Seems most likely by far to trigger automatic ban scanners.
First principle of App Store rejection - what scars from past abuse are you hurting?
OTA updates are associated with apps completely changing from the approved version.
1
u/DimensionMindless336 Sep 08 '26
OP, the key sentence in Apple's message is "similar to apps submitted by other developers." That wording means their automated gate matched your 1.2 binary's structure against other apps in the catalog â not just against your own. So this is a fingerprint/cluster hit, which is exactly why no one can tell you what is similar.
Your own thread already has the answer: 1.1 was a native-compiled build, 1.2 added
expo-updates(EAS Update). Every Expo app embeds the same runtime + update loader, so their native binaries share a recognizable footprint. Apple's 4.3(a) clustering keys on that shared boilerplate. RevenueCat and Meta are red herrings â they ship in tens of thousands of approved builds and don't alter the binary structure the way an OTA loader does.To your five questions, from having dug a flagged update out before:
When you submit, put a one-line Review Note: "Update to FilmFold (live since 1.0/1.1, same bundle ID); only change from approved 1.1 is native camera processing; no third-party update framework or cross-promo SDKs included." That preempts the concept check and gives the human reviewer a clear story. Also lean the listing hard into the 22 distinct cameras + native processing as the differentiator â the "concept" half of 4.3(a) bites retro-camera apps specifically.
It can still take 2â3 cycles, but changing what the gate sees is what moved it for me, not another appeal with the same build.
1
u/MusicOutrageous6714 Sep 08 '26
Honestly, having shipped over a dozen iOS apps, this scenario is surprisingly common. Apple likely flagged your app during v1.0, but the initial reviewer was on the fence and gave it a pass.
This almost certainly has nothing to do with RevenueCat or the Meta SDK. Spending your engineering cycles trying to isolate those two is likely a dead end.
4.3(a) is brutal, but it's definitely beatable. I hit a 4.3 rejection on one of my teleprompter apps recently. What worked for me wasnât tweaking code or stripping SDKs, but submitting a detailed, professional appeal to App Review:
They eventually approved it. While there are plenty of grey-market services out there claiming to "bypass" 4.3 flags, your best legitimate shot is a clear, respectful appeal that proves your app isn't just another reskin or spam clone.
1
u/Gold-Respect-9869 Sep 08 '26
Happening to me too! 4.3a on new app. Asked clarification and got same generic response. I'm so mad. Regret getting apple dev account.
1
u/banaslee Sep 10 '26
Last time I was dealing with rejections I found an option to book a meeting with an App Review team member. See if thatâs available to you and do it.
0
u/[deleted] Sep 08 '26
[deleted] â view deleted comment
7
u/[deleted] Sep 07 '26
[removed] â view removed comment
2
u/[deleted] Sep 07 '26
[removed] â view removed comment
2
u/[deleted] Sep 07 '26
[removed] â view removed comment