Reid Baker

Closing this as stale and there are conflicts. Please re-open if progress can be made.

I am for this but I don't think we can just remove dependency locking as a feature in the framework.

What happens if you enable kill background activities? My gut is that this is intended android behavior you are seeing and not a flutter bug.

@PMARZV thank you for your comment this further makes me think this a quirk of the android system when you have an activity with a transparent background that is not...

I cannot add reviewers but this looks like a good update to * The version of kotlin * Targeting compileSdkVersion 33 which will be required for all new apps soon...

Would you be willing to share the plugins you use? I am wondering if you have webview?

@zanderso do you know where we have documentation around the behavior of multiple engines and what should or should not be expected?

Thank you for following up with an explanation. Did you not get a compilation error when `SplashScreenDrawable` was removed?

Fyi there is documentation here https://docs.flutter.dev/platform-integration/android/splash-screen#android-12 that says do not reference Splashscreen in your manifest. And a migration guide here https://docs.flutter.dev/release/breaking-changes/splash-screen-migration

Actually given this has been deprecated for so long I am going to go ahead and close this issue.