Skip to content

docs: update Capacitor 9 docs outside guides and plugin APIs - #591

Open
andredestro wants to merge 1 commit into
chore/RMET-5321-cap9-plugin-upgrade-guidefrom
chore/RMET-5322-cap9-docs-misc
Open

docs: update Capacitor 9 docs outside guides and plugin APIs#591
andredestro wants to merge 1 commit into
chore/RMET-5321-cap9-plugin-upgrade-guidefrom
chore/RMET-5322-cap9-docs-misc

Conversation

@andredestro

Copy link
Copy Markdown
Contributor

Description

Updates Capacitor 9 documentation that falls outside the app/plugin migration guides and the auto-generated plugin API pages:

  • docs/cli/commands/run.md and docs/main/guides/live-reload.md: replace the removed --live-reload/-l/--host/--port/--https flags with the new --url flag (verified directly against the CLI's current option list on the next branch)
  • docs/main/ios/index.md: iOS 15+ / Xcode 26.0+ → iOS 16+ / Xcode 27.0+
  • docs/main/android/index.md: API 24+ → API 26+ (both the general support statement and the emulator note), keeping the Chrome-vs-System-WebView distinction accurate for the new floor (Android 8-9 vs 10+)
  • docs/main/android/setting-target-sdk.md: example targetSdkVersion 36 → 37
  • docs/main/getting-started/environment-setup.md: Node 22 → 24, Xcode 26.0 → 27.0, Android Studio 2025.2.1 → 2025.3.3, minimum installable SDK API 24 → 26, latest stable Android 16 (API 36) → Android 17 (API 37)
  • docs/main/reference/support-policy.mdx: added a v9 row to all three tables (release status, compatibility recommendations, minimum supported platforms), marked Unreleased/TBD where there's no public date yet

Change Type

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

Rationale / Problems Fixed

docs/main now represents the unreleased Capacitor 9 (next), but several reference pages still described Capacitor 8 minimums and the old live-reload CLI flags. These are locked-in facts already shipped in the next branch (Node/iOS/Android floors, the --url flag), so keeping the docs stale would actively mislead anyone testing against Capacitor 9 alpha.

Internal Jira reference: https://outsystemsrd.atlassian.net/browse/RMET-5322

Tests or Reproductions

Every changed value was verified against the actual Capacitor 9 next branch (CLI option list, variables.gradle, --version outputs) rather than inferred, and cross-checked with the internal System Requirements doc for the platform floors. Verified npm run build (Docusaurus) succeeds with no broken links or routes.

Note: unlike the other changes, the support-policy.mdx v9 row records values that are still moving pre-GA (e.g. Xcode 27 is in beta at the time of writing). Decided to add it now anyway and revisit if it drifts before GA, rather than waiting until release like previous majors did.

Screenshots / Media

N/A

Platforms Affected

  • Android
  • iOS
  • Web

@vercel

vercel Bot commented Aug 12, 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 12:06pm

Request Review

@andredestro
andredestro force-pushed the chore/RMET-5321-cap9-plugin-upgrade-guide branch from 6dd69f7 to e4ff100 Compare August 14, 2026 10:22
@andredestro
andredestro force-pushed the chore/RMET-5322-cap9-docs-misc branch from ed2c887 to caf73d1 Compare August 14, 2026 10:32
@andredestro
andredestro force-pushed the chore/RMET-5321-cap9-plugin-upgrade-guide branch from e4ff100 to 0400079 Compare August 14, 2026 11:42
@andredestro
andredestro force-pushed the chore/RMET-5322-cap9-docs-misc branch from caf73d1 to 7288075 Compare August 14, 2026 11:42
Updates cap run CLI docs and the live-reload guide for the --url
flag merge, refreshes iOS/Android minimum platform mentions, and
adds a v9 row to the support policy and target SDK tables.

RMET-5322
Comment on lines 8 to 24
All Android applications must specify a target SDK version, or the version of Android that the application is designed to run on. Each year, Google releases updates to the Android operating system and subsequently bumps the version number that applications are required to target. Typically, [this date is August 31st](https://support.google.com/googleplay/android-developer/answer/11926878?hl=en) of each year. Because of this, it is important to keep your application up to date with the latest version of Android. In a Capacitor application, this is done by specifying your target SDK in the `/android/variables.gradle` file.

```groovy
targetSdkVersion = 36
targetSdkVersion = 37
```

## Capacitor Android Requirements

In Capacitor, the Android target SDK version is strongly tied to the major version of Capacitor. This means that while you could change the target SDK to a higher version and rebuild your application, there's a very strong likelihood that your application will experience issues not otherwise present. The Capacitor team releases a new major version of Capacitor every year that includes support for the new target SDK version to ensure that applications remain compliant with Google's requirements. For this reason, it is important to keep your application up to date with the latest major version of Capacitor.

## Android Target SDK Matrix

The following table shows the target SDK versions that are supported by Capacitor Android.

| Capacitor Android | Target SDK Version |
| ----------------- | ------------------ |
| 8.x | 36 |

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.

Because the targetSdkVersion is now the same as compile SDK version, perhaps this page needs tweaking? Also, we could add 9.x to Android Target SDK matrix as well?


```bash
npx cap run --live-reload --port 8100
npx cap run android --url http://192.168.1.68:8100

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.

Minor: To maintain the same command it should be without android, users can select android or ios manually afterwards.

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.

Kind of related to this, we could update the "Official Platforms" under docs/main/getting-started/faqs.md as well?

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.

2 participants