Tags: jiacai2050/flauth
Tags
Fix Windows release build failure on latest MSVC toolchain (#28) The Windows release job started failing on `windows-latest` during `flutter build windows`. The breakage came from transitive Windows plugins (`local_auth_windows`, `permission_handler_windows`) hitting MSVC's new hard error for deprecated `<experimental/coroutine>` usage. - **Root cause** - Current GitHub Actions Windows runners ship an MSVC/STL version that rejects deprecated experimental coroutine support used by plugin native code. - The later `Compress-Archive` failure in the job was secondary; the build output was never produced. - **Change** - Add a top-level Windows compile definition in `windows/CMakeLists.txt`: - `_SILENCE_EXPERIMENTAL_COROUTINE_DEPRECATION_WARNINGS` - This applies to plugin subprojects built through the app's CMake graph, avoiding direct edits to generated plugin files or dependency sources. - **Why here** - The failing plugins are added as CMake subdirectories from Flutter's generated Windows plugin wiring, so a single definition at the app level propagates to those targets. ```cmake # windows/CMakeLists.txt add_definitions(-DUNICODE -D_UNICODE) add_compile_definitions(_SILENCE_EXPERIMENTAL_COROUTINE_DEPRECATION_WARNINGS) ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
chore(workflow): Remove build id in jni CMakeLists for release This change disables build id generation in jni dependency to reduce binary size and improve reproducibility. Previously, build ids were included in release artifacts, which could cause unnecessary differences between builds. This update ensures more consistent output for release workflows.