ZapbirdDocs

Prepare a store build

Turn the permissions your code needs into Info.plist and AndroidManifest.xml entries.

While you develop, the Zapbird runner already has every permission. Your own app does not. Before it goes to the App Store or Google Play, its Info.plist and AndroidManifest.xml must ask for what your code uses.

zapbird.yaml lists those permissions in one place, found from the packages your code imports.

#Create the file

zapbird create writes it for new projects, and zapbird start creates it the first time and adds to it when your code starts using a package that needs a permission. Nothing is ever removed for you.

Terminal
$ zapbird init

#Write your reasons

Each permission iOS asks the user about needs a reason in your words. Zapbird writes a TODO in its place, and config apply skips it until you replace it.

zapbird.yaml
permissions:  camera:    reason: Take a photo for your profile picture.  location:    reason: Show places near you.

#Apply it to your project

Terminal
$ zapbird config apply$ zapbird config check

Apply changes only the entries it manages and leaves the rest of each file as it is. A value someone changed by hand is left alone and reported. Running it twice changes nothing the second time.

#Check before you upload

Terminal
$ zapbird release check

This runs config check, then looks for what the stores refuse:

  • A missing version.
  • An app id that still starts with com.example.
  • An Android release build signed with the debug key.

Was this doc helpful?

Zapbird sends no analytics. Read about security.

Flutter and the related logo are trademarks of Google LLC. Zapbird is not endorsed by or affiliated with Google LLC.

esc