Getting Started
Copy a setup prompt with the install steps and the full markdown guide for this plugin.
Set up this Capacitor plugin in the project.
Use the package manager already used by the project.
Install these package(s): `@capgo/capacitor-downloader`
Run the required Capacitor sync/update step after installation.
Read this markdown guide for the full setup steps: https://raw.githubusercontent.com/Cap-go/website/refs/heads/main/apps/docs/src/content/docs/docs/plugins/downloader/getting-started.mdx
Use that guide for platform-specific steps, native file edits, permissions, config changes, imports, and usage setup.
If that guide references other docs pages, read them too.
Install
Section titled “Install”You can use our AI-Assisted Setup to install the plugin. Add the Capgo skills to your AI tool using the following command:
npx skills add https://github.com/Cap-go/capgo-skills --skill capacitor-pluginsThen use the following prompt:
Use the `capacitor-plugins` skill from `Cap-go/capgo-skills` to install the `@capgo/capacitor-downloader` plugin in my project.If you prefer Manual Setup, install the plugin by running the following commands and follow the platform-specific instructions below:
bun add @capgo/capacitor-downloaderbunx cap syncImport
Section titled “Import”import { CapacitorDownloader } from '@capgo/capacitor-downloader';Quick start
Section titled “Quick start”Download to a known folder, listen for progress, and resume after app restarts when supported.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
const progressListener = await CapacitorDownloader.addListener('downloadProgress', (event) => { if (event.id === 'offline-pack') { console.log(event.progress); }});
const task = await CapacitorDownloader.download({ id: 'offline-pack', url: 'https://cdn.example.com/large-pack.zip', destination: 'downloads/offline-pack.zip',});Robust background downloads
Section titled “Robust background downloads”Available since 8.8.0. Use this when users fetch large offline assets while switching apps.
What changed since 8.7.0
Section titled “What changed since 8.7.0”| Area | 8.7.0 | 8.8.0 |
|---|---|---|
OkHttp notification default (completed) | No ongoing notification, no foreground service | Same (unchanged) |
OkHttp notification: 'progress' | N/A (no ongoing UI) | Opt-in ongoing progress plus optional dataSync foreground service |
| FGS when service cannot start | N/A | Download still runs; progress notification still shows without a foreground service |
iOS files/..., cache/... | Under Documents | Same under Documents |
iOS private/... | N/A (treated as Documents path) | iOS only: Application Support/CapacitorDownloader |
| iOS continued processing | N/A | Optional iosContinuedProcessingTitle on iOS 26+ |
iOS paths: files/... and cache/... stay under Documents as in 8.7.0 (Documents/files/..., Documents/cache/...). Use private/... (iOS only) for Application Support. Segments with .. are rejected. On Android, private/ is not special (it is a normal relative path under app storage).
iOS AppDelegate (required): forward background URL session events. Warmup at launch alone does not deliver relaunched completions.
// SPMimport CapacitorDownloaderPlugin// CocoaPods// import CapgoCapacitorDownloader
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { CapacitorDownloaderLifecycle.warmUpBackgroundSessions() return true}
func application( _ application: UIApplication, handleEventsForBackgroundURLSession identifier: String, completionHandler: @escaping () -> Void) { CapacitorDownloaderLifecycle.handleEventsForBackgroundURLSession( identifier: identifier, completionHandler: completionHandler )}iOS 26+ continued processing: set iosContinuedProcessingTitle (optional iosContinuedProcessingSubtitle). Add $(PRODUCT_BUNDLE_IDENTIFIER).CapacitorDownloader.continuedProcessing.* to BGTaskSchedulerPermittedIdentifiers in Info.plist. If the system does not launch the task within a few seconds, the plugin falls back to the background URLSession. If the continued processing task expires, the transfer is cancelled with downloadFailed and is not resumed automatically on relaunch.
Android OkHttp notifications: default notification: 'completed' matches 8.7.0. Set notification: 'progress' to opt in to ongoing progress and an optional dataSync foreground service (plugin minSdk 24; Android 12+ may block background service starts; Android 15 limits dataSync time). If the foreground service cannot start, the download continues and the progress notification still shows. The manifest merges FOREGROUND_SERVICE, FOREGROUND_SERVICE_DATA_SYNC, and POST_NOTIFICATIONS; request POST_NOTIFICATIONS at runtime on Android 13+ when you use 'progress'.
import { Capacitor } from '@capacitor/core';import { CapacitorDownloader } from '@capgo/capacitor-downloader';
if (Capacitor.getPlatform() === 'ios') { await CapacitorDownloader.download({ id: 'offline-pack', url: 'https://cdn.example.com/large-pack.zip', destination: 'private/offline/large-pack.zip', iosContinuedProcessingTitle: 'Offline pack', downloadCompletedNotificationText: 'Pack is ready', });} else { await CapacitorDownloader.download({ id: 'offline-pack', url: 'https://cdn.example.com/large-pack.zip', destination: 'files/offline/large-pack.zip', androidHttpEngine: 'auto', notification: 'progress', downloadCompletedNotificationText: 'Pack is ready', });}See also the plugin repository README.
Multi-file batch downloads
Section titled “Multi-file batch downloads”Available since 8.7.0 on iOS and Android (not on Web; download() is not implemented there). Install @capgo/capacitor-downloader at 8.7.0 or newer (see Install), then pass DownloadBatchOptions (files, no top-level url/destination) to download(). Do not mix single-file fields with files; the plugin rejects url and files together at runtime. Up to 32 transfers share one batch id. Shared options such as headers, network, priority, and notification apply to every entry.
Plugin change: capacitor-downloader#107.
On iOS, batch stop() deletes paths recorded via recordMovedDestination only while the plugin still tracks that batch (running, paused, or restored after relaunch). Once the batch succeeds, fails, or is stopped, a later stop({ id }) deletes nothing; files from an older generation of the same id are never touched, and iOS rejects with Task not found.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
const batchId = 'update-bundle';
const progressListener = await CapacitorDownloader.addListener('downloadProgress', (event) => { if (event.id !== batchId) { return; } if (event.fileIndex != null) { console.log(`file ${event.fileIndex} ${event.fileProgress}, overall ${event.progress}`); }});
const completedListener = await CapacitorDownloader.addListener('downloadCompleted', (event) => { if (event.id === batchId) { console.log('batch done'); }});
const failedListener = await CapacitorDownloader.addListener('downloadFailed', (error) => { if (error.id === batchId) { const which = error.fileIndex != null ? `file ${error.fileIndex}` : 'batch'; console.log(`${which} failed: ${error.error}`); }});
await CapacitorDownloader.download({ id: batchId, files: [ { url: 'https://example.com/a.zip', destination: 'updates/a.zip' }, { url: 'https://example.com/b.zip', destination: 'updates/b.zip' }, ], notification: 'hidden',});download() resolves after the batch is enqueued, not when every file finishes. Listen for downloadProgress, downloadCompleted, and downloadFailed as shown above. For batches, progress and fileProgress use the same 0 to 1 scale as DownloadTask.progress and single-file downloads. downloadProgress may include fileIndex (0-based) alongside those fields. downloadCompleted fires once when every file succeeds. downloadFailed fires when any file in the batch fails; the payload may include optional fileIndex. Any failure cancels the remaining transfers. Files that already finished successfully stay on disk on both Android and iOS (Android stops tracking completed children without calling DownloadManager.remove on them).
Example: cancel a batch
Section titled “Example: cancel a batch”Call stop() from a user action (for example a Cancel button), not immediately after download():
await CapacitorDownloader.stop({ id: 'update-bundle' });stop() on a batch id: On iOS, deletes paths recorded via recordMovedDestination only while the batch is still tracked by the plugin (running, paused, or restored after relaunch), including files that finished before that stop(). Batch failure alone does not delete those paths; only stop() removes them while the batch is tracked. Once the batch succeeds, fails, or is stopped, a later stop({ id }) deletes nothing; files from an older generation of the same id are never touched. The plugin rejects that later call with Task not found because the batch record is removed after success, failure, or stop(). Delete leftover files in your app after a failed batch when you want them removed. On Android, removes active DownloadManager entries for in-flight children while the batch is tracked; finished children stay on disk (completed batch files, including files finished before stop()).
Batch platform notes
Section titled “Batch platform notes”- Android engine: on Android, batches use DownloadManager only. Each file uses the same
androidHttpEnginedestination rules as a single download ('auto'can apply extended roots).download()rejects before enqueue if any file would use OkHttp (for examplecache/...orfiles/...with'okhttp', or'auto'when that path selects OkHttp). - Pause and resume: iOS supports
pause()andresume()on the batchid. Android rejectspause()andresume()for every download, including single downloads and batches (usestop()). - Process death: on Android, batch state is memory-only and is lost when the process is killed (DownloadManager work may still finish, but the plugin does not rebuild batch progress). On iOS, batch metadata is persisted in
DownloadBatchStore(UserDefaults) and restored when the plugin initializes (DownloadBatchCoordinator). - Partial success on failure: when one file fails, remaining transfers are cancelled; files that finished before the failure remain on disk on Android and iOS.
- iOS batch
stop(): deletesrecordMovedDestinationpaths only while the batch is still tracked (running, paused, or restored after relaunch). After the batch succeeds, fails, or is stopped, a laterstop({ id })deletes nothing; older generations of the same id are never touched, and iOS rejects withTask not found.
Example: completion notification
Section titled “Example: completion notification”When the app may be in the background, set downloadCompletedNotificationText to alert the user after a successful download. The plugin shows a system notification only when notification permission is granted. The plugin manifest already merges POST_NOTIFICATIONS on Android, so on Android 13 and later your app only needs to request it at runtime; on iOS request notification authorization before the download finishes. Tapping the notification reopens the app. On Android, the completion alert is still posted while your app is in the foreground. On iOS, a notification that arrives in the foreground is shown only if your app’s UNUserNotificationCenter delegate presents it, so without a notifications plugin it is usually silent and downloadCompleted events are the reliable signal there.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
await CapacitorDownloader.download({ id: 'offline-pack', url: 'https://cdn.example.com/large-pack.zip', destination: 'downloads/offline-pack.zip', downloadCompletedNotificationText: 'Your pack is ready', notification: 'hidden', // Android: rely on plugin events and the completion alert});On Android, pair notification: 'hidden' with downloadCompletedNotificationText when you do not want DownloadManager progress notifications but still want a completion alert. hidden is quiet for in-progress DownloadManager UI only. downloadCompletedNotificationText can still post a completion notification on success. If Android ends the app process before the download completes, the completion alert is not shown, and hidden also suppresses the DownloadManager completion notification.
Android DownloadManager notification labels
Section titled “Android DownloadManager notification labels”Available since 8.6.0. On Android, when the plugin uses the system DownloadManager (androidHttpEngine omitted, 'auto' for an external-files destination, or 'downloadManager'), you can set title and description on download() to control the text on the in-progress DownloadManager notification.
- Android DownloadManager: non-empty
titleanddescriptionare passed toDownloadManager.Request. Empty or omitted values keep the platform default (the title often falls back to the destination file name). - Android OkHttp: both fields are ignored. Use
downloadProgresslisteners and optionaldownloadCompletedNotificationTextinstead. - iOS: both fields are ignored. iOS does not show a DownloadManager-style progress notification; use
downloadProgressand optionaldownloadCompletedNotificationText. - Web: not supported.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
await CapacitorDownloader.download({ id: 'region-pack', url: 'https://cdn.example.com/maps/europe.zip', destination: 'downloads/europe.zip', notification: 'progress', title: 'Offline maps', description: 'Downloading Europe region pack',});Related plugin change: capacitor-downloader#114.
Example: pause and resume
Section titled “Example: pause and resume”iOS supports pause and resume for single downloads and batch ids. Android rejects pause() and resume() for every download, including batches.
await CapacitorDownloader.pause({ id: 'offline-pack' });await CapacitorDownloader.resume({ id: 'offline-pack' });Example: inspect finished file
Section titled “Example: inspect finished file”import { Capacitor } from '@capacitor/core';import { Directory, Filesystem } from '@capacitor/filesystem';
const relativePath = 'downloads/offline-pack.zip';const path = Capacitor.getPlatform() === 'ios' ? (await Filesystem.getUri({ directory: Directory.Documents, path: relativePath })).uri : relativePath;
const info = await CapacitorDownloader.getFileInfo({ path });Android OkHttp engine
Section titled “Android OkHttp engine”androidHttpEngine is available since 8.5.0. Omit androidHttpEngine to keep the same default as releases before 8.5.0: DownloadManager with legacy destination paths, including cache/... and files/... under app external files.
Set 'auto' or 'okhttp' only when you want app-private roots (cache/..., files/... under internal storage). With androidHttpEngine: 'auto', DownloadManager is used for public-downloads/... and for other relative paths under app external files. If app external files storage is unavailable, those other relative paths fall back to app-private internal storage and auto selects OkHttp. 'okhttp' rejects public-downloads/... paths.
If you already use cache/... or files/... strings without androidHttpEngine, your files stay on app external storage. Opt in with 'auto' or 'okhttp' only when you intend to move those paths to internal cache or files dirs.
Choose androidHttpEngine
Section titled “Choose androidHttpEngine”| Value | When to use |
|---|---|
| Omitted | When omitted, same as releases before 8.5.0: DownloadManager only, legacy destination paths for every relative string (including existing cache/... and files/... under app external files). Absolute and file:// paths keep the 8.4.x behavior (nested under app external files). With androidHttpEngine 'auto' or 'okhttp', absolute and file:// paths are used as given. |
'auto' | OkHttp for cache/..., files/..., and absolute paths under internal cache/data/files; DownloadManager for other relative paths and public-downloads/.... If app external files storage is unavailable, other relative paths fall back to internal files storage and auto selects OkHttp. |
'okhttp' | Force OkHttp for app-private and internal destinations (sensitive offline packs, internal-only files). Requests to public-downloads/... are rejected. Transfers run in the app process and do not continue after the process is killed. |
'downloadManager' | Force system DownloadManager with legacy destination paths (same as omitting the option). |
Android destination prefixes
Section titled “Android destination prefixes”| Prefix | Resolves to when androidHttpEngine is omitted (releases before 8.5.0) | Resolves to with 'auto' or 'okhttp' | auto engine |
|---|---|---|---|
cache/... | App external files (.../cache/...) | App cache directory | OkHttp |
files/... | App external files (.../files/...) | App-private files directory | OkHttp |
public-downloads/... | App external files under public-downloads/... | Public Downloads folder | DownloadManager ('okhttp' rejects this prefix) |
| Other relative paths | App external files directory | App external files (or internal fallback) | DownloadManager, or OkHttp when the internal fallback is used |
Example: private offline pack
Section titled “Example: private offline pack”import { CapacitorDownloader } from '@capgo/capacitor-downloader';
const progress = await CapacitorDownloader.addListener('downloadProgress', (event) => { if (event.id === 'offline-pack') { console.log(event.progress); }});
await CapacitorDownloader.download({ id: 'offline-pack', url: 'https://cdn.example.com/pack.zip', destination: 'files/offline/pack.zip', androidHttpEngine: 'auto', notification: 'hidden',});OkHttp runs inside the app process. If Android kills that process, the download does not continue the way a DownloadManager transfer does. Internal cache/... and files/... destinations need 'auto' or 'okhttp'. For public-downloads/..., set 'auto' when the transfer must outlive the app process. Omitting androidHttpEngine or setting 'downloadManager' saves these files under app external files, not the public Downloads folder. For external-files paths, omit androidHttpEngine or set 'auto' / 'downloadManager' when the transfer must outlive the app process. Do not set 'okhttp' for public-downloads/...; that request is rejected.
Notifications with OkHttp
Section titled “Notifications with OkHttp”'completed'(default): same as 8.7.0. No ongoing notification and no foreground service. OkHttp still posts one “Download complete” notification on success, as in 8.7.0. With both an in-app event anddownloadCompletedNotificationText, a second completion notification can appear.POST_NOTIFICATIONSmay be required when you use'progress'or this completion notification path on Android 13 and later. UsedownloadProgress/downloadCompletedand optionaldownloadCompletedNotificationText.'hidden': no OkHttp progress UI and no default “Download complete” notification; plugin events still fire. OnlydownloadCompletedNotificationTextcan post a completion notification.'progress': opt-in ongoing progress notification while the transfer runs plus an optionaldataSyncforeground service. The notification is removed when the transfer finishes (success or failure). If the foreground service cannot start, the download still runs and the progress notification still shows. On Android 13 and later, requestPOST_NOTIFICATIONSat runtime when you use'progress'.
DownloadManager destinations continue to support 'completed', 'progress', and 'hidden' as before.
OkHttp limits
Section titled “OkHttp limits”- At most 4 OkHttp transfers run at the same time. Additional OkHttp downloads wait until a slot is free.
- HTTP 206 Partial Content is not supported. The OkHttp path fails that response (this plugin does not resume through range requests).
- An HTTPS to HTTP redirect is not followed; the download fails.
- With
network: 'wifi-only', the transfer is bound to Wi-Fi and fails if Wi-Fi drops, with no cellular fallback. stop()cancels an in-flight OkHttp transfer and deletes the destination file, including when the transfer has already finished.
Common pitfalls
Section titled “Common pitfalls”- Storage destination: pick a
destinationyour app can read on each platform. On Android, usecache/orfiles/prefixes for app-private OkHttp downloads withandroidHttpEngine'auto'or'okhttp'. - Background: downloads run on iOS and Android in the background. On Android, DownloadManager can continue after the app process is killed. OkHttp runs in the app process, so a download may stop if Android kills that process. On Web,
download()is not implemented; use a browser download flow instead. - Status: use
checkStatuswhile the app process is still alive. On iOS, task IDs are not restored after relaunch.
API Overview
Section titled “API Overview”download
Section titled “download”Start a single-file download (DownloadOptions) or a multi-file batch (DownloadBatchOptions with files, since 8.7.0). Signature: download(options: DownloadOptions | DownloadBatchOptions).
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
const task = await CapacitorDownloader.download({ id: 'my-download', url: 'https://example.com/file.pdf', destination: 'downloads/file.pdf'});Batch (at most 32 files):
await CapacitorDownloader.download({ id: 'update-bundle', files: [ { url: 'https://example.com/a.zip', destination: 'updates/a.zip' }, { url: 'https://example.com/b.zip', destination: 'updates/b.zip' }, ],});Pause an active download. Download can be resumed later from the same position.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
await CapacitorDownloader.pause({ id: 'id-123' });resume
Section titled “resume”Resume a paused download. Continues from where it was paused.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
await CapacitorDownloader.resume({ id: 'id-123' });Stop and cancel a download permanently.
Batch id on iOS: Deletes each path recorded by recordMovedDestination only while the batch is still tracked by the plugin (running, paused, or restored after relaunch). Batch failure alone does not delete finished files while the batch is tracked; only stop() removes recorded paths. Once the batch succeeds, fails, or is stopped, a later stop({ id }) deletes nothing; files from an older generation of the same id are never touched, and the plugin rejects with Task not found.
Batch id on Android: Removes DownloadManager work for non-finished children while the batch is tracked. Completed batch files stay on disk (marked complete or STATUS_SUCCESSFUL), including files finished before stop(). After the batch succeeds, fails, or is stopped, a later stop({ id }) deletes nothing on completed files; remove leftovers in your app when needed.
Single downloads: Cancels the transfer. Single-file OkHttp downloads on Android still delete the destination file when stopped, including after finish. Other platform cleanup depends on the OS.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
await CapacitorDownloader.stop({ id: 'id-123' });checkStatus
Section titled “checkStatus”Check the current status of a download.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
const result = await CapacitorDownloader.checkStatus({ id: 'id-123' });console.log(result);getFileInfo
Section titled “getFileInfo”Get information about a downloaded file.
import { CapacitorDownloader } from '@capgo/capacitor-downloader';
const result = await CapacitorDownloader.getFileInfo({ path: 'path/to/file' });console.log(result);Type Reference
Section titled “Type Reference”DownloadFileSpec
Section titled “DownloadFileSpec”One file inside a batch (files array, since 8.7.0). On Android, destination follows the same rules as a single download for the batch androidHttpEngine value; the batch is rejected only when a file would use OkHttp.
export interface DownloadFileSpec { url: string; destination: string;}DownloadOptions
Section titled “DownloadOptions”Single-file download options (url and destination required). Use files on DownloadBatchOptions instead; do not pass files here.
export interface DownloadOptions { /** Unique identifier for this download task */ id: string; /** URL of the file to download */ url: string; /** Local file path where the download will be saved */ destination: string; /** Optional HTTP headers to include in the request */ headers?: { [key: string]: string }; /** Network type requirement for download */ network?: 'cellular' | 'wifi-only'; /** Download priority level */ priority?: 'high' | 'normal' | 'low'; /** * Android DownloadManager notification visibility. Defaults to `completed` when omitted. * - `completed`: shows a notification during the download and after it completes. * - `progress`: shows a notification only during the download. * - `hidden`: shows no DownloadManager notification. */ notification?: 'completed' | 'progress' | 'hidden'; /** * Android DownloadManager progress notification title (since 8.6.0). * Ignored on iOS, Web, and the OkHttp Android path. */ title?: string; /** * Android DownloadManager progress notification description (since 8.6.0). * Ignored on iOS, Web, and the OkHttp Android path. */ description?: string; /** * Android HTTP stack: omitted, `'auto'`, `'okhttp'`, or `'downloadManager'` (since 8.5.0). * Ignored on iOS and Web. */ androidHttpEngine?: 'auto' | 'okhttp' | 'downloadManager'; /** * Optional localized text for a system notification after a successful download. * Requires notification permission on iOS and Android. */ downloadCompletedNotificationText?: string; /** * iOS 26 and later: opt in to a BGContinuedProcessingTask (since 8.8.0). */ iosContinuedProcessingTitle?: string; /** * Optional subtitle for the iOS 26 continued-processing task (since 8.8.0). */ iosContinuedProcessingSubtitle?: string; /** * Multi-file batches use `files` on DownloadBatchOptions instead (since 8.7.0). */ files?: never;}DownloadBatchOptions
Section titled “DownloadBatchOptions”Multi-file batch (since 8.7.0, at most 32 files). Uses files only; url and destination are not allowed at the top level. Passing url and files together is rejected at runtime. On Android, batches use DownloadManager only; download() rejects if any file would use OkHttp. When one file fails, remaining transfers are cancelled; files that already finished successfully stay on disk. stop({ id }) on a batch id: On iOS, deletes every path stored via recordMovedDestination only while the batch is still tracked (running, paused, or restored after relaunch). Once the batch succeeds, fails, or is stopped, a later stop({ id }) deletes nothing; files from an older generation of the same id are never touched, and iOS rejects with Task not found. On Android, removes active DownloadManager entries for in-flight children while tracked; finished children stay on disk.
export interface DownloadBatchOptions { /** Unique identifier for this batch (shared by every file in `files`) */ id: string; /** Up to 32 files (DOWNLOAD_BATCH_MAX_FILES) */ files: DownloadFileSpec[]; url?: never; destination?: never; headers?: { [key: string]: string }; network?: 'cellular' | 'wifi-only'; priority?: 'high' | 'normal' | 'low'; notification?: 'completed' | 'progress' | 'hidden'; title?: string; description?: string; /** * Same destination rules as single downloads; rejected if any file would use OkHttp on Android. */ androidHttpEngine?: 'auto' | 'okhttp' | 'downloadManager'; downloadCompletedNotificationText?: string;}Call with either type: download(options: DownloadOptions | DownloadBatchOptions).
Events
Section titled “Events”For batches, downloadProgress uses progress and fileProgress from 0 to 1 (same scale as DownloadTask.progress), and may include optional fileIndex. downloadFailed includes { id, error, fileIndex? }; for batches, fileIndex is set when the failing file is known.
DownloadTask
Section titled “DownloadTask”Represents the current state and progress of a download task.
export interface DownloadTask { /** Unique identifier for the download task */ id: string; /** Download progress from 0 to 1 */ progress: number; /** Current state of the download */ state: 'PENDING' | 'RUNNING' | 'PAUSED' | 'DONE' | 'ERROR';}Source Of Truth
Section titled “Source Of Truth”This page is generated from the plugin’s src/definitions.ts. Re-run the sync when the public API changes upstream.
Keep going from Getting Started
Section titled “Keep going from Getting Started”If you are using Getting Started to plan dashboard and API operations, connect it with Using @capgo/capacitor-downloader for the native capability in Using @capgo/capacitor-downloader, API Overview for the implementation detail in API Overview, Introduction for the implementation detail in Introduction, API Keys for the implementation detail in API Keys, and Devices for the implementation detail in Devices.