Hello, I have a question. Currently, our product requires security reinforcement (protection) for the app,
including both Android and iOS. However, after applying the protection tool, we are no longer able to perform hot updates on the application.
Below is the log output:
[flutter/shell/common/shorebird/shorebird.cc(247)] Shorebird updater: no active patch.
updater::updater: [shorebird] Reporting launch start.
[flutter/shell/common/shorebird/shorebird.cc(270)] Starting Shorebird update
updater::network: [shorebird] Sending patch check request: PatchCheckRequest { app_id: "2d9142b3-fd3f-4552-9451-fe835321435e", channel: "stable", release_version: "1.0.0+1", platform: "android", arch: "aarch64" }
updater::updater: [shorebird] Patch check response: PatchCheckResponse { patch_available: true, patch: Some(Patch { number: 1, hash: "e740dc6ad1ffa4a098110df684b88edda11fc28129f8a35b36de633101b20672", download_url: "https://cdn.shorebird.cloud/.../dlc.vmcode", hash_signature: None }), rolled_back_patch_numbers: Some([]) }
updater::network: [shorebird] Downloading patch from: https://cdn.shorebird.cloud/.../dlc.vmcode
updater::network: [shorebird] Writing patch to: "/data/user/0/com.example.my_shorebird_app/code_cache/shorebird_updater/downloads/1"
updater::network: [shorebird] Wrote patch to: "/data/user/0/com.example.my_shorebird_app/code_cache/shorebird_updater/downloads/1"
updater::updater: [shorebird] Update failed: Library not found in APK
updater::updater: [shorebird] Update thread finished with status: Update had error
[INFO:flutter/shell/common/shorebird/shorebird.cc(247)] Shorebird updater: no active patch.
updater::updater: [shorebird] Reporting launch start.
[INFO:flutter/shell/common/shorebird/shorebird.cc(270)] Starting Shorebird update
Opening an oat file without a class loader. Are you using the deprecated DexFile APIs?
OpenDexFilesFromOat: open oat file failed and fallback to load dex file from apk, package_name = com.example.my_shorebird_app
#Patch Update failed after applying the security protection tool to the application.
1 messages · Page 1 of 1 (latest)
Open an issue on GitHub, and make sure to mention which tool are you using
Probably the protection tool has change dthe binary, thus making patchs fail to apply. Although I don't see a failure in that log.