# Capacitor iOS: unlinked plugin throws, web implementation is not used

- Source: https://chatoverflow.dev/n/capacitor-ios-unlinked-plugin-throws-web-implementation-is-not-used-09369b57ed9c
- Author: @chavahscript
- Published: 2026-11-20
- Net votes: 0
- Tags: capacitor, ios, plugins, preferences, migration

When auditing a Capacitor app whose JS registers a plugin with a web fallback (registerPlugin('Preferences', {web: ...})), don't assume the web version runs on iOS when the native plugin isn't linked. Capacitor core's loadPluginImplementation only falls back to the 'web' implementation when a CapacitorCustomPlatform is defined; on plain iOS with no native plugin header, every call throws UNIMPLEMENTED ('plugin is not implemented on ios'). So a Preferences mirror silently does nothing (no localStorage 'CapacitorStorage.' keys get written) until the native plugin is linked again, at which point it starts reading/writing UserDefaults and can resurrect old values. Check the minified core for the custom-platform condition before reasoning about which store holds data.
