Merged
Conversation
Register FlutterSceneLifeCycleDelegate alongside the existing UIApplicationDelegate to handle LINE login callbacks when the host app adopts the UIScene-based lifecycle. Implements scene(_:openURLContexts:) and scene(_:continue:) which bridge URL handling to LoginManager, matching the existing application delegate pattern. Ref: #136 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Required for FlutterSceneLifeCycleDelegate and registrar.addSceneDelegate() API availability. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The protocol conformance must be explicitly declared for the compiler to accept the type passed to addSceneDelegate(). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Auto-migrated by Flutter 3.41 tooling: - Add UIApplicationSceneManifest to Info.plist - Update AppDelegate to use FlutterImplicitEngineDelegate - Bump iOS deployment target from 12.0 to 13.0
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
onevcat
force-pushed
the
feature/uiscene-lifecycle-support
branch
2 times, most recently
from
8f48813 to
be28033
Compare
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
FlutterSceneLifeCycleDelegatesupport to the iOS plugin, ensuring LINE login callbacks work correctly when the host app adopts UIScene-based lifecycle (required by Apple post-iOS 26)UIApplicationDelegateandFlutterSceneLifeCycleDelegatecallbacks, so it works with both migrated and non-migrated host appsFlutterSceneLifeCycleDelegateAPI availabilityDetails
Apple announced that apps built with the latest SDK will be required to use the UIScene lifecycle in the release following iOS 26. Flutter introduced
FlutterSceneLifeCycleDelegatein 3.38.0 to support this migration for plugins.The plugin's two URL handling methods (
application(_:open:options:)for URL schemes andapplication(_:continue:restorationHandler:)for universal links) will not be called once a host app migrates to UIScene. This PR adds the scene-based equivalents (scene(_:openURLContexts:)andscene(_:continue:)) that bridge URLs to LINE SDK'sLoginManagerusing the same caller-side bridging pattern recommended by LINE SDK Swift.No changes to LINE SDK Swift dependency are needed —
LoginManager.shared.application(.shared, open: url)accepts URLs regardless of how they were received.Closes #136
Test plan
flutter analyze— no new issuesflutter test— 7/7 passedflutter build ios) — successscene(_:openURLContexts:))application(_:open:options:), verified by disabling UIScene migration)🤖 Generated with Claude Code