[quick_actions_ios] Needs to adopt UIScene lifecycle

After adopting UIScene lifecycle in Flutter apps, quick_actions is running into errors:

This is most likely due to it relying on application lifecycle events, which are no longer called.

For example,

  public func application(
    _ application: UIApplication, performActionFor shortcutItem: UIApplicationShortcutItem,
    completionHandler: @escaping (Bool) -> Void
  ) -> Bool {
    handleShortcut(shortcutItem.type)
    return true
  }

https://github.com/flutter/packages/blob/c3c4c5a01ab077990b0aae509090d987a660b88e/packages/quick_actions/quick_actions_ios/ios/quick_actions_ios/Sources/quick_actions_ios/QuickActionsPlugin.swift#L39-L45

Apple's docs state

This method is not called for scene-based apps. If you have a scene-based app, implement windowScene(_:performActionFor:completionHandler:) in your scene delegate instead.

https://developer.apple.com/documentation/uikit/uiapplicationdelegate/application(_:performactionfor:completionhandler:)

Test failures:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8712791415816897953/+/u/Run_package_tests/native_test/stdout

This may be blocked by: #130445

This is probably what's causing #169928

This may be blocked by: #130445

From initial skimming of the docs, it looks like UISceneDelegate is a singleton (rather than something arbitrary objects can subscribe to), in which case this would definitely be blocked by building a multiplexing API at the plugin layer. I may have missed alternate non-singleton APIs though.

This issue is marked P1 but has had no recent status updates.

The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

On our app we are using class SceneDelegate: UIResponder and extension SceneDelegate: UIWindowSceneDelegate .
As far as I understand, quick_action do not work on this setup.
Can someone share the right solution for this use case?

Based on my understanding all prerequisites have been done, so this issue could finally be fixed.

Please see this PR: #175866

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

[quick_actions_ios] UIScene Migration (flutter#11047)

Navigation Menu

Repository navigation

[quick_actions_ios] Needs to adopt UIScene lifecycle #170179

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[quick_actions_ios] Needs to adopt UIScene lifecycle #170179

Description

Activity

vashworth commented on Jun 6, 2025

stuartmorgan-g commented on Jun 10, 2025

flutter-triage-bot commented on Oct 17, 2025

itaishalom commented on Feb 2, 2026

itaishalom commented on Feb 3, 2026

SrAdam commented on Feb 3, 2026

SrAdam commented on Feb 9, 2026

github-actions commented on Apr 10, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions