Capacitor plugin upgrade interruption and cross-platform binary consistency

When a Capacitor-native plugin upgrade is interrupted before the remote version manifest and native binaries are fully synchronized, the application may operate with mismatched plugin versions across iOS and Android runs. This scenario is relevant for Capacitor 5.x and later, where the update command validates the remote manifest but does not expose a rollback signal if the native installation step fails partway through. Version-specific differences between iOS and Android affect how partial binaries are handled: iOS may leave an embedded framework in an inconsistent state that prevents app launch, while Android may allow the process to start but exhibit runtime failures due to missing resources. The lack of a standardized version-revert flag in the Capacitor CLI means developers have no built-in signal to confirm whether the previous plugin version remains active or if artifacts from the interrupted upgrade are present.

• What indicators does Capacitor expose to confirm which platform-specific plugin binaries are functional after an interrupted upgrade?
• How does the framework differentiate between a failed remote manifest fetch and a failed native binary installation when no rollback flag is present?
• Which diagnostic approach can reliably determine the app's native plugin state without invoking manual platform commands?