Working with Ionic?

Ionic app broken on Capacitor, Cordova or in review? We fix it.

Ionic apps tend to survive right up until the Cordova plugin they rely on stops working on iOS 18, or a Capacitor plugin crashes on an Android permission the manifest never declared. We work through the native layer, the plugin matrix and the store paperwork until the build goes green and the submission actually gets accepted.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

ionic-build.log

still failing

What it is

Ionic at a glance

Ionic is an open-source toolkit for building hybrid mobile applications, first released in 2013 by Max Lynch, Ben Sperry and Adam Bradley. It provides a component library that works with Angular, React, Vue or vanilla web, and pairs with Capacitor for native functionality.

The current recommendation is Ionic with Capacitor, which has replaced the older Cordova as the native runtime. Capacitor plugins give web code access to the camera, filesystem, push notifications, biometrics and the rest of the platform APIs. Ionic apps ship to iOS, Android, and as progressive web apps from the same codebase, which suits teams whose core expertise is web rather than native.

Type
Hybrid mobile framework with Capacitor native runtime
First released
2013
License
MIT
Maintained by
Ionic (Drifty Co.)
Typically used for
Cross-platform mobile apps, internal tools, PWAs that also ship as native apps

The honest version

Ionic pros and cons

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

Where Ionic is strong

  • Web stack reaches both storesA team that already builds with Angular, React or Vue can ship an iOS and Android app without learning Swift, Kotlin or a new reactive framework. The skill overlap is close to total.
  • Capacitor is a clear step up from CordovaModern async APIs, better plugin development ergonomics, and a native project structure that resembles a real Xcode or Android Studio project rather than a generated mess.
  • A mature component libraryIonic Framework ships platform-appropriate components for iOS and Android out of the box: list items, navigation, modals, tabs and gestures that follow each platform's conventions.
  • Native code only when neededMost apps never write a line of Objective-C, Swift, Java or Kotlin. Teams who need a custom capability write a Capacitor plugin and keep the main codebase in web.
  • PWA story alongside nativeThe same codebase can deploy as a progressive web app for browsers that support it, which covers users who refuse to install anything.
  • Reasonable upgrade cadenceIonic and Capacitor release on roughly annual major cycles, with migration notes that cover the majority of changes a team will hit.

Where Ionic bites

  • Web view performance has a ceilingA complex list with heavy animations will not match the smoothness of a native equivalent. For most apps the gap does not matter; for apps that live or die on scroll performance, it does.
  • Plugins vary wildly in qualityFirst-party Capacitor plugins are solid, but community plugins for less common integrations are often maintained by one person, last updated nine months ago, and incompatible with the current SDK.
  • Cordova debt is still aroundPlenty of Ionic apps started on Cordova and never migrated. Cordova plugins keep breaking on new iOS and Android releases, and the official line is to move to Capacitor.
  • Store review targets native expectationsApple and Google increasingly reject apps that feel like a website in a shell. Teams who do not spend real effort on platform-specific UI get rejections that other frameworks might avoid.
  • Capacitor plugin development needs native skillsWriting a Capacitor plugin means writing Swift and Kotlin. Teams who picked Ionic specifically to avoid native code find themselves back in Xcode when a plugin is required.
  • iOS WebView quirks are a thingWKWebView handles cookies, file URIs and CORS differently than desktop Chrome, which surfaces as bugs that only reproduce on the device and not in the browser preview.

Sound familiar?

Common Ionic problems we fix

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

Plugin Camera does not have web implementation

Capacitor plugin missing a platform

A plugin that works on iOS and Android but not on web, or the other way around, with no graceful fallback. The app crashes during development instead of showing a mock.

Every target has a working path

cordova-plugin-whitelist is no longer maintained

Cordova dependencies are breaking

A Cordova project still running on plugins the authors have abandoned, with iOS SDK bumps causing new errors every few months. The project needs a Capacitor migration, not another workaround.

Capacitor runtime with plugins maintained

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

Android build fails after a Gradle bump

An Android Gradle Plugin version mismatch, often after a Capacitor upgrade that pulls in a newer AGP than the surrounding build files support.

Android build green on current AGP

Capacitor plugin returned undefined on iOS but string on Android

Plugin returns different types per platform

A plugin bridge that resolves to a JSON string on one platform and an object on the other, which surfaces as a type error in one of the two branches of code consuming it.

Plugin returns the same shape everywhere

ITMS-91053 Missing API declaration

App Store rejects the submission

Apple's privacy manifest rules require declared reasons for several common APIs, and a Capacitor or Cordova plugin uses one without declaring it in its own manifest.

Accepted on the next upload

Signing for 'App' requires a development team

iOS archive fails on signing

A signing team unset in the generated Xcode project, a certificate rotation that was not propagated, or a bundle identifier that does not match the App Store Connect record.

Archive signs and uploads cleanly

WebView crashed: ERR_INSECURE_RESPONSE

Local assets fail with HTTPS error

A WKWebView that refuses to load content served over HTTP, or a mixed-content policy blocking an asset bundle served from a different origin than the shell.

Assets reachable from the WebView

Unable to find a specification for 'CapacitorFirebaseMessaging'

Pod install fails after a plugin change

A Capacitor plugin that added a CocoaPods dependency without updating the Podfile source list, or a plugin version pinned to a pod no longer published.

Pods install cleanly on CI and locally

What we do

Ionic help, from rescue to ongoing support

Pick up the phone for one failing plugin, or hand over the Ionic project and we work both platforms.

Rescue
Builds that will not compile, store submissions bouncing back, plugins that work in the browser preview and die on device. We get the app installable first.
Cordova to Capacitor migrations
Moving a legacy Ionic app off Cordova onto Capacitor, with plugin replacements selected, the native projects regenerated cleanly, and the old build tooling retired.
Store submissions
iOS privacy manifests, Android permissions and policy forms, metadata that matches what the app actually does, and responses to review that get the app accepted.
Capacitor plugin development
Writing a custom plugin in Swift and Kotlin when the ecosystem does not have what you need, with the bridge interfaces designed to return the same shape on every platform.
Performance
List virtualization, image handling, startup time and WebView warm-up measured on real devices, with changes that users notice rather than ones that look good on paper.
Managed Tech
Steady work on Capacitor and framework upgrades, SDK bumps for iOS and Android, certificate renewals, and the regular care that keeps a hybrid mobile app passing review.

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 Ionic alongside something else?

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

Questions

Ionic questions

Something else? Call+1 737 727 7327

Should we migrate from Cordova to Capacitor?

Yes, in almost every case. Cordova is on maintenance mode, its plugin ecosystem is thinning, and new iOS and Android releases keep breaking plugins nobody is updating. The Capacitor migration takes effort, especially around replacing abandoned plugins, but it buys years of straightforward maintenance in exchange. We plan the migration plugin by plugin so the app keeps shipping during the transition.

Why does our Ionic app work in the browser but fail on device?

Because the WebView is not a desktop Chrome. WKWebView and the Android WebView handle cookies, CORS, file URIs and localStorage quotas differently, and some plugins run through a JavaScript bridge that has different behaviors between platforms. We reproduce the failure on the actual device, trace it to the specific API that behaves differently, and either adjust the code or add a native handler.

Should we pick Ionic or React Native for a new app?

Ionic suits teams whose expertise is web and whose app is mostly screens, forms and content. React Native suits teams willing to touch more native code and wanting closer-to-native performance for scroll-heavy or animation-heavy apps. We talk through the specific app rather than pick a framework based on general preference, because the right answer depends on what the app does.

Why was our Ionic app rejected by the App Store?

The most common reasons in recent years are missing privacy manifest declarations, metadata that implies features the app does not actually deliver, permission strings that do not explain why a capability is used, and UI that feels generic rather than platform-appropriate. We work from Apple's rejection notice line by line and make each change before the next submission.

Can you take over an Ionic app from a developer who left?

Yes. We inventory the source, the signing certificates, the keystores, the Capacitor or Cordova plugin set, and the App Store Connect and Play Console access. Then we get the app building on our machines, document what we found, and transfer ownership of every account into your name before any feature work begins.

How much does Ionic help cost?

We estimate for free. Tell us what the app is doing and which store or plugin is blocking it, and a price arrives before any work starts.

Free estimate

Ionic app 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.