Building with Capacitor?

Capacitor app crashing on native bridge? We bring it back.

Capacitor lets a web app sit inside a native shell on iOS and Android with access to the real native APIs, which is terrific right up until a plugin breaks on an iOS update, a permission flow was never written, or the app review team rejects it for background location. We fix the native side without rebuilding the web side.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

capacitor-build.log

still broken

What it is

Capacitor at a glance

Capacitor is an open source native runtime for building web apps that run on iOS, Android and the web from one code base. It was created by the Ionic team and first released in 2019 as the successor to Cordova, with a modern plugin API, a thinner JavaScript bridge and much better native tooling integration.

You keep whatever front end framework you like, React, Vue, Angular, Svelte or plain web, and Capacitor wraps it in a WKWebView on iOS or an Android WebView. Plugins give access to camera, filesystem, geolocation, push notifications, Bluetooth, biometrics and hundreds of community modules. It is maintained by Ionic, now a part of OutSystems, with an active plugin community and paid Enterprise plugins for the trickier native integrations.

Type
Native runtime and bridge for hybrid mobile apps
First released
2019, 1.0 in May 2019
License
MIT core, commercial Enterprise plugins available
Maintained by
Ionic, part of OutSystems
Typically used for
Hybrid mobile apps, Ionic apps, web to app wrappers, cross platform products that share a React or Vue codebase

The honest version

Capacitor pros and cons

No technology is all upside. This is where Capacitor earns its place and where it tends to cause trouble.

Where Capacitor is strong

  • One codebase across platformsA single React, Vue or Angular codebase ships to iOS, Android and the web, which is a very large saving over maintaining three separate apps.
  • Native projects you can actually editThe iOS and Android projects live in your repo as regular Xcode and Android Studio projects, so when you need native code you can write it rather than fight the abstraction.
  • Modern plugin APIPlugins are typed, promise based and asynchronous, which is a world away from the Cordova callback pattern that preceded it.
  • Good upgrade story within a majorMinor and patch upgrades in Capacitor rarely break your app, and major versions come with real migration guides rather than a vague warning.
  • Web firstThe same app can run as a web app with the same plugin API where supported, which is useful for progressive rollouts and for shared QA.
  • Reasonable native performance for most appsFor content, forms, CRUD and most business apps, the WebView is fast enough that users do not notice. Native is only needed where it genuinely is needed.

Where Capacitor bites

  • You still ship a native appApp Store and Play Store review, provisioning profiles, signing certificates, push certificates and store listings are all in your life. Capacitor does not make iOS less iOS.
  • Plugins vary in qualityThe core plugins are well maintained. Community plugins range from excellent to abandoned, and one unmaintained dependency can block an upgrade for months.
  • WebView quirks are realiOS WKWebView and the Android WebView behave differently from desktop Chrome and from each other, and the differences show up in file inputs, IndexedDB behaviour and anything touching the keyboard.
  • Performance ceiling for heavy UIAnimations, gaming and graphics heavy screens reach a ceiling that native or React Native will clear more easily, so a hybrid is the wrong choice for those features.
  • Native expertise still requiredPush notifications, background modes, deep links, app clips, widgets and in app purchases all involve native code or configuration that a pure web developer will not know by default.
  • Review rejections hurt timelinesApp Review will reject builds for missing Info.plist usage descriptions, overly broad permissions or background location without justification, which is cheap to fix but expensive to not notice until submission.

Sound familiar?

Common Capacitor problems we fix

The Capacitor problems that bring people to us, and what you have once each one is fixed.

ITMS-90683: Missing Purpose String

App Store rejecting for missing usage strings

A new plugin pulled in camera, microphone or photo library access but the matching usage description was never added to Info.plist, and the automated review bounces the build.

Info.plist complete, review passes

AAPT: error: resource android:attr/lStar not found

Android build fails after a Capacitor upgrade

A mismatch between compileSdkVersion, the Android Gradle Plugin and the resources a plugin expects, which turns a dependency update into a cascade of resource errors.

Build chain aligned, build green

Plugin is not compatible with Capacitor 6

A plugin blocks the major upgrade

A community plugin that has not been updated in two years, no maintained fork, and the functionality the app actually needs is a small slice of what the plugin provides.

Plugin replaced or forked minimally

camera permission denied

Permission prompt never fires on iOS

The plugin was called before the permission was requested, or the first request was denied silently and the retry path was never written, so the camera never opens.

Permission flow explicit and testable

server.url points to a local IP in production

Live app pointing at a dev server

The Capacitor config was switched to a local IP for live reload during development and shipped to production that way, which an attacker or a confused user can trip over.

Config separated by environment

background location without justification

App Review flags background location

Background location enabled by a plugin default rather than a product decision, and the review team wants to know why and sees no justification in the app's description.

Only the capabilities the app earns

push notifications silent on iOS

Push notifications arrive on Android but not iOS

APNs key not uploaded to the push provider, provisioning profile missing push entitlement, or the iOS app ID is misconfigured in the Apple developer portal.

Push working across both platforms

Capacitor 3, last release 2 years ago

Project stuck on an old Capacitor version

The team has been getting by on Capacitor 3, plugin releases now target 5 or 6, and the app will not ship against the latest iOS and Android SDKs without an upgrade.

On a supported Capacitor major

What we do

Capacitor help, from build fix to rework

Fix one failing Capacitor build, or let us run the whole mobile stack.

Build rescue
Builds failing on iOS, Android or both, after a plugin update, an Xcode version bump or a Gradle change. We get the build green and explain what shifted.
Capacitor upgrades
Moving from Capacitor 3 or 4 onto a current major, with plugins replaced where they have stalled and native projects updated to the new SDK levels.
Store submission
Info.plist usage strings, permissions, background modes and review responses handled, so a submission does not sit in review for a week over a missing field.
Custom plugin development
Writing native Swift and Kotlin plugins when the ecosystem does not have one, with a tested JavaScript surface the web app can call like any other plugin.
Performance and WebView tuning
First paint, scroll performance, memory and battery investigated on real devices, with the WebView behaviours on each platform accounted for.
Managed Tech
SDK updates tracked, store policy changes watched, plugin dependencies kept green and an engineer on call who understands your mobile stack when something breaks.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Capacitor alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Capacitor questions

Something else? Call+1 737 727 7327

Should we use Capacitor or go fully native?

Capacitor wins when the product is content, forms, CRUD or standard mobile UX, and the team already has web skills. Fully native wins when the app is heavy on animations, gaming, platform specific UX or deep hardware integration. React Native sits in the middle. We will give you a plain read on which bucket your app lives in rather than default to the fashionable answer.

Can we migrate a Cordova app to Capacitor?

Yes, and that is a common piece of work. The migration path is documented, the plugin APIs are close enough that most code transfers, and the end state is on a supported runtime with modern tooling. The gotchas are usually custom Cordova plugins that need rewriting and configuration that was buried in config.xml.

Why does my Capacitor app crash on iOS but not Android?

Three usual suspects. A plugin that silently failed its iOS native implementation and returned undefined to the bridge, a missing Info.plist usage description that triggered an iOS runtime deny, or a WebView difference like file inputs or localStorage limits. We reproduce on a device, attach Safari web inspector to the WebView, and the cause is almost always visible from there.

How do we keep the Capacitor app and the web app in sync?

By sharing as much code as the product allows and being honest about where the two have to diverge. The front end code lives in one repo, plugin calls are gated behind a thin abstraction so the web build has a graceful fallback, and the mobile build only adds the native pieces that cannot exist on the web.

Can you handle the Apple and Google store submissions for us?

Yes. We prepare the build, fill in the store listing against what you supply for copy and screenshots, handle rejection responses from the review teams, and release through TestFlight and the Play Console internal tracks before a public roll out. We would rather see one quiet launch than a dramatic one.

How much does Capacitor help cost?

Free written estimates. Tell us what the app is, where it is failing, and we come back with a price before any work is scheduled.

Free estimate

Capacitor giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.