1/* tslint:disable */
2/**
3 * The standard Expo config object defined in `app.config.js` files.
4 */
5
6export interface ExpoConfig {
7  /**
8   * The name of your app as it appears both within Expo Go and on your home screen as a standalone app.
9   */
10  name: string;
11  /**
12   * A short description of what your app is and why it is great.
13   */
14  description?: string;
15  /**
16   * The friendly URL name for publishing. For example, `myAppName` will refer to the `expo.dev/@project-owner/myAppName` project.
17   */
18  slug: string;
19  /**
20   * The name of the Expo account that owns the project. This is useful for teams collaborating on a project. If not provided, the owner defaults to the username of the current user.
21   */
22  owner?: string;
23  /**
24   * The auto generated Expo account name and slug used for display purposes. It is not meant to be set directly. Formatted like `@username/slug`. When unauthenticated, the username is `@anonymous`. For published projects, this value may change when a project is transferred between accounts or renamed.
25   */
26  currentFullName?: string;
27  /**
28   * The auto generated Expo account name and slug used for services like Notifications and AuthSession proxy. It is not meant to be set directly. Formatted like `@username/slug`. When unauthenticated, the username is `@anonymous`. For published projects, this value will not change when a project is transferred between accounts or renamed.
29   */
30  originalFullName?: string;
31  /**
32   * Defaults to `unlisted`. `unlisted` hides the project from search results. `hidden` restricts access to the project page to only the owner and other users that have been granted access. Valid values: `public`, `unlisted`, `hidden`.
33   */
34  privacy?: 'public' | 'unlisted' | 'hidden';
35  /**
36   * The Expo sdkVersion to run the project on. This should line up with the version specified in your package.json.
37   */
38  sdkVersion?: string;
39  /**
40   * **Note: Don't use this property unless you are sure what you're doing**
41   *
42   * The runtime version associated with this manifest.
43   * Set this to `{"policy": "nativeVersion"}` to generate it automatically.
44   */
45  runtimeVersion?:
46    | string
47    | { policy: 'nativeVersion' | 'sdkVersion' | 'appVersion' | 'fingerprintExperimental' };
48  /**
49   * Your app version. In addition to this field, you'll also use `ios.buildNumber` and `android.versionCode` — read more about how to version your app [here](https://docs.expo.dev/distribution/app-stores/#versioning-your-app). On iOS this corresponds to `CFBundleShortVersionString`, and on Android, this corresponds to `versionName`. The required format can be found [here](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleshortversionstring).
50   */
51  version?: string;
52  /**
53   * Platforms that your project explicitly supports. If not specified, it defaults to `["ios", "android"]`.
54   */
55  platforms?: ('android' | 'ios' | 'web')[];
56  /**
57   * If you would like to share the source code of your app on Github, enter the URL for the repository here and it will be linked to from your Expo project page.
58   */
59  githubUrl?: string;
60  /**
61   * Locks your app to a specific orientation with portrait or landscape. Defaults to no lock. Valid values: `default`, `portrait`, `landscape`
62   */
63  orientation?: 'default' | 'portrait' | 'landscape';
64  /**
65   * Configuration to force the app to always use the light or dark user-interface appearance, such as "dark mode", or make it automatically adapt to the system preferences. If not provided, defaults to `light`. Requires `expo-system-ui` be installed in your project to work on Android.
66   */
67  userInterfaceStyle?: 'light' | 'dark' | 'automatic';
68  /**
69   * The background color for your app, behind any of your React views. This is also known as the root view background color. Requires `expo-system-ui` be installed in your project to work on iOS.
70   */
71  backgroundColor?: string;
72  /**
73   * On Android, this will determine the color of your app in the multitasker. Currently this is not used on iOS, but it may be used for other purposes in the future.
74   */
75  primaryColor?: string;
76  /**
77   * Local path or remote URL to an image to use for your app's icon. We recommend that you use a 1024x1024 png file. This icon will appear on the home screen and within the Expo app.
78   */
79  icon?: string;
80  /**
81   * Configuration for remote (push) notifications.
82   */
83  notification?: {
84    /**
85     * (Android only) Local path or remote URL to an image to use as the icon for push notifications. 96x96 png grayscale with transparency. We recommend following [Google's design guidelines](https://material.io/design/iconography/product-icons.html#design-principles). If not provided, defaults to your app icon.
86     */
87    icon?: string;
88    /**
89     * (Android only) Tint color for the push notification image when it appears in the notification tray. Defaults to `#ffffff`
90     */
91    color?: string;
92    /**
93     * Whether or not to display notifications when the app is in the foreground on iOS. `_displayInForeground` option in the individual push notification message overrides this option. [Learn more.](https://docs.expo.dev/push-notifications/receiving-notifications/#foreground-notification-behavior) Defaults to `false`.
94     */
95    iosDisplayInForeground?: boolean;
96    /**
97     * Show each push notification individually (`default`) or collapse into one (`collapse`).
98     */
99    androidMode?: 'default' | 'collapse';
100    /**
101     * If `androidMode` is set to `collapse`, this title is used for the collapsed notification message. For example, `'#{unread_notifications} new interactions'`.
102     */
103    androidCollapsedTitle?: string;
104  };
105  /**
106   * Configuration for the status bar on Android. For more details please navigate to [Configuring StatusBar](https://docs.expo.dev/guides/configuring-statusbar/).
107   */
108  androidStatusBar?: {
109    /**
110     * Configures the status bar icons to have a light or dark color. Valid values: `light-content`, `dark-content`. Defaults to `dark-content`
111     */
112    barStyle?: 'light-content' | 'dark-content';
113    /**
114     * Specifies the background color of the status bar. Defaults to `#00000000` (transparent) for `dark-content` bar style and `#00000088` (semi-transparent black) for `light-content` bar style
115     */
116    backgroundColor?: string;
117    /**
118     * Instructs the system whether the status bar should be visible or not. Defaults to `false`
119     */
120    hidden?: boolean;
121    /**
122     * When false, the system status bar pushes the content of your app down (similar to `position: relative`). When true, the status bar floats above the content in your app (similar to `position: absolute`). Defaults to `true` to match the iOS status bar behavior (which can only float above content). Explicitly setting this property to `true` will add `android:windowTranslucentStatus` to `styles.xml` and may cause unexpected keyboard behavior on Android when using the `softwareKeyboardLayoutMode` set to `resize`. In this case you will have to use `KeyboardAvoidingView` to manage the keyboard layout.
123     */
124    translucent?: boolean;
125  };
126  /**
127   * Configuration for the bottom navigation bar on Android. Can be used to configure the `expo-navigation-bar` module in EAS Build.
128   */
129  androidNavigationBar?: {
130    /**
131     * Determines how and when the navigation bar is shown. [Learn more](https://developer.android.com/training/system-ui/immersive). Requires `expo-navigation-bar` be installed in your project. Valid values: `leanback`, `immersive`, `sticky-immersive`
132     *
133     *  `leanback` results in the navigation bar being hidden until the first touch gesture is registered.
134     *
135     *  `immersive` results in the navigation bar being hidden until the user swipes up from the edge where the navigation bar is hidden.
136     *
137     *  `sticky-immersive` is identical to `'immersive'` except that the navigation bar will be semi-transparent and will be hidden again after a short period of time.
138     */
139    visible?: 'leanback' | 'immersive' | 'sticky-immersive';
140    /**
141     * Configure the navigation bar icons to have a light or dark color. Supported on Android Oreo and newer. Valid values: `'light-content'`, `'dark-content'`
142     */
143    barStyle?: 'light-content' | 'dark-content';
144    /**
145     * Specifies the background color of the navigation bar.
146     */
147    backgroundColor?: string;
148  };
149  /**
150   * Settings that apply specifically to running this app in a development client
151   */
152  developmentClient?: {
153    /**
154     * If true, the app will launch in a development client with no additional dialogs or progress indicators, just like in a standalone app.
155     */
156    silentLaunch?: boolean;
157  };
158  /**
159   * URL scheme(s) to link into your app. For example, if we set this to `'demo'`, then demo:// URLs would open your app when tapped. This is a build-time configuration, it has no effect in Expo Go.
160   */
161  scheme?: string | string[];
162  /**
163   * Any extra fields you want to pass to your experience. Values are accessible via `Constants.expoConfig.extra` ([Learn more](https://docs.expo.dev/versions/latest/sdk/constants/#constantsmanifest))
164   */
165  extra?: {
166    [k: string]: any;
167  };
168  /**
169   * @deprecated Use a `metro.config.js` file instead. [Learn more](https://docs.expo.dev/guides/customizing-metro/)
170   */
171  packagerOpts?: {
172    [k: string]: any;
173  };
174  /**
175   * Configuration for how and when the app should request OTA JavaScript updates
176   */
177  updates?: {
178    /**
179     * If set to false, your standalone app will never download any code, and will only use code bundled locally on the device. In that case, all updates to your app must be submitted through app store review. Defaults to true. (Note: This will not work out of the box with ExpoKit projects)
180     */
181    enabled?: boolean;
182    /**
183     * By default, Expo will check for updates every time the app is loaded. Set this to `ON_ERROR_RECOVERY` to disable automatic checking unless recovering from an error. Set this to `NEVER` to completely disable automatic checking. Must be one of `ON_LOAD` (default value), `ON_ERROR_RECOVERY`, `WIFI_ONLY`, or `NEVER`
184     */
185    checkAutomatically?: 'ON_ERROR_RECOVERY' | 'ON_LOAD' | 'WIFI_ONLY' | 'NEVER';
186    /**
187     * How long (in ms) to allow for fetching OTA updates before falling back to a cached version of the app. Defaults to 0. Must be between 0 and 300000 (5 minutes).
188     */
189    fallbackToCacheTimeout?: number;
190    /**
191     * URL from which expo-updates will fetch update manifests
192     */
193    url?: string;
194    /**
195     * Local path of a PEM-formatted X.509 certificate used for requiring and verifying signed Expo updates
196     */
197    codeSigningCertificate?: string;
198    /**
199     * Metadata for `codeSigningCertificate`
200     */
201    codeSigningMetadata?: {
202      /**
203       * Algorithm used to generate manifest code signing signature.
204       */
205      alg?: 'rsa-v1_5-sha256';
206      /**
207       * Identifier for the key in the certificate. Used to instruct signing mechanisms when signing or verifying signatures.
208       */
209      keyid?: string;
210    };
211    /**
212     * Extra HTTP headers to include in HTTP requests made by `expo-updates`. These may override preset headers.
213     */
214    requestHeaders?: {
215      [k: string]: any;
216    };
217  };
218  /**
219   * Provide overrides by locale for System Dialog prompts like Permissions Boxes
220   */
221  locales?: {
222    [k: string]:
223      | string
224      | {
225          [k: string]: any;
226        };
227  };
228  /**
229   * An array of file glob strings which point to assets that will be bundled within your standalone app binary. Read more in the [Offline Support guide](https://docs.expo.dev/guides/offline-support/)
230   */
231  assetBundlePatterns?: string[];
232  /**
233   * Config plugins for adding extra functionality to your project. [Learn more](https://docs.expo.dev/guides/config-plugins/).
234   */
235  plugins?: (string | [] | [string] | [string, any])[];
236  splash?: Splash;
237  /**
238   * Specifies the JavaScript engine for apps. Supported only on EAS Build. Defaults to `hermes`. Valid values: `hermes`, `jsc`.
239   */
240  jsEngine?: 'hermes' | 'jsc';
241  ios?: IOS;
242  android?: Android;
243  web?: Web;
244  /**
245   * Configuration for scripts to run to hook into the publish process
246   */
247  hooks?: {
248    postPublish?: PublishHook[];
249    postExport?: PublishHook[];
250  };
251  /**
252   * Enable experimental features that may be unstable, unsupported, or removed without deprecation notices.
253   */
254  experiments?: {
255    /**
256     * Export a website relative to a subpath of a domain. The path will be prepended as-is to links to all bundled resources. Prefix the path with a `/` (recommended) to load all resources relative to the server root. If the path **does not** start with a `/` then resources will be loaded relative to the code that requests them, this could lead to unexpected behavior. Example '/subpath'. Defaults to '' (empty string).
257     */
258    basePath?: string;
259    /**
260     * If true, indicates that this project does not support tablets or handsets, and only supports Apple TV and Android TV
261     */
262    supportsTVOnly?: boolean;
263    /**
264     * Enable tsconfig/jsconfig `compilerOptions.paths` and `compilerOptions.baseUrl` support for import aliases in Metro.
265     */
266    tsconfigPaths?: boolean;
267    /**
268     * Enable support for statically typed links in Expo Router. This feature requires TypeScript be set up in your Expo Router v2 project.
269     */
270    typedRoutes?: boolean;
271    /**
272     * Enables Turbo Modules, which are a type of native modules that use a different way of communicating between JS and platform code. When installing a Turbo Module you will need to enable this experimental option (the library still needs to be a part of Expo SDK already, like react-native-reanimated v2). Turbo Modules do not support remote debugging and enabling this option will disable remote debugging.
273     */
274    turboModules?: boolean;
275  };
276  /**
277   * Internal properties for developer tools
278   */
279  _internal?: {
280    /**
281     * List of plugins already run on the config
282     */
283    pluginHistory?: {
284      [k: string]: any;
285    };
286    [k: string]: any;
287  };
288}
289/**
290 * Configuration for loading and splash screen for standalone apps.
291 */
292export interface Splash {
293  /**
294   * Color to fill the loading screen background
295   */
296  backgroundColor?: string;
297  /**
298   * Determines how the `image` will be displayed in the splash loading screen. Must be one of `cover` or `contain`, defaults to `contain`.
299   */
300  resizeMode?: 'cover' | 'contain';
301  /**
302   * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
303   */
304  image?: string;
305  [k: string]: any;
306}
307/**
308 * Configuration that is specific to the iOS platform.
309 */
310export interface IOS {
311  /**
312   * The manifest for the iOS version of your app will be written to this path during publish.
313   */
314  publishManifestPath?: string;
315  /**
316   * The bundle for the iOS version of your app will be written to this path during publish.
317   */
318  publishBundlePath?: string;
319  /**
320   * The bundle identifier for your iOS standalone app. You make it up, but it needs to be unique on the App Store. See [this StackOverflow question](http://stackoverflow.com/questions/11347470/what-does-bundle-identifier-mean-in-the-ios-project).
321   */
322  bundleIdentifier?: string;
323  /**
324   * Build number for your iOS standalone app. Corresponds to `CFBundleVersion` and must match Apple's [specified format](https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion). (Note: Transporter will pull the value for `Version Number` from `expo.version` and NOT from `expo.ios.buildNumber`.)
325   */
326  buildNumber?: string;
327  /**
328   * The background color for your iOS app, behind any of your React views. Overrides the top-level `backgroundColor` key if it is present. Requires `expo-system-ui` be installed in your project to work on iOS.
329   */
330  backgroundColor?: string;
331  /**
332   * Local path or remote URL to an image to use for your app's icon on iOS. If specified, this overrides the top-level `icon` key. Use a 1024x1024 icon which follows Apple's interface guidelines for icons, including color profile and transparency.
333   *
334   *  Expo will generate the other required sizes. This icon will appear on the home screen and within the Expo app.
335   */
336  icon?: string;
337  /**
338   * URL to your app on the Apple App Store, if you have deployed it there. This is used to link to your store page from your Expo project page if your app is public.
339   */
340  appStoreUrl?: string;
341  /**
342   * Enable iOS Bitcode optimizations in the native build. Accepts the name of an iOS build configuration to enable for a single configuration and disable for all others, e.g. Debug, Release. Not available in Expo Go. Defaults to `undefined` which uses the template's predefined settings.
343   */
344  bitcode?: boolean | string;
345  /**
346   * Note: This property key is not included in the production manifest and will evaluate to `undefined`. It is used internally only in the build process, because it contains API keys that some may want to keep private.
347   */
348  config?: {
349    /**
350     * [Branch](https://branch.io/) key to hook up Branch linking services.
351     */
352    branch?: {
353      /**
354       * Your Branch API key
355       */
356      apiKey?: string;
357    };
358    /**
359     * Sets `ITSAppUsesNonExemptEncryption` in the standalone ipa's Info.plist to the given boolean value.
360     */
361    usesNonExemptEncryption?: boolean;
362    /**
363     * [Google Maps iOS SDK](https://developers.google.com/maps/documentation/ios-sdk/start) key for your standalone app.
364     */
365    googleMapsApiKey?: string;
366    /**
367     * [Google Mobile Ads App ID](https://support.google.com/admob/answer/6232340) Google AdMob App ID.
368     */
369    googleMobileAdsAppId?: string;
370    /**
371     * A boolean indicating whether to initialize Google App Measurement and begin sending user-level event data to Google immediately when the app starts. The default in Expo (Go and in standalone apps) is `false`. [Sets the opposite of the given value to the following key in `Info.plist`.](https://developers.google.com/admob/ios/eu-consent#delay_app_measurement_optional)
372     */
373    googleMobileAdsAutoInit?: boolean;
374  };
375  /**
376   * [Firebase Configuration File](https://support.google.com/firebase/answer/7015592) Location of the `GoogleService-Info.plist` file for configuring Firebase.
377   */
378  googleServicesFile?: string;
379  /**
380   * Whether your standalone iOS app supports tablet screen sizes. Defaults to `false`.
381   */
382  supportsTablet?: boolean;
383  /**
384   * If true, indicates that your standalone iOS app does not support handsets, and only supports tablets.
385   */
386  isTabletOnly?: boolean;
387  /**
388   * If true, indicates that your standalone iOS app does not support Slide Over and Split View on iPad. Defaults to `false`
389   */
390  requireFullScreen?: boolean;
391  /**
392   * Configuration to force the app to always use the light or dark user-interface appearance, such as "dark mode", or make it automatically adapt to the system preferences. If not provided, defaults to `light`.
393   */
394  userInterfaceStyle?: 'light' | 'dark' | 'automatic';
395  /**
396   * Dictionary of arbitrary configuration to add to your standalone app's native Info.plist. Applied prior to all other Expo-specific configuration. No other validation is performed, so use this at your own risk of rejection from the App Store.
397   */
398  infoPlist?: {
399    [k: string]: any;
400  };
401  /**
402   * Dictionary of arbitrary configuration to add to your standalone app's native *.entitlements (plist). Applied prior to all other Expo-specific configuration. No other validation is performed, so use this at your own risk of rejection from the App Store.
403   */
404  entitlements?: {
405    [k: string]: any;
406  };
407  /**
408   * An array that contains Associated Domains for the standalone app. [Learn more](https://developer.apple.com/documentation/safariservices/supporting_associated_domains).
409   */
410  associatedDomains?: string[];
411  /**
412   * A boolean indicating if the app uses iCloud Storage for `DocumentPicker`. See `DocumentPicker` docs for details.
413   */
414  usesIcloudStorage?: boolean;
415  /**
416   * A boolean indicating if the app uses Apple Sign-In. See `AppleAuthentication` docs for details.
417   */
418  usesAppleSignIn?: boolean;
419  /**
420   * A Boolean value that indicates whether the app may access the notes stored in contacts. You must [receive permission from Apple](https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_developer_contacts_notes) before you can submit your app for review with this capability.
421   */
422  accessesContactNotes?: boolean;
423  /**
424   * Configuration for loading and splash screen for standalone iOS apps.
425   */
426  splash?: {
427    /**
428     * Color to fill the loading screen background
429     */
430    backgroundColor?: string;
431    /**
432     * Determines how the `image` will be displayed in the splash loading screen. Must be one of `cover` or `contain`, defaults to `contain`.
433     */
434    resizeMode?: 'cover' | 'contain';
435    /**
436     * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
437     */
438    image?: string;
439    /**
440     * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
441     */
442    tabletImage?: string;
443    /**
444     * Configuration for loading and splash screen for standalone iOS apps in dark mode.
445     */
446    dark?: {
447      /**
448       * Color to fill the loading screen background
449       */
450      backgroundColor?: string;
451      /**
452       * Determines how the `image` will be displayed in the splash loading screen. Must be one of `cover` or `contain`, defaults to `contain`.
453       */
454      resizeMode?: 'cover' | 'contain';
455      /**
456       * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
457       */
458      image?: string;
459      /**
460       * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
461       */
462      tabletImage?: string;
463      [k: string]: any;
464    };
465    [k: string]: any;
466  };
467  /**
468   * Specifies the JavaScript engine for iOS apps. Supported only on EAS Build. Defaults to `hermes`. Valid values: `hermes`, `jsc`.
469   */
470  jsEngine?: 'hermes' | 'jsc';
471  /**
472   * **Note: Don't use this property unless you are sure what you're doing**
473   *
474   * The runtime version associated with this manifest for the iOS platform. If provided, this will override the top level runtimeVersion key.
475   * Set this to `{"policy": "nativeVersion"}` to generate it automatically.
476   */
477  runtimeVersion?:
478    | string
479    | { policy: 'nativeVersion' | 'sdkVersion' | 'appVersion' | 'fingerprintExperimental' };
480}
481/**
482 * Configuration that is specific to the Android platform.
483 */
484export interface Android {
485  /**
486   * The manifest for the Android version of your app will be written to this path during publish.
487   */
488  publishManifestPath?: string;
489  /**
490   * The bundle for the Android version of your app will be written to this path during publish.
491   */
492  publishBundlePath?: string;
493  /**
494   * The package name for your Android standalone app. You make it up, but it needs to be unique on the Play Store. See [this StackOverflow question](http://stackoverflow.com/questions/6273892/android-package-name-convention).
495   */
496  package?: string;
497  /**
498   * Version number required by Google Play. Increment by one for each release. Must be a positive integer. [Learn more](https://developer.android.com/studio/publish/versioning.html)
499   */
500  versionCode?: number;
501  /**
502   * The background color for your Android app, behind any of your React views. Overrides the top-level `backgroundColor` key if it is present.
503   */
504  backgroundColor?: string;
505  /**
506   * Configuration to force the app to always use the light or dark user-interface appearance, such as "dark mode", or make it automatically adapt to the system preferences. If not provided, defaults to `light`. Requires `expo-system-ui` be installed in your project to work on Android.
507   */
508  userInterfaceStyle?: 'light' | 'dark' | 'automatic';
509  /**
510   * Local path or remote URL to an image to use for your app's icon on Android. If specified, this overrides the top-level `icon` key. We recommend that you use a 1024x1024 png file (transparency is recommended for the Google Play Store). This icon will appear on the home screen and within the Expo app.
511   */
512  icon?: string;
513  /**
514   * Settings for an Adaptive Launcher Icon on Android. [Learn more](https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive)
515   */
516  adaptiveIcon?: {
517    /**
518     * Local path or remote URL to an image to use for your app's icon on Android. If specified, this overrides the top-level `icon` and the `android.icon` keys. Should follow the [specified guidelines](https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive). This icon will appear on the home screen.
519     */
520    foregroundImage?: string;
521    /**
522     * Local path or remote URL to an image representing the Android 13+ monochromatic icon. Should follow the [specified guidelines](https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive). This icon will appear on the home screen when the user enables 'Themed icons' in system settings on a device running Android 13+.
523     */
524    monochromeImage?: string;
525    /**
526     * Local path or remote URL to a background image for your app's Adaptive Icon on Android. If specified, this overrides the `backgroundColor` key. Must have the same dimensions as `foregroundImage`, and has no effect if `foregroundImage` is not specified. Should follow the [specified guidelines](https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive).
527     */
528    backgroundImage?: string;
529    /**
530     * Color to use as the background for your app's Adaptive Icon on Android. Defaults to white, `#FFFFFF`. Has no effect if `foregroundImage` is not specified.
531     */
532    backgroundColor?: string;
533  };
534  /**
535   * URL to your app on the Google Play Store, if you have deployed it there. This is used to link to your store page from your Expo project page if your app is public.
536   */
537  playStoreUrl?: string;
538  /**
539   * List of permissions used by the standalone app.
540   *
541   *  To use ONLY the following minimum necessary permissions and none of the extras supported by Expo in a default managed app, set `permissions` to `[]`. The minimum necessary permissions do not require a Privacy Policy when uploading to Google Play Store and are:
542   * • receive data from Internet
543   * • view network connections
544   * • full network access
545   * • change your audio settings
546   * • prevent device from sleeping
547   *
548   *  To use ALL permissions supported by Expo by default, do not specify the `permissions` key.
549   *
550   *   To use the minimum necessary permissions ALONG with certain additional permissions, specify those extras in `permissions`, e.g.
551   *
552   *  `[ "CAMERA", "ACCESS_FINE_LOCATION" ]`.
553   *
554   *   You can specify the following permissions depending on what you need:
555   *
556   * - `ACCESS_COARSE_LOCATION`
557   * - `ACCESS_FINE_LOCATION`
558   * - `ACCESS_BACKGROUND_LOCATION`
559   * - `CAMERA`
560   * - `RECORD_AUDIO`
561   * - `READ_CONTACTS`
562   * - `WRITE_CONTACTS`
563   * - `READ_CALENDAR`
564   * - `WRITE_CALENDAR`
565   * - `READ_EXTERNAL_STORAGE`
566   * - `WRITE_EXTERNAL_STORAGE`
567   * - `USE_FINGERPRINT`
568   * - `USE_BIOMETRIC`
569   * - `WRITE_SETTINGS`
570   * - `VIBRATE`
571   * - `READ_PHONE_STATE`
572   * - `FOREGROUND_SERVICE`
573   * - `WAKE_LOCK`
574   * - `com.anddoes.launcher.permission.UPDATE_COUNT`
575   * - `com.android.launcher.permission.INSTALL_SHORTCUT`
576   * - `com.google.android.c2dm.permission.RECEIVE`
577   * - `com.google.android.gms.permission.ACTIVITY_RECOGNITION`
578   * - `com.google.android.providers.gsf.permission.READ_GSERVICES`
579   * - `com.htc.launcher.permission.READ_SETTINGS`
580   * - `com.htc.launcher.permission.UPDATE_SHORTCUT`
581   * - `com.majeur.launcher.permission.UPDATE_BADGE`
582   * - `com.sec.android.provider.badge.permission.READ`
583   * - `com.sec.android.provider.badge.permission.WRITE`
584   * - `com.sonyericsson.home.permission.BROADCAST_BADGE`
585   *
586   */
587  permissions?: string[];
588  /**
589   * List of permissions to block in the final `AndroidManifest.xml`. This is useful for removing permissions that are added by native package `AndroidManifest.xml` files which are merged into the final manifest. Internally this feature uses the `tools:node="remove"` XML attribute to remove permissions. Not available in Expo Go.
590   */
591  blockedPermissions?: string[];
592  /**
593   * [Firebase Configuration File](https://support.google.com/firebase/answer/7015592) Location of the `GoogleService-Info.plist` file for configuring Firebase. Including this key automatically enables FCM in your standalone app.
594   */
595  googleServicesFile?: string;
596  /**
597   * Note: This property key is not included in the production manifest and will evaluate to `undefined`. It is used internally only in the build process, because it contains API keys that some may want to keep private.
598   */
599  config?: {
600    /**
601     * [Branch](https://branch.io/) key to hook up Branch linking services.
602     */
603    branch?: {
604      /**
605       * Your Branch API key
606       */
607      apiKey?: string;
608    };
609    /**
610     * [Google Maps Android SDK](https://developers.google.com/maps/documentation/android-api/signup) configuration for your standalone app.
611     */
612    googleMaps?: {
613      /**
614       * Your Google Maps Android SDK API key
615       */
616      apiKey?: string;
617    };
618    /**
619     * [Google Mobile Ads App ID](https://support.google.com/admob/answer/6232340) Google AdMob App ID.
620     */
621    googleMobileAdsAppId?: string;
622    /**
623     * A boolean indicating whether to initialize Google App Measurement and begin sending user-level event data to Google immediately when the app starts. The default in Expo (Client and in standalone apps) is `false`. [Sets the opposite of the given value to the following key in `Info.plist`](https://developers.google.com/admob/ios/eu-consent#delay_app_measurement_optional)
624     */
625    googleMobileAdsAutoInit?: boolean;
626  };
627  /**
628   * Configuration for loading and splash screen for managed and standalone Android apps.
629   */
630  splash?: {
631    /**
632     * Color to fill the loading screen background
633     */
634    backgroundColor?: string;
635    /**
636     * Determines how the `image` will be displayed in the splash loading screen. Must be one of `cover`, `contain` or `native`, defaults to `contain`.
637     */
638    resizeMode?: 'cover' | 'contain' | 'native';
639    /**
640     * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
641     */
642    image?: string;
643    /**
644     * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
645     *
646     *  `Natural sized image (baseline)`
647     */
648    mdpi?: string;
649    /**
650     * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
651     *
652     *  `Scale 1.5x`
653     */
654    hdpi?: string;
655    /**
656     * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
657     *
658     *  `Scale 2x`
659     */
660    xhdpi?: string;
661    /**
662     * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
663     *
664     *  `Scale 3x`
665     */
666    xxhdpi?: string;
667    /**
668     * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
669     *
670     *  `Scale 4x`
671     */
672    xxxhdpi?: string;
673    /**
674     * Configuration for loading and splash screen for managed and standalone Android apps in dark mode.
675     */
676    dark?: {
677      /**
678       * Color to fill the loading screen background
679       */
680      backgroundColor?: string;
681      /**
682       * Determines how the `image` will be displayed in the splash loading screen. Must be one of `cover`, `contain` or `native`, defaults to `contain`.
683       */
684      resizeMode?: 'cover' | 'contain' | 'native';
685      /**
686       * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
687       */
688      image?: string;
689      /**
690       * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
691       *
692       *  `Natural sized image (baseline)`
693       */
694      mdpi?: string;
695      /**
696       * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
697       *
698       *  `Scale 1.5x`
699       */
700      hdpi?: string;
701      /**
702       * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
703       *
704       *  `Scale 2x`
705       */
706      xhdpi?: string;
707      /**
708       * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
709       *
710       *  `Scale 3x`
711       */
712      xxhdpi?: string;
713      /**
714       * Local path or remote URL to an image to fill the background of the loading screen in "native" mode. Image size and aspect ratio are up to you. [Learn more]( https://developer.android.com/training/multiscreen/screendensities)
715       *
716       *  `Scale 4x`
717       */
718      xxxhdpi?: string;
719      [k: string]: any;
720    };
721    [k: string]: any;
722  };
723  /**
724   * Configuration for setting an array of custom intent filters in Android manifest. [Learn more](https://developer.android.com/guide/components/intents-filters)
725   */
726  intentFilters?: {
727    /**
728     * You may also use an intent filter to set your app as the default handler for links (without showing the user a dialog with options). To do so use `true` and then configure your server to serve a JSON file verifying that you own the domain. [Learn more](https://developer.android.com/training/app-links)
729     */
730    autoVerify?: boolean;
731    action: string;
732    data?: AndroidIntentFiltersData | AndroidIntentFiltersData[];
733    category?: string | string[];
734  }[];
735  /**
736   * Allows your user's app data to be automatically backed up to their Google Drive. If this is set to false, no backup or restore of the application will ever be performed (this is useful if your app deals with sensitive information). Defaults to the Android default, which is `true`.
737   */
738  allowBackup?: boolean;
739  /**
740   * Determines how the software keyboard will impact the layout of your application. This maps to the `android:windowSoftInputMode` property. Defaults to `resize`. Valid values: `resize`, `pan`.
741   */
742  softwareKeyboardLayoutMode?: 'resize' | 'pan';
743  /**
744   * Specifies the JavaScript engine for Android apps. Supported only on EAS Build and in Expo Go. Defaults to `hermes`. Valid values: `hermes`, `jsc`.
745   */
746  jsEngine?: 'hermes' | 'jsc';
747  /**
748   * **Note: Don't use this property unless you are sure what you're doing**
749   *
750   * The runtime version associated with this manifest for the Android platform. If provided, this will override the top level runtimeVersion key.
751   * Set this to `{"policy": "nativeVersion"}` to generate it automatically.
752   */
753  runtimeVersion?:
754    | string
755    | { policy: 'nativeVersion' | 'sdkVersion' | 'appVersion' | 'fingerprintExperimental' };
756}
757export interface AndroidIntentFiltersData {
758  /**
759   * Scheme of the URL, e.g. `https`
760   */
761  scheme?: string;
762  /**
763   * Hostname, e.g. `myapp.io`
764   */
765  host?: string;
766  /**
767   * Port, e.g. `3000`
768   */
769  port?: string;
770  /**
771   * Exact path for URLs that should be matched by the filter, e.g. `/records`
772   */
773  path?: string;
774  /**
775   * Pattern for paths that should be matched by the filter, e.g. `.*`. Must begin with `/`
776   */
777  pathPattern?: string;
778  /**
779   * Prefix for paths that should be matched by the filter, e.g. `/records/` will match `/records/123`
780   */
781  pathPrefix?: string;
782  /**
783   * MIME type for URLs that should be matched by the filter
784   */
785  mimeType?: string;
786}
787/**
788 * Configuration that is specific to the web platform.
789 */
790export interface Web {
791  /**
792   * Sets the rendering method for the web app for both `expo start` and `expo export`. `static` statically renders HTML files for every route in the `app/` directory, which is available only in Expo Router apps. `single` outputs a Single Page Application (SPA), with a single `index.html` in the output folder, and has no statically indexable HTML. Defaults to `single`.
793   */
794  output?: 'single' | 'static';
795  /**
796   * Relative path of an image to use for your app's favicon.
797   */
798  favicon?: string;
799  /**
800   * Defines the title of the document, defaults to the outer level name
801   */
802  name?: string;
803  /**
804   * A short version of the app's name, 12 characters or fewer. Used in app launcher and new tab pages. Maps to `short_name` in the PWA manifest.json. Defaults to the `name` property.
805   */
806  shortName?: string;
807  /**
808   * Specifies the primary language for the values in the name and short_name members. This value is a string containing a single language tag.
809   */
810  lang?: string;
811  /**
812   * Defines the navigation scope of this website's context. This restricts what web pages can be viewed while the manifest is applied. If the user navigates outside the scope, it returns to a normal web page inside a browser tab/window. If the scope is a relative URL, the base URL will be the URL of the manifest.
813   */
814  scope?: string;
815  /**
816   * Defines the color of the Android tool bar, and may be reflected in the app's preview in task switchers.
817   */
818  themeColor?: string;
819  /**
820   * Provides a general description of what the pinned website does.
821   */
822  description?: string;
823  /**
824   * Specifies the primary text direction for the name, short_name, and description members. Together with the lang member, it helps the correct display of right-to-left languages.
825   */
826  dir?: 'auto' | 'ltr' | 'rtl';
827  /**
828   * Defines the developers’ preferred display mode for the website.
829   */
830  display?: 'fullscreen' | 'standalone' | 'minimal-ui' | 'browser';
831  /**
832   * The URL that loads when a user launches the application (e.g., when added to home screen), typically the index. Note: This has to be a relative URL, relative to the manifest URL.
833   */
834  startUrl?: string;
835  /**
836   * Defines the default orientation for all the website's top level browsing contexts.
837   */
838  orientation?:
839    | 'any'
840    | 'natural'
841    | 'landscape'
842    | 'landscape-primary'
843    | 'landscape-secondary'
844    | 'portrait'
845    | 'portrait-primary'
846    | 'portrait-secondary';
847  /**
848   * Defines the expected “background color” for the website. This value repeats what is already available in the site’s CSS, but can be used by browsers to draw the background color of a shortcut when the manifest is available before the stylesheet has loaded. This creates a smooth transition between launching the web application and loading the site's content.
849   */
850  backgroundColor?: string;
851  /**
852   * If content is set to default, the status bar appears normal. If set to black, the status bar has a black background. If set to black-translucent, the status bar is black and translucent. If set to default or black, the web content is displayed below the status bar. If set to black-translucent, the web content is displayed on the entire screen, partially obscured by the status bar.
853   */
854  barStyle?: 'default' | 'black' | 'black-translucent';
855  /**
856   * Hints for the user agent to indicate to the user that the specified native applications (defined in expo.ios and expo.android) are recommended over the website.
857   */
858  preferRelatedApplications?: boolean;
859  /**
860   * Experimental features. These will break without deprecation notice.
861   */
862  dangerous?: {
863    [k: string]: any;
864  };
865  /**
866   * Configuration for PWA splash screens.
867   */
868  splash?: {
869    /**
870     * Color to fill the loading screen background
871     */
872    backgroundColor?: string;
873    /**
874     * Determines how the `image` will be displayed in the splash loading screen. Must be one of `cover` or `contain`, defaults to `contain`.
875     */
876    resizeMode?: 'cover' | 'contain';
877    /**
878     * Local path or remote URL to an image to fill the background of the loading screen. Image size and aspect ratio are up to you. Must be a .png.
879     */
880    image?: string;
881    [k: string]: any;
882  };
883  /**
884   * Firebase web configuration. Used by the expo-firebase packages on both web and native. [Learn more](https://firebase.google.com/docs/reference/js/firebase.html#initializeapp)
885   */
886  config?: {
887    firebase?: {
888      apiKey?: string;
889      authDomain?: string;
890      databaseURL?: string;
891      projectId?: string;
892      storageBucket?: string;
893      messagingSenderId?: string;
894      appId?: string;
895      measurementId?: string;
896      [k: string]: any;
897    };
898    [k: string]: any;
899  };
900  /**
901   * Sets the bundler to use for the web platform. Only supported in the local CLI `npx expo`.
902   */
903  bundler?: 'webpack' | 'metro';
904  [k: string]: any;
905}
906export interface PublishHook {
907  file?: string;
908  config?: {
909    [k: string]: any;
910  };
911  [k: string]: any;
912}
913