@iternio/react-native-auto-play 0.1.16 → 0.2.0-alpha.1

package/README.md

@@ -220,6 +220,84 @@ You can customize certain behaviors of the library on Android Auto by setting pr
     ```
     The default values are `1000` for the delay and `500` for the duration.
 
+### Android Automotive
+
+This library also supports Android Automotive. To enable Android Automotive support, you need to configure a few properties in your Android project.
+
+-   **`minSdkVersion`**: The minimum API level for Android Automotive is 29. You must set `minSdkVersion` to at least `29`. For Android Auto, the minimum is `24`.
+
+-   **`isAutomotiveApp` flag**: You need to inform the library if this is an Automotive app by setting the `isAutomotiveApp` property to `true`. For Android Auto, it should be `false`.
+
+You can set these properties directly in your `android/gradle.properties` file:
+```properties
+# For Android Automotive
+minSdkVersion=29
+isAutomotiveApp=true
+```
+
+Alternatively, if you need to support different build variants (e.g., for both Android Auto and Android Automotive from the same codebase), using `react-native-config` is the recommended approach.
+
+1.  Install `react-native-config`:
+    ```bash
+    yarn add react-native-config
+    ```
+
+2.  Create different `.env` files for your variants. Create a default `.env` for Android Auto:
+    ```
+    # .env (for Android Auto)
+    isAutomotiveApp=false
+    minSdkVersion=24
+    ```
+    And an `.env.automotive` for Android Automotive:
+    ```
+    # .env.automotive
+    minSdkVersion=29
+    isAutomotiveApp=true
+    ```
+
+3.  In your `android/app/build.gradle`, apply the configuration from `react-native-config` based on your build flavors.
+    ```groovy
+    // android/app/build.gradle
+
+    project.ext.envConfigFiles = [
+        automotive: ".env.automotive",
+        // other flavors...
+    ]
+    apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle"
+
+    if (project.ext.has("env")) {
+        rootProject.ext.minSdkVersion = project.ext.env.minSdkVersion
+        rootProject.ext.isAutomotiveApp = project.ext.env.isAutomotiveApp
+    }
+    ```
+Adjust to the build variants your app provides. Check the example app for details.
+
+This approach allows you to dynamically set the required flags based on your build variant, which is demonstrated in the example app.
+
+#### App launch on Android Automotive
+
+Android Automotive requires you to remove your app activity since it invokes the libraries Android Auto service in a different way. Not doing so will bring up 2 app icons on the Android Automotive launcher.
+To get rid of your default activity, do an automotive specific build variant and add this AndroidManifest.xml for that variant.
+```xml
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:tools="http://schemas.android.com/tools">
+
+    <application>
+        <activity
+            android:name=".MainActivity"
+            tools:node="remove" /> <!-- remove main activity -->
+    </application>
+
+</manifest>
+```
+For details check the example app and its build variants.
+
+#### A Note on Android Studio
+
+When using build variants, Android Studio may not be aware of the selected variant during a Gradle sync. This can cause the IDE to show the incorrect implementation of native classes like `AndroidTelemetryObserver` (e.g., it might show the Android Auto version instead of the Automotive version).
+
+To work around this and allow for debugging or enhancing the Android Automotive-specific implementation, you can temporarily set the automotive flags in your `gradle.properties` file or your default `.env` file before running a Gradle sync.
+
 ## Icons
 The library is using [Material Symbols](https://fonts.google.com/icons) for iconography. The font is bundled with the library, so no extra setup is required. You can use these icons on both Android Auto and CarPlay.
 
@@ -347,6 +425,258 @@ export default registerAutoPlay;
 
 -   `HybridAutoPlay`: The primary interface for interacting with the native module, handling connection status and events.
 
+### Core Types
+
+#### AutoText
+Most text props accept `AutoText` so you can localize and provide variants. You can pass either a string or an object with `text`/`variants` as used throughout the example app.
+
+#### AutoImage
+Images are provided as `AutoImage` objects with a `type` and `name`. The built-in icon set is Material Symbols (see **Icons**). You can also use bundled images from your native project.
+
+#### RootComponentInitialProps
+All root components rendered by templates/scenes receive `RootComponentInitialProps`:
+
+-   `id`: Module identifier (e.g. `AutoPlayRoot`, `CarPlayDashboard`, or a cluster UUID).
+-   `rootTag`: React Native root tag.
+-   `colorScheme`: `'light' | 'dark'` initial color scheme (listen to `onAppearanceDidChange` on `MapTemplate` for updates).
+-   `window`: `{ width, height, scale }`.
+
+### Template Configs (Props)
+
+Below is a concise overview of the most important props per template. Optional props are marked as **optional**. Required props are marked as **required**.
+
+#### MapTemplateConfig
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `component` | `React.ComponentType<RootComponentInitialProps>` | ✅ | React component to render on the map surface. |
+| `onStopNavigation` | `(template: MapTemplate) => void` | ✅ | Called when navigation is stopped by the system. |
+| `headerActions` | `MapHeaderActions<MapTemplate>` | ❌ | Top action strip. See **Header Actions** below. |
+| `mapButtons` | `MapButtons<MapTemplate>` | ❌ | 1–4 map buttons shown on the map. |
+| `visibleTravelEstimate` | `'first'` `'last'` | ❌ | Which travel estimate to display. |
+| `onDidPan` / `onDidUpdateZoomGestureWithCenter` | callbacks | ❌ | Map gesture events. |
+| `onAppearanceDidChange` | `(colorScheme) => void` | ❌ | Listen for light/dark mode changes. |
+| `onAutoDriveEnabled` | `(template) => void` | ⚠️ | Android-only auto drive callback. Make sure to take action when receiving this and simulate a drive to the set destination. [Check Android docs for details](https://developer.android.com/reference/androidx/car/app/navigation/NavigationManagerCallback#onAutoDriveEnabled()) |
+
+#### ListTemplateConfig
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `title` | `AutoText` | ✅ | Header title. |
+| `sections` | `Section<ListTemplate>` | ❌ | List sections/rows. Not providing anything here will result in a loading indicator on Android and an empty list on iOS. |
+| `headerActions` | `HeaderActions<ListTemplate>` | ❌ | Header actions. See **Header Actions** below. |
+| `mapConfig` | `BaseMapTemplateConfig<ListTemplate>` | ❌ | Android map-with-content layout. |
+
+#### GridTemplateConfig
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `title` | `AutoText` | ✅ | Header title. |
+| `buttons` | `GridButton<GridTemplate>[]` | ✅ | Grid items. Providing an empty array will result in a loading indicator on Android and an empty template on iOS. |
+| `headerActions` | `HeaderActions<GridTemplate>` | ❌ | Header actions. See **Header Actions** below. |
+| `mapConfig` | `BaseMapTemplateConfig<GridTemplate>` | ❌ | Android map-with-content layout. |
+
+#### SearchTemplateConfig
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `title` | `AutoText` | ✅ | Header title. |
+| `results` | `SearchSection<SearchTemplate>` | ❌ | Initial results. |
+| `headerActions` | `HeaderActions<SearchTemplate>` | ❌ | Header actions. See **Header Actions** below. |
+| `searchHint` | `string` | ❌ | Android-only placeholder. |
+| `initialSearchText` | `string` | ❌ | Android-only initial value. |
+| `onSearchTextChanged` | `(text) => void` | ✅ | Fired on text input changes. |
+| `onSearchTextSubmitted` | `(text) => void` | ✅ | Fired on submit. |
+
+#### InformationTemplateConfig
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `title` | `AutoText` | ✅ | Header title. |
+| `items` | `InformationItems` | ❌ | 1–4 rows. |
+| `actions` | platform-specific | ❌ | Up to 2 buttons on Android, up to 3 on iOS. |
+| `headerActions` | `HeaderActions<InformationTemplate>` | ❌ | Header actions. See **Header Actions** below. |
+| `mapConfig` | `BaseMapTemplateConfig<InformationTemplate>` | ❌ | Android map-with-content layout. |
+
+#### MessageTemplateConfig
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `message` | `AutoText` | ✅ | Main message text. |
+| `title` | `AutoText` | ❌ | Android header title. |
+| `image` | `AutoImage` | ❌ | Android-only image above the message. |
+| `actions` | platform-specific | ❌ | Up to 2 buttons on Android, up to 3 on iOS. |
+| `headerActions` | `HeaderActionsAndroid<MessageTemplate>` | ❌ | Android-only header actions. |
+| `mapConfig` | `BaseMapTemplateConfig<MessageTemplate>` | ❌ | Android map-with-content layout. |
+
+#### SignInTemplateConfig (Android-only)
+
+| Prop | Type | Required | Notes |
+| --- | --- | --- | --- |
+| `signInMethod` | `SignInMethod` | ✅ | The sign-in method configuration. Can be QRSignIn, PinSignIn, InputSignIn. |
+| `title` | `string` | ❌ | Header title. |
+| `additionalText` | `string` | ❌ | Additional descriptive text. |
+| `instructions` | `string` | ❌ | Sign-in Instructions text. |
+| `actions` | `ActionButton<SignInTemplate>[]` | ❌ | Up to 2 buttons. |
+| `headerActions` | `SignInHeaderActions<SignInTemplate>` | ❌ | Header actions. See **Header Actions** below. |
+
+**SignInMethod**
+
+| Method | Type | Notes |
+| --- | --- | --- |
+| QR | `QrSignIn` | QR Code sign in |
+| PIN | `PinSignIn` | PIN Code sign in (1–12 characters) |
+| Input | `InputSignIn` | Text sign in, for example mail/username and password |
+
+For InputSignIn the keyboard and input fields can be configured with following properties:
+
+**KeyboardType enum:** `DEFAULT`, `EMAIL`, `PHONE`, `NUMBER`
+
+**TextInputType enum:** `PASSWORD`, `DEFAULT`
+
+
+### Header Actions (Important)
+
+On Android, header actions may be omitted, although this is not recommended. If `headerActions` is `undefined`, the system automatically renders the app icon in the header. Because Android Auto enforces monochrome icons, this can result in a poor-looking button.
+
+**Use these rules to avoid crashes:**
+
+1. **For List/Grid/Information/Search/Message/SignIn templates on Android**, always pass the structured object format (alignment is implicit via `startHeaderAction`/`endHeaderActions`):
+
+```ts
+const headerActions: HeaderActions<MyTemplate> = {
+  android: {
+    startHeaderAction: { type: 'back', onPress: (t) => HybridAutoPlay.popTemplate() },
+    endHeaderActions: [
+      { type: 'image', image: { name: 'help', type: 'glyph' }, onPress: () => {} },
+    ],
+  },
+  ios: {
+    backButton: { type: 'back', onPress: (t) => HybridAutoPlay.popTemplate() },
+    trailingNavigationBarButtons: [
+      { type: 'image', image: { name: 'close', type: 'glyph' }, onPress: () => {} },
+    ],
+  },
+};
+```
+
+⚠️ **Do not pass a raw array of actions** to `headerActions` on Android for these templates. Arrays are only valid for **MapTemplate** header actions (see below). Passing an array for header-based templates results in actions without alignment and can crash on Android.
+
+2. **For MapTemplate on Android**, you can use the array format (1–4 actions) for the action strip:
+
+```ts
+const mapHeaderActions: MapTemplateConfig['headerActions'] = {
+  android: [
+    { type: 'image', image: { name: 'list', type: 'glyph' }, onPress: () => {} },
+    { type: 'image', image: { name: 'search', type: 'glyph' }, onPress: () => {} },
+  ],
+  ios: {
+    leadingNavigationBarButtons: [
+      { type: 'image', image: { name: 'list', type: 'glyph' }, onPress: () => {} },
+    ],
+  },
+};
+```
+
+**Header action shapes (structured overview):**
+
+| Platform | Property | Shape | Limits / Notes |
+| --- | --- | --- | --- |
+| Android (header templates) | `headerActions.android` | `{ startHeaderAction?, endHeaderActions? }` | `endHeaderActions`: 1–2 buttons. `startHeaderAction` can be `appIcon`/`back`/custom. |
+| Android (MapTemplate) | `headerActions.android` | `ActionButton[]` | 1–4 action strip buttons. |
+| iOS | `headerActions.ios` | `{ backButton?, leadingNavigationBarButtons?, trailingNavigationBarButtons? }` | Each list supports 1–2 buttons. `backButton` optional (system back is added if omitted). |
+
+### Actions & Button Types (Quick Reference)
+
+-   **Android header actions** use `startHeaderAction` + `endHeaderActions`:
+    - `startHeaderAction`: `AppButton | BackButton | ActionButton`
+    - `endHeaderActions`: 1–2 buttons
+    - **If `headerActions` is omitted**: Android renders the **app icon** automatically.
+-   **iOS header actions** use:
+    - `backButton` (optional, otherwise iOS provides a default back action)
+    - `leadingNavigationBarButtons` (1–2)
+    - `trailingNavigationBarButtons` (1–2)
+-   **MapTemplate map buttons**: 1–4 buttons, including the special `pan` button.
+
+### Event & Listener APIs
+
+This section lists the available listeners and lifecycle callbacks so you can wire up connection state, visibility, cluster settings, and system events.
+
+#### HybridAutoPlay listeners
+
+| API | Payload | Notes |
+| --- | --- | --- |
+| `HybridAutoPlay.addListener(event, cb)` | event: `'didConnect'` `'didDisconnect'` | Connection changes for the head unit. |
+| `HybridAutoPlay.addListenerRenderState(moduleName, cb)` | `cb(visibility: 'willAppear' \| 'didAppear' \| 'willDisappear' \| 'didDisappear')` | Use `AutoPlayModules.*` or a cluster UUID. |
+| `HybridAutoPlay.addListenerVoiceInput(cb)` | `cb(location?, query?)` | Android-only voice input. |
+| `HybridAutoPlay.addSafeAreaInsetsListener(moduleName, cb)` | `cb(insets)` | Safe area inset changes for any module. |
+
+```ts
+import { AutoPlayModules, HybridAutoPlay } from '@iternio/react-native-auto-play';
+
+const cleanup = HybridAutoPlay.addListener('didConnect', () => {
+  console.log('Head unit connected');
+});
+
+const removeVisibility = HybridAutoPlay.addListenerRenderState(
+  AutoPlayModules.AutoPlayRoot,
+  (state) => console.log('AutoPlayRoot state', state)
+);
+```
+
+#### Template lifecycle callbacks
+
+All templates accept these lifecycle callbacks in their config:
+
+- `onWillAppear(animated?)`
+- `onDidAppear(animated?)`
+- `onWillDisappear(animated?)`
+- `onDidDisappear(animated?)`
+- `onPopped()` (not supported on all iOS templates, see notes in code)
+
+```ts
+const template = new ListTemplate({
+  title: { text: 'Menu' },
+  onWillAppear: () => console.log('will appear'),
+  onPopped: () => console.log('popped forever'),
+});
+```
+
+#### MapTemplate callbacks
+
+Map-specific callbacks live on `MapTemplateConfig`:
+
+- `onDidPan({ x, y })`
+- `onDidUpdateZoomGestureWithCenter({ x, y }, scale)`
+- `onClick({ x, y })` (Android)
+- `onDoubleClick({ x, y })` (Android)
+- `onAppearanceDidChange(colorScheme)`
+- `onAutoDriveEnabled(template)` (Android)
+- `onStopNavigation(template)` (**required**)
+
+#### AutoPlayCluster listeners (instrument cluster)
+
+| API | Payload | Notes |
+| --- | --- | --- |
+| `AutoPlayCluster.addListenerColorScheme(cb)` | `(clusterId, colorScheme)` | iOS + Android. |
+| `AutoPlayCluster.addListenerZoom(cb)` | `(clusterId, zoomEvent)` | iOS only. |
+| `AutoPlayCluster.addListenerCompass(cb)` | `(clusterId, enabled)` | iOS only. |
+| `AutoPlayCluster.addListenerSpeedLimit(cb)` | `(clusterId, enabled)` | iOS only. |
+
+```ts
+const removeCompass = AutoPlayCluster.addListenerCompass((clusterId, enabled) => {
+  console.log('Cluster', clusterId, 'compass', enabled);
+});
+```
+
+#### CarPlayDashboard listeners (iOS)
+
+| API | Payload | Notes |
+| --- | --- | --- |
+| `CarPlayDashboard.addListener(event, cb)` | event: `'didConnect'` `'didDisconnect'` | Connection changes for the dashboard scene. |
+| `CarPlayDashboard.addListenerRenderState(cb)` | `cb(visibility)` | Scene visibility changes. |
+| `CarPlayDashboard.addListenerColorScheme(cb)` | `cb(colorScheme)` | Light/dark changes. |
+
 ### Localization
 The library allows you to pass distances and durations and formats them according to the system defaults.
 For iOS make sure to provide all supported app languages in Info.plist CFBundleLocalizations for this to work properly, missing languages will use CFBundleDevelopmentRegion as fallback which is **en** most of the time. This results in a mix up with the region which might result in **en**_AT instead of **de**_AT for example.
@@ -397,12 +727,33 @@ useEffect(() => {
 
 ### Templates
 
--   `MapTemplate`: For navigation apps.
--   `ListTemplate`: To display a list of items.
--   `GridTemplate`: To display a grid of items.
--   `SearchTemplate`: For search functionality.
--   `InformationTemplate`: For showing information with actions.
--   `MessageTemplate`: For displaying messages.
+| Template | Purpose | Notes |
+| --- | --- | --- |
+| `MapTemplate` | Navigation, map rendering | Use as root; supports map buttons & navigation APIs. |
+| `ListTemplate` | Lists/menus | Supports sections, radio/toggle rows. |
+| `GridTemplate` | Action grid | Use `GridButton` items. |
+| `SearchTemplate` | Search UI | Android-only search bar callbacks. |
+| `InformationTemplate` | Info panels | Android uses PaneTemplate; iOS uses InformationTemplate. |
+| `MessageTemplate` | Modal messages | Always shown on top until popped. |
+
+**Template quick examples:**
+
+```ts
+// MapTemplate
+const map = new MapTemplate({
+  component: MapScreen,
+  onStopNavigation: () => {},
+  headerActions: { android: [{ type: 'image', image: { name: 'list', type: 'glyph' }, onPress: () => {} }] },
+});
+map.setRootTemplate();
+
+// ListTemplate
+new ListTemplate({
+  title: { text: 'Destinations' },
+  sections: [{ type: 'default', title: 'Recent', items: [{ type: 'default', title: { text: 'Home' }, onPress: () => {} }] }],
+  headerActions: { android: { startHeaderAction: { type: 'back', onPress: () => {} } } },
+}).push();
+```
 
 ### Hooks
 
@@ -410,20 +761,39 @@ useEffect(() => {
 -   `useVoiceInput()`: Access voice input functionality - Android Auto only.
 -   `useSafeAreaInsets()`: Get safe area insets for any root component.
 -   `useFocusedEffect()`: A useEffect alternative that executes when the specified component is visible to the user - use any of the `AutoPlayModules` enum or a cluster uuid to sepcify the component the effect should listen for.
--   `useAndroidAutoTelemetry()`: Access to car telemetry data on Android Auto.
+-   `useAndroidAutoTelemetry()`: Access to car telemetry data on Android Auto and Android Automotive.
     ```tsx
     import {
       useAndroidAutoTelemetry,
       AndroidAutoTelemetryPermissions,
+      AndroidAutomotiveTelemetryPermissions,
     } from '@iternio/react-native-auto-play';
+    import Config from 'react-native-config';
 
     const MyComponent = () => {
       const { telemetry, permissionsGranted, error } = useAndroidAutoTelemetry({
-        requiredPermissions: [
-          AndroidAutoTelemetryPermissions.Speed,
-          AndroidAutoTelemetryPermissions.Energy,
-          AndroidAutoTelemetryPermissions.Odometer,
-        ],
+        requiredPermissions:
+          Config.isAutomotiveApp === 'true'
+            ? [
+                AndroidAutomotiveTelemetryPermissions.Info,
+                AndroidAutomotiveTelemetryPermissions.Speed,
+                AndroidAutomotiveTelemetryPermissions.Energy,
+                AndroidAutomotiveTelemetryPermissions.ExteriorEnvironment,
+                AndroidAutomotiveTelemetryPermissions.EnergyPorts,
+              ]
+            : [
+                AndroidAutoTelemetryPermissions.Speed,
+                AndroidAutoTelemetryPermissions.Energy,
+                AndroidAutoTelemetryPermissions.Odometer,
+              ],
+        automotivePermissionRequest:
+          Config.isAutomotiveApp === 'true'
+            ? {
+                cancelButtonText: 'Cancel',
+                grantButtonText: 'Grant',
+                message: 'Grant permission for vehicle telemetry access.',
+              }
+            : undefined,
       });
 
       if (!permissionsGranted) {
@@ -441,6 +811,14 @@ useEffect(() => {
           <Text>Battery Level: {telemetry?.batteryLevel?.value}%</Text>
           <Text>Range: {telemetry?.range?.value} km</Text>
           <Text>Odometer: {telemetry?.odometer?.value} km</Text>
+          <Text>Selected Gear: {telemetry?.selectedGear?.value}</Text>
+          <Text>Outside Temperature: {telemetry?.envOutsideTemperature?.value}°C</Text>
+          <Text>EV Charge Port Connected: {String(telemetry?.evChargePortConnected?.value)}</Text>
+          <Text>EV Battery Charge Rate: {telemetry?.evBatteryInstantaneousChargeRate?.value} kW</Text>
+          <Text>Parking Brake On: {String(telemetry?.parkingBrakeOn?.value)}</Text>
+          <Text>Vehicle Name: {telemetry?.vehicle?.name?.value}</Text>
+          <Text>Vehicle Manufacturer: {telemetry?.vehicle?.manufacturer?.value}</Text>
+          <Text>Vehicle Year: {telemetry?.vehicle?.year?.value}</Text>
         </View>
       );
     }
@@ -452,6 +830,15 @@ useEffect(() => {
     - `range`: Range in km.
     - `odometer`: Odometer in km.
     - `vehicle`: Vehicle information (model name, model year, manufacturer).
+    - `selectedGear`: The currently selected gear, one of the `VehicleGear` enum:
+       - Neutral = 1
+       - Reverse = 2
+       - Park = 4
+       - Drive = 8
+    - `envOutsideTemperature`: The outside temperature in °C.
+    - `evChargePortConnected`: Whether the EV charge port is connected.
+    - `evBatteryInstantaneousChargeRate`: The instantaneous charge rate of the EV battery in kW.
+    - `parkingBrakeOn`: Whether the parking brake is on.
 
 
 ### Scenes
@@ -459,11 +846,36 @@ useEffect(() => {
 -   `CarPlayDashboard`: A component to render content on the CarPlay dashboard (CarPlay only).
 -   `AutoPlayCluster`: A component to render content on the instrument cluster (CarPlay & Android Auto).
 
+**Scene APIs (overview):**
+
+**CarPlayDashboard (iOS)**
+- `setComponent(component)` — register the React component (call once).
+- `setButtons(buttons)` — **required** to make the dashboard visible.
+- `addListener(event, cb)` — `didConnect` / `didDisconnect`.
+- `addListenerRenderState(cb)` — scene visibility callbacks.
+- `addListenerColorScheme(cb)` — light/dark changes.
+
+```ts
+CarPlayDashboard.setButtons([
+  {
+    titleVariants: ['Open App'],
+    subtitleVariants: ['Dashboard shortcut'],
+    image: { name: 'directions_car', type: 'glyph' },
+    onPress: () => console.log('open app'),
+  },
+]);
+```
+
+**AutoPlayCluster**
+- `setComponent(component)` — register the cluster component.
+- `setAttributedInactiveDescriptionVariants(variants)` — iOS only inactive text.
+- `addListenerColorScheme(cb)` / `addListenerZoom(cb)` / `addListenerCompass(cb)` / `addListenerSpeedLimit(cb)`.
+
 ## Known Issues
 
 ### iOS
 
--   **Broken exceptions with `react-native-skia`**: When using `react-native-skia` up to version `2.4.7`, exceptions on iOS are not reported correctly. This is fixed in newer versions of `react-native-skia`. For more details, see this [pull request](https://github.com/Shopify/react-native-skia/pull/3595).
+-   **Broken exceptions with `react-native-skia`**: When using `react-native-skia` up to version `2.4.14`, exceptions on iOS are not reported correctly. This is fixed in newer versions of `react-native-skia`. For more details, see this [pull request](https://github.com/Shopify/react-native-skia/pull/3595) and [issue](https://github.com/Shopify/react-native-skia/issues/3635).
 -   **AppState on iOS**: The `AppState` module from React Native does not work correctly on iOS because this library uses scenes, which are not supported by the stock `AppState` module. This library provides a custom state listener that works for both Android and iOS. Use `HybridAutoPlay.addListenerRenderState` instead of `AppState`.
 -   **Timers stop on screen lock**: iOS stops all timers when the device's main screen is turned off. To ensure timers continue to run (which is often necessary for background tasks related to autoplay), a patch for `react-native` is required. A patch is included in the root `patches/` directory and can be applied using `patch-package`.
 -   **expo-splash-screen stuck on iOS**: The `expo-splash-screen` module is broken on iOS because it does not support scenes, which are used by this library. This can cause the splash screen to be stuck on either the mobile device or on CarPlay. To fix this, a patch for `expo-splash-screen` is included in the root `patches/` directory and can be applied using `patch-package`. After applying the patch, you can hide the splash screen for a specific scene by passing the module name to the `hide` or `hideAsync` function. The module name can be one of the values from the `AutoPlayModules` enum or the UUID of a cluster screen.
@@ -477,6 +889,10 @@ useEffect(() => {
     // Hide the splash screen for the CarPlay screen
     hideAsync(AutoPlayModules.AutoPlayRoot);
     ```
+### Android
+-   **Broken exceptions with `react-native`** up to version 0.79
+When using react-native before 0.80.0 exceptions are broken and are reported as `Unknown runtime_error` or similar.
+See [this issue](https://github.com/mrousavy/nitro/issues/382) for details.
 
 ## Contributing
 
@@ -485,4 +901,3 @@ Contributions are welcome! Please submit a pull request.
 ## License
 
 This project is licensed under the MIT License - see the [LICENSE](../../LICENSE.md) file for details.
-

package/android/build.gradle

@@ -124,8 +124,20 @@ android {
           "${project.buildDir}/generated/source/codegen/java"
         ]
       }
+
+      if (getExtOrDefault("isAutomotiveApp") == "true") {
+        java.srcDirs += 'src/automotive/java'
+        manifest.srcFile 'src/automotive/AndroidManifest.xml'
+      } else {
+        java.srcDirs += 'src/auto/java'
+        manifest.srcFile 'src/main/AndroidManifest.xml'
+      }
     }
   }
+
+  if (getExtOrDefault("isAutomotiveApp") == "true") {
+    useLibrary 'android.car'
+  }
 }
 
 repositories {
@@ -133,7 +145,6 @@ repositories {
   google()
 }
 
-
 dependencies {
   // For < 0.71, this will be from the local maven repo
   // For > 0.71, this will be replaced by `com.facebook.react:react-android:$version` by react gradle plugin
@@ -151,5 +162,8 @@ dependencies {
     println("☎️ Enjoy your nitro powered Android Auto app!")
     implementation "androidx.car.app:app-projected:1.7.0"
   }
+
+  implementation 'com.google.android.gms:play-services-base:18.3.0'
+  implementation 'com.google.android.gms:play-services-auth:21.0.0'
 }
 

package/android/gradle.properties

@@ -1,5 +1,5 @@
 ReactNativeAutoPlay_kotlinVersion=2.1.20
-ReactNativeAutoPlay_minSdkVersion=23
+ReactNativeAutoPlay_minSdkVersion=24
 ReactNativeAutoPlay_targetSdkVersion=36
 ReactNativeAutoPlay_compileSdkVersion=36
 ReactNativeAutoPlay_ndkVersion=27.1.12297006