text stringlengths 1 474 |
|---|
<topic_end> |
<topic_start>Add macOS devtools for Flutter |
To choose the guide to add macOS devtools to your Flutter configuration, |
click the Getting Started path you followed. |
<topic_end> |
<topic_start>Building macOS apps with Flutter |
This page discusses considerations unique to building |
macOS apps with Flutter, including shell integration |
and distribution of macOS apps through the Apple Store.<topic_end> |
<topic_start> |
Integrating with macOS look and feel |
While you can use any visual style or theme you choose |
to build a macOS app, you might want to adapt your app |
to more fully align with the macOS look and feel. |
Flutter includes the Cupertino widget set, |
which provides a set of widgets for |
the current iOS design language. |
Many of these widgets, including sliders, |
switches and segmented controls, |
are also appropriate for use on macOS.Alternatively, you might find the macos_ui |
package a good fit for your needs. |
This package provides widgets and themes that |
implement the macOS design language, |
including a MacosWindow frame and scaffold, |
toolbars, pulldown and |
pop-up buttons, and modal dialogs.<topic_end> |
<topic_start> |
Building macOS apps |
To distribute your macOS application, you can either |
distribute it through the macOS App Store, |
or you can distribute the .app itself, |
perhaps from your own website. |
As of macOS 10.14.5, you need to notarize |
your macOS application before distributing |
it outside of the macOS App Store.The first step in both of the above processes |
involves working with your application inside of Xcode. |
To be able to compile your application from inside of |
Xcode you first need to build the application for release |
using the flutter build command, then open the |
Flutter macOS Runner application.Once inside of Xcode, follow either Apple’s |
documentation on notarizing macOS Applications, or |
on distributing an application through the App Store. |
You should also read through the |
macOS-specific support |
section below to understand how entitlements, |
the App Sandbox, and the Hardened Runtime |
impact your distributable application.Build and release a macOS app provides a more detailed |
step-by-step walkthrough of releasing a Flutter app to the |
App Store.<topic_end> |
<topic_start> |
Entitlements and the App Sandbox |
macOS builds are configured by default to be signed, |
and sandboxed with App Sandbox. |
This means that if you want to confer specific |
capabilities or services on your macOS app, |
such as the following:Then you must set up specific entitlements in Xcode. |
The following section tells you how to do this.<topic_end> |
<topic_start> |
Setting up entitlements |
Managing sandbox settings is done in the |
macos/Runner/*.entitlements files. When editing |
these files, you shouldn’t remove the original |
Runner-DebugProfile.entitlements exceptions |
(that support incoming network connections and JIT), |
as they’re necessary for the debug and profile |
modes to function correctly.If you’re used to managing entitlement files through |
the Xcode capabilities UI, be aware that the capabilities |
editor updates only one of the two files or, |
in some cases, it creates a whole new entitlements |
file and switches the project to use it for all configurations. |
Either scenario causes issues. We recommend that you |
edit the files directly. Unless you have a very specific |
reason, you should always make identical changes to both files.If you keep the App Sandbox enabled (which is required if you |
plan to distribute your application in the App Store), |
you need to manage entitlements for your application |
when you add certain plugins or other native functionality. |
For instance, using the file_chooser plugin |
requires adding either the |
com.apple.security.files.user-selected.read-only or |
com.apple.security.files.user-selected.read-write entitlement. |
Another common entitlement is |
com.apple.security.network.client, |
which you must add if you make any network requests.Without the com.apple.security.network.client entitlement, |
for example, network requests fail with a message such as:Important: The com.apple.security.network.server |
entitlement, which allows incoming network connections, |
is enabled by default only for debug and profile |
builds to enable communications between Flutter tools |
and a running app. If you need to allow incoming |
network requests in your application, |
you must add the com.apple.security.network.server |
entitlement to Runner-Release.entitlements as well, |
otherwise your application will work correctly for debug or |
profile testing, but will fail with release builds.For more information on these topics, |
see App Sandbox and Entitlements |
on the Apple Developer site.<topic_end> |
<topic_start> |
Hardened Runtime |
If you choose to distribute your application outside |
of the App Store, you need to notarize your application |
for compatibility with macOS 10.15+. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.