-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Add flags to make App.framework work in app extension #123618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
cyanglaz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
What does App.framework do? (As opposed to flutter.framework)
Flutter.framework is the precompiled engine we ship in the SDK. App.framework is the app's compiled dart code. In debug JIT mode the App.framework/App (35KB) is a dummy binary that satisfies the structure of a framework and only contains:
the actual compiled binary is at App.framework/flutter_assets/kernel_blob.bin (39MB) plus the isolate_snapshot_data (5MB). In release AOT the code is actually compiled to App.framework/App (8.4MB) and there is no kernel_blob.bin or isolate_snapshot_data. |
When linking or compiling App.framework for iOS or macOS add the
-fapplication-extensionflag which marks the executable as "safe" to use in an iOS or macOS app extension.Part of #16092
See https://flutter.dev/go/app-extensions.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.