đ Need Expert Help?
Stuck with a complex issue? Our expert team is here to help! Get personalized support, code reviews, and custom solutions tailored to your specific needs.
Here are some common issues you might encounter while using Capgo and how to resolve them.
đ Need Expert Help?
Stuck with a complex issue? Our expert team is here to help! Get personalized support, code reviews, and custom solutions tailored to your specific needs.
If your bundle upload fails, double check:
capacitor.config.ts
matches your app in the Capgo dashboardThe Capgo CLI provides some additional flags to help with common upload issues:
--tus
: Uses the tus resumable upload protocol for more reliable uploads of large bundles or on poor network connections. If your bundle is over 10MB or youâre on a spotty connection, consider using --tus
:
npx @capgo/cli@latest bundle upload --tus
--package-json
and --node-modules
: Tells Capgo where to find your root package.json
and node_modules
if your app uses a non-standard structure like a monorepo or npm workspace. Pass the path to the root package.json
and the --node_modules
path:
npx @capgo/cli@latest bundle upload --package-json=path/to/package.json --node_modules=path/to/node_modules
Capgo needs this information to correctly bundle your appâs dependencies.
You can combine these flags with other options like --channel
as needed. See the Capgo CLI docs for full details on the available upload options.
If youâre still having trouble with uploads, reach out to Capgo support for further assistance.
If youâre encountering issues with live updates, the Capgo debug command is a helpful tool for troubleshooting. To use it:
Run the following command in your project directory:
npx @capgo/cli@latest app debug
Launch your app on a device or emulator and perform the action that should trigger an update (e.g. reopening the app after uploading a new bundle).
Watch the output of the debug command. It will log information about the update process, including:
Use the debug logs to identify where the issue is occurring. For example:
CapacitorUpdater.notifyAppReady()
and that the app was fully closed and reopened.The debug command is especially useful for identifying issues with the update download and installation process. If the logs show the expected update version was found but not ultimately applied, focus your troubleshooting on the steps after the download.
In addition to the Capgo debug command, the native logs on Android and iOS can provide valuable troubleshooting information, especially for issues on the native side of the update process.
To access the Android logs:
Capgo
to find the SDK logsAlternatively, you can use the adb logcat
command and grep for Capgo
to filter the logs.
The Capgo SDK will log key events during the update process, such as:
Common Android-specific issues you might see in the logs include:
To access the iOS logs:
Capgo
to find the SDK logsYou can also use the log stream
command in the terminal and grep for Capgo
to filter the logs.
Similar to Android, the Capgo SDK will log key iOS-side events:
iOS-specific issues you might identify in the logs include:
On both platforms, the native logs provide a lower-level view into the update process, with more details on the native implementation. They are especially useful for identifying issues that occur outside of the Capgo JavaScript layer.
When troubleshooting a tricky live update problem, itâs a good idea to capture both the Capgo debug logs and the native logs for a comprehensive picture of whatâs happening. The two logs together will give you the best chance of identifying and resolving the issue.
If youâve uploaded a bundle but arenât seeing the changes on your device:
CapacitorUpdater.notifyAppReady()
in your app code as shown in the quickstartRefer to the deploying live updates guide for more details on the update process. If youâre still stuck, use the npx @capgo/cli@latest app debug
command and native logs to get more visibility into whatâs happening.
If youâre having trouble installing the Capgo SDK, make sure:
For issues with triggering Capgo uploads from your CI/CD pipeline:
See the CI/CD integration docs for more troubleshooting tips. You can also use the npx @capgo/cli@latest app debug
command to confirm if your CI/CD-triggered updates are being received by the app.