- Updated AAR releaser test to use ShorebirdProcess.defaultFlutterStorageBaseUrl. - Changed macOS releaser test to reference a new troubleshooting URL. - Enhanced shorebird_yaml_test with deserialization for AOT patch metadata. - Modified network_checker_test to check self-hosted URLs from ShorebirdEnv. - Added tests for artifact paths in shorebird_artifacts_test. - Updated shorebird_cli_command_runner_test to reflect new repository URL. - Improved shorebird_env_test with additional tests for shorebirdRoot and engine revision fallback. - Adjusted shorebird_flutter_test to use environment variables for Flutter Git URL. - Updated shorebird_process_test to utilize default Flutter storage URL. - Enhanced shorebird_validator_test to link to the default hosted URL. - Updated shorebird_web_console_test to use the configured hosted URL. - Refactored code_push_client to use default hosted URL for API requests. - Updated README and generation scripts for the code_push_protocol package to reflect new OpenAPI spec source. - Modified shared.sh to allow configurable Flutter repository and storage URLs. Signed-off-by: Tony <tonylu@tony-cloud.com>
Code Push Troubleshooting
The open replacement uses a self-hosted server and a local artifact mirror by default. Check these values first when release or patch commands fail:
SHOREBIRD_HOSTED_URL, defaulthttp://localhost:8080SHOREBIRD_AUTH_URL, defaulthttp://localhost:8080/authSHOREBIRD_ARTIFACT_BASE_URL, defaulthttp://localhost:8080/artifactsSHOREBIRD_FLUTTER_STORAGE_BASE_URL, defaulthttp://localhost:8080/download.flutter.io
Unsupported Class File Major Version 65
Use the Java version expected by the Flutter and Android Gradle Plugin version
in your project. If the Gradle build fails outside Shorebird, resolve that
plain flutter build failure before retrying the Shorebird command.
Can't Run My App In VS Code
Run the app with the generated Flutter SDK and engine artifacts from this workspace. Mixing a release built by this workspace with a stock Flutter tool can make debug and launch behavior confusing.
Your App Contains Asset Changes Warning When Creating A Patch
Asset changes are not part of a Dart code patch. Create a new release when assets, native resources, icons, or bundled files change.
Your App Contains Native Changes Warning When Creating A Patch Even Though You Haven't Changed Swiftobjective Ckotlinjava Code
Native build outputs can change when project files, plugins, build settings, or generated native artifacts change. Compare the release and patch build inputs, then create a new release if native outputs are expected to differ.