Skip to content

docs: add @NativePlugin removal to Capacitor 9 upgrade guide - #586

Open
OS-ruimoreiramendes wants to merge 1 commit into
chore/RMET-5321-cap9-plugin-upgrade-guidefrom
chore/RMET-5305/docs-drop-native-plugin
Open

docs: add @NativePlugin removal to Capacitor 9 upgrade guide#586
OS-ruimoreiramendes wants to merge 1 commit into
chore/RMET-5321-cap9-plugin-upgrade-guidefrom
chore/RMET-5305/docs-drop-native-plugin

Conversation

@OS-ruimoreiramendes

@OS-ruimoreiramendes OS-ruimoreiramendes commented Aug 10, 2026

Copy link
Copy Markdown

Description

Extends the "Breaking changes in @capacitor/android" section in the "Updating to 9.0" upgrade guide (docs/main/updating/9-0.md) with a subsection for the removal of the legacy @NativePlugin annotation and its associated deprecated permission/activity-result APIs.

The new subsection documents the annotation removal (with a pointer to the Capacitor 3 plugin migration guide for the overall migration pattern) and provides a replacement table for each removed method.

Change Type

  • Fix
  • Feature
  • Refactor
  • Breaking Change
  • Documentation
  • Other (CI, chores, etc.)

Rationale / Problems Fixed

Capacitor 9 removes the legacy @NativePlugin ecosystem (see ionic-team/capacitor#8563 / RMET-5305).
Plugin authors and app developers hitting compile errors after upgrading need a place that maps each removed API to its replacement, alongside the rest of the Android deprecated API removals from ionic-team/capacitor#8564.

Tests or Reproductions

Content was verified against the actual removals in ionic-team/capacitor#8563 and ionic-team/capacitor#8564 : every removed symbol listed in the guide matches the source changes. Replacements were taken directly from the @deprecated javadoc annotations on the removed methods where available, and from the modern equivalents in the same files for the two methods without explicit replacement notes (Plugin.startActivityForResult(int) and Bridge.startActivityForPluginWithResult(int)).

Platforms Affected

  • Android
  • iOS
  • Web

Notes / Comments

@vercel

vercel Bot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
capacitor-docs Ready Ready Preview Aug 14, 2026 3:23pm

Request Review

Comment thread docs/main/updating/9-0.md

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking whether or not this is better suited for updating plugins to 9.0 rather than updating apps. Maybe they could have a place in both but updating plugins seems like a better place, since @NativePlugin and Plugin apis would be consumed by Capacitor Plugins, not apps.

That would mean to tie this PR to #590 instead?

What do you think @OS-ruimoreiramendes @andredestro?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose my question can apply to other API removals from #581 and #580

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, everything here is only reachable from plugin code, so the plugin guide is the better home for it.
I can re-base this PR on #590 and move the content into docs/main/updating/plugins/9-0.md, but let's see what @andredestro thinks before I move it.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, the plugin guide is the right home. plugins/7-0.md already has a "Breaking changes in code" section for exactly this. #590 just needs that section added at the top.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. @andredestro since #590 is yours, does it make sense for you to add the "Breaking changes in code" section header there, and then I rebase this PR on top and drop the content into that section? Or if you prefer, I can do it myself.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rebased on #590 and moved the content into docs/main/updating/plugins/9-0.md under the new "Breaking changes in code" section. Also pushed a small commit to #590 branch adding that section header so this could hook into it.

@OS-ruimoreiramendes
OS-ruimoreiramendes force-pushed the chore/RMET-5305/docs-drop-native-plugin branch from c7863b4 to 8c8b6f2 Compare August 14, 2026 15:20
@OS-ruimoreiramendes
OS-ruimoreiramendes changed the base branch from chore/RMET-5304-cap9-android-deprecated-apis to chore/RMET-5320-cap9-app-upgrade-guide August 14, 2026 15:23
@OS-ruimoreiramendes
OS-ruimoreiramendes changed the base branch from chore/RMET-5320-cap9-app-upgrade-guide to chore/RMET-5321-cap9-plugin-upgrade-guide August 14, 2026 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants