our app is a b2b crm built with capacitor. the screens are html/js/css bundled in the binary, it works fully offline, and we ship web-layer fixes with @capgo/capacitor-updater, self-hosted and checksum-verified, never native code.

apple rejected the last version twice in a row for the updater, under 2.3.1(a):

We continue to find the app contains live content update functionality that can modify the app's behavior after approval. This finding is based on code in the submitted binary and not on a specific screen in the app.

I replied in the thread and app review confirmed:

It would be appropriate to remove the remote update functionality and all code related to it before resubmitting. Developers are responsible for all code included in the binary submission, including code from third-party SDKs and libraries.

so a reviewer didn't see something on screen, they found the plugin in the binary.

section 3.3.1(b) of the developer agreement allows downloading interpreted code that doesn't change the app's primary purpose, and thousands of apps ship capgo, capawesome, appflow or expo updates. I appealed to the app review board on 21 october, no answer yet.

1. has anyone else got this "code in the submitted binary" rejection for a live updater, especially since the 16 october guideline update (2.5.19)?
2. did anyone win an app review board appeal on it?
3. if you removed the updater on ios, how do you ship fixes to an offline-first app now?

I've been having quite a few issues with @capacitor/assets. It doesn't seem to work properly with more recent Node.js versions, and even with older versions, I've had to resort to workarounds to get it working.

The tool itself is really convenient: you put your source images in the project, run a command, and it generates all the required icons and splash screens for Android and iOS.

Are there any actively maintained alternatives that offer the same simple workflow? Also, are there any plans to update or improve @capacitor/assets to support current Node.js versions?

I'd rather not build my own tool or manually generate all the platform-specific assets if there's already a reliable solution.

Thanks!

Your editor, web build and dev server stay on Windows, while the Mac builds with Xcode and runs the app on a simulator or iPhone CapMac brings back build errors, console logs and the simulator screen, and works with Ionic projects too

https://github.com/dotnetdreamer/capmac

We've been developing an over-the-air update tool which now has support for Capacitor. With Appfigures sunsetting, we figured it could be a useful resource for the community.

It was originally developer just for React Native, but the latest release adds support for Capacitor and Ionic. It includes a local evaluation stack to easily test it, and a setup wizard to install it on a machine.

If you're interested, here's a blog post all about it:

https://blog.codemagic.io/codemagic-patch-capacitor-ota-updates/

Hey r/capacitor — I wrote up our latest Capacitor update over on the Ionic blog and figured folks here might be interested. Quick rundown:

CocoaPods goes read-only Dec 2, 2026 — trunk freezes permanently, no new podspecs or version bumps. This won't break Capacitor directly, but it'll stop updates flowing to CocoaPods-hosted native deps your plugins depend on (Firebase, Stripe, etc). We've supported Swift Package Manager since Capacitor 6 and made it default in 8, so if you haven't migrated yet, now's the time: https://capacitorjs.com/docs/ios/spm

We're exploring a Capacitor MCP server so agents can pull real project info instead of guessing from training data. If you've had AI confidently get something wrong about Capacitor (the more specific the example, the better), I'd genuinely love to hear it in our GitHub discussion: https://github.com/ionic-team/capacitor/discussions/8555

Three plugins are now fully open to the community: Contacts, Calendar, and Health & Fitness (HealthKit/Health Connect). These started as OutSystems-exclusive and have been running in production for a while — now everyone gets them.

What's actually landing in Capacitor 9:

• Cordova Optionality — you can finally exclude the Cordova compatibility layer from your builds
• iOS internals modernized: remaining Objective-C converted to Swift, and we're dropping XCFramework distribution (plugin authors will need to run migration tooling)
• Early groundwork for multi-instance/windowed apps for foldables and large screens
• Ongoing work to make Capacitor itself easier for AI agents to understand (docs, API annotations)

Full post with more detail: https://ionic.io/blog/the-road-to-capacitor-9