WebView dependency and upgrade notes

Reference for the files delivered in Main_File. Documentation updated 22 September 2026. Examples use fictional IDs and balances; replace them with values from your installation.

Current package: hosted plugin, no vendored override

The reviewed buyer package Main_File/flutter_app does not contain local_plugins/webview_flutter_android and does not declare its path override. Its pubspec.yaml declares webview_flutter 4.10.0; its lockfile resolves webview_flutter_android 4.12.0 from pub.dev. Therefore the previous instruction to keep an included local fork was inaccurate for these delivered files.

The buyer source includes GamePix games using the hosted WebView plugin. GamePix does not require the historical custom bridge or development fork. Keep the buyer package's hosted dependency resolution unless you intentionally perform and test a separate dependency upgrade.

Historical fork: why it existed and what it preserved

A local development copy remains outside the buyer package. Its pubspec identifies webview_flutter_android 3.12.0. Source inspection shows a concrete custom bridge for an earlier embedded integration; the broad old claim about unspecified media/lifecycle fixes did not explain it.

• WebViewHostApiImpl.loadUrl called setNativeBridge, registering a JavaScript interface named NativeBridge.
• The interface exposed getConfig, destroy, reportGameSize, gameRecharge, gameLoaded and sendGameAction. Each forwarded a string through a main-thread Handler to BSEventChannel. The bridge's destroy method forwarded a message; it did not itself destroy the native WebView.
• BSEventChannel registered the EventChannel baishunChannel, managed its event sink on listen/cancel, and forwarded messages to Dart.
• WebViewFlutterPlugin registered that channel on engine attachment and detached its stream handler on engine removal.

These facts explain the historical fork's observable custom behavior. They are not instructions to restore the removed integration. No separately verified patch history establishing custom media playback fixes was supplied, so this guide does not claim them.

Future Flutter/plugin upgrades

1. Start from the delivered flutter_app, retain a copy of pubspec.yaml/pubspec.lock and record Flutter, Dart, Gradle, Android SDK and WebView versions.
2. Update dependencies in an isolated branch. Review the official plugin changelog/API changes and the new resolved lockfile; do not copy the old 3.12.0 Android plugin over a newer generated platform implementation.
3. Confirm flutter pub deps uses the hosted plugin and that no path override or baishunChannel/NativeBridge consumer has been inadvertently reintroduced.
4. Run flutter analyze and the relevant build. Test the GamePix catalogue/player using its device checklist, and the separate URL-launch paths: home banners, sign-in legal links and settings links. These use url_launcher in-app browser modes; they are not proof that the historical custom bridge exists.
5. On Android test open/close repeatedly, back navigation, rotation where enabled, app background/resume, external links, load failure/retry, keyboard input, and any retained media playback. Watch for blank surfaces, duplicate events and audio continuing after close. On iOS verify the equivalent retained web flows with the iOS implementation.
6. If a buyer independently develops a new custom bridge, explicitly design and test its API, origin restrictions, thread handoff and disposal. Do not assume upstream provides NativeBridge or baishunChannel. Such a custom bridge is outside the delivered GamePix integration.

Upgrade acceptance: Android release builds, GamePix and retained web links work on physical devices, no local fork is resolved, and room/navigation behavior remains unchanged. If a regression occurs, restore the previously tested lockfile and SDK configuration while investigating.