Apple's minimum SDK moved on
How you'll know: App Store Connect refuses the upload, or warns that the build used an SDK that's too old.
Fix: Apple raises the minimum Xcode and SDK for uploads about once a year. The current rule asks for Xcode 26 and the iOS 26 SDK. Newer Xcode also needs a recent macOS, so the build Mac may need updating first.
Swift 6 concurrency errors everywhere
How you'll know: After the Xcode update, a wall of warnings about Sendable types and the main actor, or hard errors if a target was switched to Swift 6 mode.
Fix: The Swift 6 compiler still builds code in Swift 5 language mode. Ship in that mode, then turn on strict concurrency checking one module at a time.
Dependencies still come through CocoaPods
How you'll know: There's a Podfile, pod install fails, or a library's newer versions aren't published to CocoaPods at all.
Fix: CocoaPods' central trunk is going read-only, so libraries now publish new versions through Swift Package Manager. Move dependencies over one by one, testing after each.
An old SDK has no privacy manifest
How you'll know: The upload email names a third-party SDK or a "required reason" API with no privacy manifest.
Fix: Apple wants apps, and many common SDKs, to declare why they call certain APIs. Update those SDKs to versions that include a manifest, then add the app's own.
Signing only worked on the last developer's Mac
How you'll know: The distribution certificate has expired, or it lived in a keychain nobody can reach.
Fix: Distribution certificates last a year. Create a new one inside your company's Apple Developer team so signing never depends on one person's laptop again.