text
stringlengths 1
372
|
|---|
the setup-msstore-cli
|
GitHub action installs the cli so that the action can use it for packaging
|
and publishing.
|
as packaging the MSIX uses the
|
msix pub package, the project’s pubspec.yaml
|
must contain an appropriate msix_config node.
|
you must create an azure AD directory from the dev center with
|
global administrator permission.
|
the GitHub action requires environment secrets from the partner center.
|
AZURE_AD_TENANT_ID, AZURE_AD_ClIENT_ID, and AZURE_AD_CLIENT_SECRET
|
are visible on the dev center following the instructions for the
|
windows store publish action.
|
you also need the SELLER_ID secret, which can be found in the dev center
|
under account settings > organization profile > legal info.
|
the application must already be present in the microsoft dev center with at
|
least one complete submission, and msstore init must be run once within
|
the repository before the action can be performed. once complete, running
|
msstore package .
|
and
|
msstore publish
|
in a GitHub action packages the
|
application into an MSIX and uploads it to a new submission on the dev center.
|
the steps necessary for MSIX publishing resemble the following
|
<topic_end>
|
<topic_start>
|
updating the app’s version number
|
for apps published to the microsoft store,
|
the version number must be set during the
|
packaging process.
|
the default version number of the app is 1.0.0.0.
|
info note
|
microsoft store apps are not allowed to have a
|
version with a revision number other than zero.
|
therefore, the last number of the version must
|
remain zero for all releases.
|
ensure that you follow microsoft’s
|
versioning guidelines.
|
for apps not published to the microsoft store, you
|
can set the app’s executable’s file and product versions.
|
the executable’s default file version is 1.0.0.1,
|
and its default product version is 1.0.0+1. to update these,
|
navigate to the pubspec.yaml file and update the
|
following line:
|
the build name is three numbers separated by dots,
|
followed by an optional build number that is separated
|
by a +. in the example above, the build name is 1.0.0
|
and the build number is 1.
|
the build name becomes the first three numbers of the
|
file and product versions, while the build number becomes
|
the fourth number of the file and product versions.
|
both the build name and number can be overridden in
|
flutter build windows by specifying --build-name and
|
--build-number, respectively.
|
info note
|
flutter projects created before flutter 3.3
|
need to be updated to set the executable’s version
|
information. for more information,
|
refer to the version migration guide.
|
<topic_end>
|
<topic_start>
|
add app icons
|
to update the icon of a flutter windows
|
desktop application before packaging use the
|
following instructions:
|
when packaging with the msix pub package,
|
the logo path can also be configured inside the pubspec.yaml file.
|
to update the application image in the store listing,
|
navigate to the store listing step of the submission
|
and select store logos.
|
from there, you can upload the logo with
|
the size of 300 x 300 pixels.
|
all uploaded images are retained for subsequent submissions.
|
<topic_end>
|
<topic_start>
|
validating the application package
|
before publication to the microsoft store,
|
first validate the application package locally.
|
windows app certification kit
|
is a tool included in the
|
windows software development kit (sdk).
|
to validate the application:
|
the report might contain important warnings and information,
|
even if the certification passes.
|
<topic_end>
|
<topic_start>
|
build and release a web app
|
during a typical development cycle,
|
you test an app using flutter run -d chrome
|
(for example) at the command line.
|
this builds a debug version of your app.
|
this page helps you prepare a release version
|
of your app and covers the following topics:
|
<topic_end>
|
<topic_start>
|
building the app for release
|
build the app for deployment using the
|
flutter build web command.
|
you can also choose which renderer to use
|
by using the --web-renderer option (see web renderers).
|
this generates the app, including the assets,
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.