zapbird config
Put zapbird.yaml into your project files.
Usage: zapbird config apply [--force] [--project <folder>] and zapbird config check [--project <folder>]
#apply
Writes the permissions, reasons and app name from zapbird.yaml into ios/Runner/Info.plist and android/app/src/main/AndroidManifest.xml. It changes only those entries and leaves the rest of each file as it is.
A value someone changed by hand is left alone and reported. --force replaces it. A permission you removed from zapbird.yaml is taken out again if apply added it. Running apply twice changes nothing the second time.
$ zapbird config apply#check
Changes nothing. It fails when the files do not match zapbird.yaml, a reason is still a TODO, or your code imports a package whose permission is not listed. It also names setup only you can do, such as API keys and Xcode capabilities. Exit code 1 means something must be fixed.
$ zapbird config check#Options
| Option | What it does |
|---|---|
--force | (apply) Replace values that someone changed by hand. |
--project <folder> | The app folder. Default: the current folder. |
#Other entries
Anything else goes into the files as written:
ios: info_plist: LSApplicationQueriesSchemes: [https]android: permissions: [WAKE_LOCK]