iOS build broke after an Xcode update
A new Xcode release changed a signing default or deprecated a pod, and the Runner project stopped compiling on the build machine.
iOS archive produced again
Working with Flutter?
A Flutter project that built fine last year often won't survive the next Xcode or Android SDK update. We work through the toolchain, the Dart version, the plugins and the store paperwork until the build is green and the app is on the store.
What it is
Flutter is Google's open-source UI toolkit for building apps for iOS, Android, web, Windows, macOS, Linux and embedded devices, all from a single Dart codebase. Its first stable release landed in December 2018.
It uses its own rendering engine, originally Skia and now moving to Impeller, together with a widget composition model that draws every pixel itself. Teams tend to pick it when they want pixel-perfect design parity across iOS and Android without maintaining two separate native projects.
The honest version
No technology is all upside. This is where Flutter earns its place and where it tends to cause trouble.
Sound familiar?
The Flutter problems that bring people to us, and what you have once each one is fixed.
A new Xcode release changed a signing default or deprecated a pod, and the Runner project stopped compiling on the build machine.
iOS archive produced again
A Gradle, AGP or Android SDK bump has pushed the project past what the current plugins or build files support.
assembleRelease green on CI
Apple's privacy manifest rules now require declared reasons for several common APIs, and a plugin inside your app uses one without declaring it.
Accepted on the next upload
A year or two without upgrades, breaking changes piled up, and nobody wants to be the one to bump it and watch half the plugins fail.
Running on current stable
Lifecycle bugs, stale async callbacks and controllers that outlive their widgets only surface under real-world timing.
Crash-free sessions back up
Two packages demand incompatible versions of a shared dependency, often after a major framework upgrade.
A lockfile that resolves
No source, no signing keys, nobody on the App Store Connect team, and a binary on the store that nobody can rebuild.
Everything back in your name
What we do
Call us for one failed build, or hand us the whole app.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. The usual culprits are signing defaults, deprecated CocoaPods specs, a bumped iOS deployment target or a plugin that has not caught up with the new Xcode. We work through the Runner project, the Podfile and the plugin set until a release archive comes out the other end.
Yes. We start by taking an inventory of what you actually have: source code, signing certificates, provisioning profiles, keystores, App Store Connect and Play Console access. Then we get the project building on our machines, write down what we found, and move ownership of every account into your name.
On a branch, against a copy. We bump the Dart SDK and Flutter in stages, work through the breaking changes, replace plugins that have been abandoned, and run the app on real devices before merging anything. For a project a year or two behind, this is usually a few days of focused work rather than a rewrite.
Common reasons right now are missing privacy manifest declarations (ITMS-91053), outdated SDK versions, metadata that does not match what the app actually does, and permission strings that fail to explain why a feature is used. We work from Apple's rejection notice and address each item before the next upload.
Usually stay, if the app fits the model Flutter is good at. We will tell you plainly where Flutter is a poor fit, for example heavy platform-specific integrations or a product that lives mostly in a background service, and when a native rewrite would genuinely pay for itself.
Estimates are free. Describe what is broken and what you want shipped, and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: