canLaunchUrl in Link, to avoid issues on platforms where canLaunchUrl is unreliable or requires permissions.prefer_relative_imports.README.md examples to the code-excerpt system.canLaunchUrl recommendations.launchUrl and canLaunchUrl APIs; launch and canLaunch are now deprecated. These new APIs:String URL argument with a Uri, to prevent common issues with providing invalid URL strings.forceSafariVC and forceWebView with LaunchMode, which makes the API platform-neutral, and standardizes the default behavior between Android and iOS.WebViewConfiguration object. The default behavior for JavaScript and DOM storage is now enabled rather than disabled.closeWebView in favor of closeInAppWebView to clarify that it is specific to the in-app web view launch option.default_package registration for Windows, macOS, and Linux.file scheme usage.Uri class link to SDK documentation.meta.canLaunch should be used.canLaunch.Uri query encoding bug.url_launcher_platform_interface 2.0.3. This fixes an issue where 6.0.5 could fail to compile in some projects due to internal changes in that version that were not compatible with earlier versions of url_launcher_platform_interface.Link widget to the example app.True on iOS when the url was loaded successfully.RaisedButton and FlatButton widgets.README.mdtestWidgets instead of test.launch method can’t find an app to open the provided url. It will now throw a clear Dart PlatformException.shouldOverrideUrlLoading method on Android of the FlutterWebChromeClient class.headers parameter.false if package visibility (Android API 30) is not managed correctly.shouldOverrideUrlLoading method on Android.platform_interface package that adds the webOnlyWindowName parameter.previousAutomaticSystemUiAdjustment in launch method.web to the example app.getFlutterEngine call on Android.plugin_platform_interface.package:url_launcher_platform_interface to get the platform-specific implementation.build.gradle to support apps that has not been migrated to AndroidX.gradle.properties.headers field to enable headers in the Android implementation.enableDomStorage field to launch to enable DOM storage in Android WebView.invokeMethod calls.closeWebView failure on iOS.Breaking change. Migrate from the deprecated original Android Support Library to AndroidX. This shouldn‘t result in any functional changes, but it requires any Android apps using this plugin to also migrate if they’re using the original support library.
This was originally incorrectly pushed in the 4.2.0 update.
5.0.0 instead. That's the correctly versioned new push of 4.2.0.launch to use async and await, fixed the incorrect return value by launch method.BAD. This was a breaking change that was incorrectly published on a minor version upgrade, should never have happened. Reverted by 4.2.0+3.
Breaking change. Migrate from the deprecated original Android Support Library to AndroidX. This shouldn‘t result in any functional changes, but it requires any Android apps using this plugin to also migrate if they’re using the original support library.
universalLinksOnly setting.launch to return Future<bool>.launch now assert activity not null and using activity to startActivity.WebViewActivity has leaked IntentReceiver for Android.closeWebView function to programmatically close the current WebView.launch to enable javascript in Android WebView.launch to set iOS status bar brightness.launch now returns Future<void> instead of Future<Null>.canLaunch method.launch to a top-level method instead of a static method in a class.