Pinned Tweet
Something is seriously wrong with Apple's App Store enforcement, and more developers are starting to speak up.
Reports of sudden developer account terminations under Section 3.2(f) are raising serious questions about transparency, accountability, and the future of independent development.
I know because I'm living through it.
Years of work. Apps approved by Apple. A growing business. Then one termination notice puts everything at risk, without a clear explanation of the specific violations or a meaningful opportunity to speak with a human reviewer.
And I'm far from the only developer raising these concerns.
@Apple @tim_cook @cue, we understand the need to fight fraud, copycats, and deceptive apps. But protecting the App Store should never mean treating every flagged developer as guilty without a fair opportunity to respond.
Even former App Review leadership is publicly questioning how Section 3.2(f) is being enforced.
Developers helped build the App Store into what it is today. We deserve a voice in how it is governed.
We aren't asking for immunity from the rules. We're asking for clear explanations, meaningful human reviews, and a transparent appeals process.
A developer shouldn't need thousands of followers, media attention, or personal connections inside Apple just to get their case heard.
Behind every account is a person, a business, and sometimes an entire family's livelihood.
Apple, please listen to the developers who helped build your ecosystem.
Speak to us. Review our cases. Don't let an unexplained decision erase years of work.
I'm still fighting for my account, and I'll keep speaking up until my case is fairly reviewed.
Dan The builder retweeted
A sad end to more than 9 years of developing apps for the App Store.
Apple responded to my appeal and decided to terminate my Apple Developer account under Section 3.2(f).
I was hoping Apple's response would at least explain what exactly I did wrong, but it didn't. I've seen termination notices shared by other developers that included additional details about the violations. Mine only contains general examples of misleading or fraudulent behavior.
I think my biggest mistake was how I handled the appeal.
When I received the pending termination notice, I was shocked and submitted my appeal within 30–50 minutes. At that point, I didn't fully understand what could have triggered it, especially since I hadn't updated the affected app in more than a year.
Over the following days, I went through my old submissions and tried to reconstruct what happened. I submitted two additional explanations as I understood more about the possible issues. Looking back, I wish I had taken more time before sending my first appeal.
The app had received several rejections during its initial 1.0.0 review in 2025. I made changes that I genuinely believed addressed Apple's concerns. The app was eventually approved, followed by four updates that were all approved without a single rejection.
Then, more than a year after the last update, Apple apparently determined that those issues had not been properly resolved.
I never intentionally tried to mislead App Review or bypass its rules. I believed I had fixed the problems. But I also understand that it was my responsibility to fully understand what the reviewer was asking me to change at the time. Looking back, I may have interpreted some of that feedback too narrowly, and I take responsibility for that.
What makes this especially painful is seeing other developers, some with accounts barely a year old, who openly admit to deliberately bypassing App Store rules, such as adding Stripe payments to avoid Apple's commission, being given an opportunity to correct their violations and keep their accounts and applications. I think most people here know exactly which app I'm talking about.
Meanwhile, after more than 9 years on the App Store, my entire developer account is being terminated over issues I genuinely believed I had corrected more than a year ago.
I'm not saying my mistakes should have no consequences. I would have accepted the permanent removal of the affected app. I just wish there had been an opportunity to correct whatever remained wrong without losing my entire account and more than 9 years of work.
It's a heartbreaking way for this chapter of my life to end.
Dan The builder retweeted
Apple's decisions can push developers into severe psychological distress, mental illness, and dependence on medication or even drugs. These are real human lives, not just developer accounts.
Dan The builder retweeted
Something is seriously wrong with Apple's App Store enforcement, and more developers are starting to speak up.
Reports of sudden developer account terminations under Section 3.2(f) are raising serious questions about transparency, accountability, and the future of independent development.
I know because I'm living through it.
Years of work. Apps approved by Apple. A growing business. Then one termination notice puts everything at risk, without a clear explanation of the specific violations or a meaningful opportunity to speak with a human reviewer.
And I'm far from the only developer raising these concerns.
@Apple @tim_cook @cue, we understand the need to fight fraud, copycats, and deceptive apps. But protecting the App Store should never mean treating every flagged developer as guilty without a fair opportunity to respond.
Even former App Review leadership is publicly questioning how Section 3.2(f) is being enforced.
Developers helped build the App Store into what it is today. We deserve a voice in how it is governed.
We aren't asking for immunity from the rules. We're asking for clear explanations, meaningful human reviews, and a transparent appeals process.
A developer shouldn't need thousands of followers, media attention, or personal connections inside Apple just to get their case heard.
Behind every account is a person, a business, and sometimes an entire family's livelihood.
Apple, please listen to the developers who helped build your ecosystem.
Speak to us. Review our cases. Don't let an unexplained decision erase years of work.
I'm still fighting for my account, and I'll keep speaking up until my case is fairly reviewed.
since nobody’s giving you a straight answer:
these app removals are due to wider security breaches across the internet.
in response, tech companies panicked and started removing apps.
they found a wasp nest but torched the whole forest.
developers: patch your apps.
everyone: update your damn softwares.
Really sorry to hear this, Araz. I'm facing the same 3.2(f) termination notice, and seeing your appeal rejected is heartbreaking.
Years of hard work shouldn't end without a clear explanation and a meaningful chance to address Apple's concerns.
I still hope there's a way forward for both of us. Stay strong, brother. This isn't the end of our journey. 🙏
Interesting advice coming from someone who has experienced Apple account terminations himself.
You know firsthand how difficult this situation can be, yet you keep questioning developers who choose to protect their identity.
You've reportedly continued publishing through another company after your own terminations, so you understand how much is at stake.
I've shared my apps privately with trusted developers. Privacy isn't proof of guilt.
Instead of attacking developers asking for fair treatment, why not support meaningful human reviews and a transparent appeal process?
@tim_cook @AppleSupport @Apple
One small piece of advice for developers going public with their Apple Developer Account termination stories:
NAME YOUR APP
Share the details. Explain what happened.
Without specifics, you’re just feeding your own ego.
If you want people to care, understand your situation, and help you, give them something concrete to work with. Otherwise, your posts won’t have any real impact.
A must-watch video for every indie developer.
This explains why Apple's enforcement of Section 3.2(f) deserves serious scrutiny.
Entire businesses can be put at risk by termination decisions without clear explanations or meaningful human review.
I'm experiencing this firsthand. Years of hard work are on the line.
Please watch and share. This could happen to other developers too.
Apple terminated my developer account.
Now the former head of Apple's App Review team is speaking out about how other developers are being terminated.
Phillip Shoemaker (@pbsIdentity) helped write the rules. Now he's publicly questioning how they're enforced.
This is getting bigger than one developer's story 👇
This isn't about mindset, luck, or intelligence.
You can work hard, build from zero, follow the rules, and still have years of progress put at risk by one decision from a multibillion-dollar company.
No amount of positive thinking can fix an unfair system.
Stop blaming developers for decisions they don't control.
@AppleSupport #buildinginpublic
Dan The builder retweeted
Replying to @erikgoinsHQ
It is abhorrent for Apple to block competing stores and then arbitrarily refuse to carry perfectly fine and lawful third-party apps on their monopoly store.
Apple is playing games with the livelihoods of 1M developers and the freedom of access for 1B consumers.
Dan The builder retweeted
New video dropping tomorrow (11/2) at 12:45 PM EST.
Apple Developer account terminations are getting more attention, and now a former head of Apple's App Review team is speaking out.
I'll be covering the latest developments right here on X.
Stay tuned.
Dan The builder retweeted
After 9+ years as an iOS developer, Apple flagged my entire developer account for termination under Section 3.2(f).
The reason? Repeated App Review violations.
But my app was approved in 2025, with 4 subsequent updates approved without rejection. No updates for over a year.
This might be the scariest Halloween I’ve ever had.
Not because of ghosts, horror movies, or anything supernatural.
But because, after almost 10 years as an independent iOS developer, I might lose everything I’ve built.
On October 26, 2026, I received a Pending Termination Notice from Apple saying that app submissions from my account had “repeatedly violated the App Review Guidelines in an attempt to evade the review process” and that the violations remained unresolved after multiple resubmissions.
I’m trying to understand how my review history matches that conclusion.
Here is the full story.
I started learning Objective-C at the beginning of 2017.
At the time I had an iPhone 5c and simply wanted to build an app for myself because I couldn’t find anything in the App Store that worked the way I wanted.
For around 3–4 months I learned every day from documentation, videos and whatever resources I could find.
YouTube had far fewer good iOS development tutorials back then, and a lot of learning material was paid.
Eventually I reached the point where I thought: I can actually build this.
I still remember how amazing it felt writing some code and then seeing something I had created running on my own iPhone.
I released my first app on August 11, 2017.
That app is still maintained today.
It is written in Objective-C, which is becoming increasingly difficult to maintain, and one of my plans has been to finally rewrite it in Swift/SwiftUI.
That was the beginning of my journey as an independent developer.
I’ve never been a developer who releases dozens of apps every year.
I’ve started many ideas and abandoned many of them because somebody built something better, because I decided the idea wasn’t good enough, or simply because I no longer felt passionate about making it.
That is why the notice I received this week was so difficult to understand.
The app connected to the termination notice was first submitted as version 1.0 in April 2025.
During the initial review I had five rejections.
Unfortunately, App Store Connect no longer shows me enough detail to reconstruct every rejection from that period.
But from what I remember, they were mainly related to screenshots and App Store metadata.
One issue was that my screenshots were too marketing-oriented and did not show enough of the actual app experience.
I changed them.
Another rejection concerned content shown inside the screenshots.
One screenshot showed a man and woman kissing.
I replaced it with an image showing a marriage proposal.
That was rejected too.
As I remember, the reviewer cited the Objectionable Content guideline, explaining that the content could be considered objectionable by some users. The reviewer also referred me to screenshots attached to the rejection message, which pointed to the particular App Store screenshot I had been trying to correct.
I suspected that the title or wording displayed on that screenshot might also have contributed to the rejection.
So I changed the screenshot's text as well.
After making these adjustments, the app eventually passed review.
During those submissions I also made changes to the binary and uploaded new builds.
The important part is what happened afterwards.
Version 1.0.1 — approved April 28, 2025.
Version 1.0.2 — approved May 5, 2025.
Version 1.0.3 — approved May 27, 2025.
Version 1.0.4 — approved August 7, 2025.
Those four updates passed App Review without rejection.
Then more than one year passed.
I did not submit another update to this app.
And on October 26, 2026, I suddenly received a notice saying:
“App submissions from your account have repeatedly violated the App Review Guidelines in an attempt to evade the review process.”
It also says that after multiple resubmissions, violations described in previous correspondence remained unresolved.
That is the part I cannot reconcile with the history I can see.
After the initial review process in April 2025, Apple approved the app.
Then Apple approved four additional updates.
The last one was approved in August 2025.
As far as I can determine, none of my other apps have a history of repeatedly being rejected for the same unresolved issue either.
I have never intentionally tried to hide functionality from App Review.
I don’t use A/B testing to show reviewers a different paywall.
I don’t dynamically switch to a different paywall for review.
I don’t intentionally use dark patterns.
In this app, I have never shown a paywall during onboarding or immediately after onboarding. I also don't use promotional paywall screens that interrupt users after they enter the app.
Users are not forced to make a purchase just to get past onboarding. My intention has always been to provide a transparent experience where users can explore the app and understand its functionality without being pressured into purchasing.
My apps are not built around hard paywalls — I normally provide free functionality so users can actually use and evaluate the app.
I also regularly check my privacy policy and support pages to make sure they continue working, because I know broken or misleading links can themselves cause App Store problems.
The difficult part for me is that this is not just an app.
Independent development has been my work for almost a decade and is how I support myself and my family.
Almost ten years of work could potentially disappear because of a violation that, at least from the information currently available to me, I still do not understand.
I appealed approximately 30 minutes after receiving the notice.
Looking back, I probably should have waited until the next morning.
I received the message around midnight and didn’t sleep that night.
The appeal form also limits the response to 2,000 characters, so I had to repeatedly shorten what I wanted to explain.
The next day I realized there were things I could have explained much more clearly.
For now, I’m waiting for Apple’s response.
I hope Apple reviews the account manually and that this can be resolved.
P.S. I also want to clarify a few things about the app involved in this termination notice.
This was not an AI girlfriend / boyfriend app. Its name and icon did not imitate, copy, or attempt to resemble any other apps, brands, or popular services.
It was a simple AI image-to-video generator. Users could upload their own photos and generate AI videos from them. The app did not offer pre-made templates or similar content.
I also implemented safety checks for both uploaded images and text prompts before processing generation requests, with the intention of preventing NSFW or otherwise prohibited content.
Every new user received their first AI video generation completely free. I personally covered the cost of that generation, so users could try the app and see the results before deciding whether to spend any money.
After using their free generation, users could optionally purchase additional credits through Apple's In-App Purchase system. The app never offered subscriptions of any kind. There were no recurring payments or automatic renewals, only one-time purchases of credits when users wanted to generate more videos.
I also never actively promoted or advertised this app. I didn't create TikTok or Instagram accounts for it, run social media campaigns, or use paid advertising to attract users.
And importantly, Apple's stated reason for the Pending Termination Notice was not any of these issues. The notice specifically alleged repeated App Review Guideline violations, attempts to evade the review process, and unresolved violations after multiple resubmissions.
That is precisely what I am trying to understand, because the initial rejections were addressed, the app was approved, and all four subsequent updates passed review without rejection.
#Apple #AppleDeveloper #AppStore
@AppleSupport @Apple #IndieDev
#BuildInPublic
Another day, still no clear answers from Apple.
My entire business was put at risk under Section 3.2(f), and I'm still hoping for a fair human review.
I spent years building from zero, only to see everything threatened overnight.
I'm not asking for special treatment. I just want to understand what went wrong and have a chance to fix it.
I won't stop speaking up until my case is heard. Giving up isn't an option. 🙏
This is what years of hard work looked like before Apple terminated my developer account.
$1,729 MRR. 136 active subscriptions. Real growth, built from zero.
No shortcuts. No overnight success. Just an indie developer working every day to build a career and a stable income.
Then Apple terminated my entire account under Section 3.2(f), citing a pattern of misleading or manipulative behavior, without clearly explaining which actions justified such a serious decision.
Apps that had been approved and live for months were suddenly part of a termination I still don't fully understand.
No meaningful human conversation. No clear guidance on what to fix. Just years of work and income put at risk.
I understand Apple needs to protect the App Store from fraud, but legitimate developers deserve transparency, a fair review, and an opportunity to correct mistakes.
I wasn't making millions. I was finally starting to make a living from something I built myself.
I'm not asking for special treatment. I'm asking Apple to review my case fairly and explain what I did wrong.
Section 3.2(f) should protect the App Store, not leave developers feeling powerless against decisions they can't understand or challenge.
I'm not giving up.
#BuildInPublic @AppleSupport @Apple @tim_cook
@pbsIdentity
Dan The builder retweeted
the worst part of getting terminated by Apple wasn't losing the income.
it was people who had never used my apps, never even looked at them, telling me i deserved it.
you don't know the product. you don't know the story. you just saw "Terminated" and picked a side.
anyway. that's the last time i'm talking about it. back to building!
Replying to @ahari_araz
No you all are doing fraud and just not telling the whole story.
Fake reviews
Slop copy apps
Predatory subscriptions
Apple is cleaning house.
Dan The builder retweeted
This is what years of hard work looked like before Apple terminated my developer account.
$1,729 MRR. 136 active subscriptions. Real growth, built from zero.
No shortcuts. No overnight success. Just an indie developer working every day to build a career and a stable income.
Then Apple terminated my entire account under Section 3.2(f), citing a pattern of misleading or manipulative behavior, without clearly explaining which actions justified such a serious decision.
Apps that had been approved and live for months were suddenly part of a termination I still don't fully understand.
No meaningful human conversation. No clear guidance on what to fix. Just years of work and income put at risk.
I understand Apple needs to protect the App Store from fraud, but legitimate developers deserve transparency, a fair review, and an opportunity to correct mistakes.
I wasn't making millions. I was finally starting to make a living from something I built myself.
I'm not asking for special treatment. I'm asking Apple to review my case fairly and explain what I did wrong.
Section 3.2(f) should protect the App Store, not leave developers feeling powerless against decisions they can't understand or challenge.
I'm not giving up.
#BuildInPublic @AppleSupport @Apple @tim_cook
@pbsIdentity
Dan The builder retweeted
Now let’s recall all the posts going around pretending that any developer who loses their Apple Dev account must have automatically done something so wrong, something so evil, that the gracious @Apple had no choice but to step in & destroy their livelihood to “protect”customers.
If you have an Apple developer account or an app in the App Store, read this now and share it.
Apple rejects your app. The notice is vague, so you fix what you reasonably think is wrong and resubmit.
Apple approves it.
Months later, with nothing in review, Apple terminates your account under 3.2(f) for “a pattern of manipulative or misleading behavior.” Every app gone. No explanation of what you did.
Your crime? Trusting the approval.
Apple’s own reviewer looked at your fix, with your rejection history in front of them, and said yes. Then Apple turned that yes into evidence against you.
So who’s misleading whom?
I ran App Review for seven years and wrote the guidelines. 3.2(f) used to mean real fraud. Now it’s being used against developers who did exactly what Apple approved.
I’ve made this Substack post free for everyone. Every developer needs to see it before this happens to them.
Share it before someone you know gets that email.
phillipshoemaker.substack.co…
Dan The builder retweeted
The former head of Apple App Store review goes on record to explain what happens when Apple approves your app, then terminates your account:
If you have an Apple developer account or an app in the App Store, read this now and share it.
Apple rejects your app. The notice is vague, so you fix what you reasonably think is wrong and resubmit.
Apple approves it.
Months later, with nothing in review, Apple terminates your account under 3.2(f) for “a pattern of manipulative or misleading behavior.” Every app gone. No explanation of what you did.
Your crime? Trusting the approval.
Apple’s own reviewer looked at your fix, with your rejection history in front of them, and said yes. Then Apple turned that yes into evidence against you.
So who’s misleading whom?
I ran App Review for seven years and wrote the guidelines. 3.2(f) used to mean real fraud. Now it’s being used against developers who did exactly what Apple approved.
I’ve made this Substack post free for everyone. Every developer needs to see it before this happens to them.
Share it before someone you know gets that email.
phillipshoemaker.substack.co…
It's disappointing to see @seraleev , someone who has publicly shared his own struggles with Apple's account terminations, now questioning developers who are going through similar situations.
Not every terminated developer is a fraudster. Not everyone is comfortable exposing their identity or business publicly. Privacy doesn't automatically mean guilt.
I understand that Apple needs to fight fraud and IP violations, but that doesn't mean every termination is justified.
I've personally shared my apps and case details with trusted developers who took the time to review them.
Instead of assuming developers are hiding something, why not advocate for transparency, meaningful human reviews, and fair appeals?
You can support Apple's efforts to stop fraud without automatically defending every decision Apple makes.
Let me tell you an interesting story.
A developer contacted me after Apple terminated his developer account for repeated IP violations.
The pattern was always the same: he’d receive a complaint, fix the issue and then bring it back some time later.
Eventually, Apple terminated his account. Over $100K in payouts frozen.
He decided to go public. Here’s what he did.
He created a fake profile on X. Didn’t even reveal his real name. Didn’t disclose which app was involved or explain what had actually happened.
Sure, the story got impressions. But the result? Zero.
On the second day, X suspended his account too.
He never contacted me again…
If you want to raise awareness about a problem, you need to be willing to share the facts.
You can’t expect people to take your side when you hide the very details they need to understand what happened.























