App Store upload blocked: 'PLA Update available' when creating the IPA
Unable to process request - PLA Update availableShort answer
Apple has published an updated agreement and your team has not accepted it yet. Your code and signing are fine. The Account Holder must sign in at developer.apple.com, accept the updated Program License Agreement, and then accept any updated Paid Apps Agreement in App Store Connect. Retry the export after that.
Fix it fast
1Find out which cause you have
Open your account landing page and App Store Connect in a browser. An update notice or banner there names the agreement that is waiting.
open https://developer.apple.com/account2Match what you see, then jump to its fix
- 1
A banner on developer.apple.com/account asks you to review and accept updated termsThe updated Apple Developer Program License Agreement is not acceptedFix - 2
An alert in App Store Connect says a new Paid Apps Agreement is availableA new version of the Paid Apps Agreement is waiting in App Store ConnectFix
- 1
What does the error look like?
Unable to process request - PLA Update available
Cause 1 of 2
The updated Apple Developer Program License Agreement is not accepted
1Check
When an agreement is updated, Apple notifies the Account Holder, who must accept on behalf of the organisation. Other roles can see the notice but cannot accept.
open https://developer.apple.com/account2Fix
Ask the Account Holder to sign in, review the terms and accept. Then wait a few minutes and retry the export.
flutter build ipa3Verify
The banner is gone and flutter build ipa and the upload finish without the PLA message.
flutter build ipaConfirmed by developer.apple.com
Cause 2 of 2
A new version of the Paid Apps Agreement is waiting in App Store Connect
1Check
Until the latest Paid Apps Agreement is accepted, Apple says you cannot create a new app or In-App Purchase. Only the Account Holder can sign it.
open https://appstoreconnect.apple.com2Fix
In App Store Connect choose Business, find the Paid Apps row on the Agreements tab, click View and Agree to Terms, read the terms and click Submit. You may be asked for a two-factor code.
# App Store Connect > Business > Agreements > Paid Apps3Verify
The Paid Apps row no longer asks for action and the upload goes through.
xcrun altool --upload-app --type ios -f build/ios/ipa/*.ipa --apiKey your_api_key --apiIssuer your_issuer_idConfirmed by developer.apple.com
How do I stop it coming back?
- Keep the Account Holder's contact details current so agreement notices reach a person who can act.
- Check the account landing page before a release day.
- Tell the Account Holder early when a release depends on a signature.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fixMobile apps
FirebaseMessaging.getAPNSToken() returns null on iOS
FirebaseMessaging.instance.getAPNSToken() returns null
getAPNSToken() gives null when iOS has not handed the app an APNs token yet or never will.
4 causes, each with a fix