stuartmorgan-g

> Actually I found out today that if I use the launch(url_here) rather than launchUrl() it opens and asks to download or open. By default I believe `launch` will use...

The most likely explanation based on the repro description is that we need an extra delegate wired up for the in-app webview to deal with unhandled content (e.g., to prompt...

> This is not the experience I was looking for. I'm looking for something similar to iOS. You can't get the same experience on Android, because Android webview doesn't display...

See https://github.com/flutter/flutter/issues/105205#issuecomment-1248938994. You just need to specify the correct launch mode to the current API, you don't need to use the deprecated API (which defaulted to that launch mode on...

@BrendanBasson4 This issue is about nothing happening when using the in-app webview. If you are opening in an external browser and it opened (which is did if it's downloading), then...

@TimAlber Please file a new issue; this is about the in-app webview move.

Anyone affected by this issue can `flutter pub upgrade` to pick up `url_launcher_android` 6.1.0 or later, and in [supported configurations](https://github.com/flutter/flutter/issues/18589#issuecomment-1701648535) in-app mode will use [Custom Tabs](https://developer.chrome.com/docs/android/custom-tabs/) instead of the previous...

@BuzzBumbleBee The next step here would be to update the design document. Currently there's a comment thread where I explained that what is proposed there isn't something we would move...

> Is it because background service spawns its own flutter engine(and consequently a background isolate?). It is because it spawns its own Flutter engine, with its own new **root** isolate....

@heynext Are you still planning on updating this PR based on the feedback above?