@symbiote-native/brightness 3.0.1 → 3.0.3

package/README.md

@@ -1,15 +1,15 @@
 # @symbiote-native/brightness
 
 A wrapper package for [SymbioteNative](../../README.md) that makes
-[`expo-brightness`](https://github.com/expo/expo/tree/main/packages/expo-brightness) — screen
+[`expo-brightness`](https://github.com/expo/expo/tree/main/packages/expo-brightness) - screen
 brightness get/set, Android-only system-brightness-mode control, an iOS-only brightness-change
-listener, and permission get/request — usable from **every** adapter: React, Vue, Svelte, Solid,
-and Angular, not just React. Unlike [`@symbiote-native/sensors`](../sensors) — a `DeviceSensor` class per instance,
-subscribed through a hook/composable/service — this package's surface is mostly stateless free
+listener, and permission get/request - usable from **every** adapter: React, Vue, Svelte, Solid,
+and Angular, not just React. Unlike [`@symbiote-native/sensors`](../sensors) - a `DeviceSensor` class per instance,
+subscribed through a hook/composable/service - this package's surface is mostly stateless free
 async functions plus one listener; only the permission surface gets its own lifecycle hook/
 composable/service, mirroring upstream's own `usePermissions`. Built the same way as
 [`@symbiote-native/local-auth`](../local-auth), [`@symbiote-native/battery`](../battery), and
-[`@symbiote-native/haptics`](../haptics) — an `expo-modules-core`-based wrapper (see the
+[`@symbiote-native/haptics`](../haptics) - an `expo-modules-core`-based wrapper (see the
 `symbiote-expo-native-module` project skill for the full mechanism: why `expo-modules-core` is
 depended on directly and never the `expo` meta-package, why the upstream JS is hand-ported into
 `core/` rather than imported, and how autolinking picks up the native module).
@@ -28,17 +28,17 @@ npx @symbiote-native/cli new my-app --brightness
 npx @symbiote-native/cli add --brightness
 ```
 
-Either way: installs `@symbiote-native/brightness` and wires the native autolinking automatically — see
+Either way: installs `@symbiote-native/brightness` and wires the native autolinking automatically - see
 [`@symbiote-native/cli`](../cli).
 
 <details>
-<summary>Manual install (no CLI — installing and wiring native autolinking by hand)</summary>
+<summary>Manual install (no CLI - installing and wiring native autolinking by hand)</summary>
 
 ```bash
 npm install @symbiote-native/brightness
 ```
 
-`expo-brightness` and `expo-modules-core` come along as regular, pinned dependencies — never
+`expo-brightness` and `expo-modules-core` come along as regular, pinned dependencies - never
 install either yourself, and never add the `expo` meta-package to this project (it bundles its own
 Metro/Babel pipeline that conflicts with this project's own).
 
@@ -46,23 +46,23 @@ Metro/Babel pipeline that conflicts with this project's own).
 
 Unlike a plain RN native module, `expo-brightness`'s native code is discovered by
 `expo-modules-autolinking`, not the `react-native.config.cjs`/podspec mechanism other wrappers in
-this repo use — this needs wiring into the native host app **once**, covering this package and
+this repo use - this needs wiring into the native host app **once**, covering this package and
 every other `expo-modules-core` package with zero further changes:
 
 | Platform | Touches                                                                                                                                                             |
 | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| iOS      | `ios/Podfile` — add `use_expo_modules!`                                                                                                                             |
-| iOS      | `AppDelegate.swift` — Expo's runtime-bootstrap hook                                                                                                                 |
-| Android  | `settings.gradle` / `app/build.gradle` — resolve and include the Expo Gradle projects                                                                               |
-| Android  | `MainApplication.kt` — Expo's bootstrap hook, plus a hand-written native-module name map (there's no `expo` meta-package here to auto-generate one)                 |
-| Android  | `AndroidManifest.xml` — `android.permission.WRITE_SETTINGS`, required to set the system-wide brightness (`setSystemBrightnessAsync`/`setSystemBrightnessModeAsync`) |
-
-Full mechanics — the Podfile pieces that normally ship inside the `expo` package, the `expo`
-peer-dependency exclusion list — live in the `symbiote-expo-native-module` skill. Reference
+| iOS      | `ios/Podfile` - add `use_expo_modules!`                                                                                                                             |
+| iOS      | `AppDelegate.swift` - Expo's runtime-bootstrap hook                                                                                                                 |
+| Android  | `settings.gradle` / `app/build.gradle` - resolve and include the Expo Gradle projects                                                                               |
+| Android  | `MainApplication.kt` - Expo's bootstrap hook, plus a hand-written native-module name map (there's no `expo` meta-package here to auto-generate one)                 |
+| Android  | `AndroidManifest.xml` - `android.permission.WRITE_SETTINGS`, required to set the system-wide brightness (`setSystemBrightnessAsync`/`setSystemBrightnessModeAsync`) |
+
+Full mechanics - the Podfile pieces that normally ship inside the `expo` package, the `expo`
+peer-dependency exclusion list - live in the `symbiote-expo-native-module` skill. Reference
 implementation: `examples/expo-react/android/app/src/main/AndroidManifest.xml` (the
 `WRITE_SETTINGS` permission) and
 `examples/expo-react/android/app/src/main/java/com/canaryexpo/MainApplication.kt` (the
-`BrightnessModule` registration) — the Vue and Angular Expo canaries wire the same three layers.
+`BrightnessModule` registration) - the Vue and Angular Expo canaries wire the same three layers.
 
 </details>
 
@@ -73,24 +73,24 @@ src/core/                 isAvailableAsync, get/setBrightnessAsync, the Android-
                           system-brightness-mode surface, permission get/request, and
                           addBrightnessListener (iOS only); native-module.ts resolves
                           ExpoBrightness through expo-modules-core's requireNativeModule.
-src/react/hooks/           @symbiote-native/brightness/react   — usePermissions
-src/vue/composables/       @symbiote-native/brightness/vue     — usePermissions (same name)
-src/svelte/runes/          @symbiote-native/brightness/svelte  — usePermissions (same name)
-src/solid/primitives/      @symbiote-native/brightness/solid   — createPermissions (Solid says
+src/react/hooks/           @symbiote-native/brightness/react   - usePermissions
+src/vue/composables/       @symbiote-native/brightness/vue     - usePermissions (same name)
+src/svelte/runes/          @symbiote-native/brightness/svelte  - usePermissions (same name)
+src/solid/primitives/      @symbiote-native/brightness/solid   - createPermissions (Solid says
                                                                  create*, not use*)
-src/angular/services/      @symbiote-native/brightness/angular — PermissionsService
+src/angular/services/      @symbiote-native/brightness/angular - PermissionsService
 ```
 
 Each adapter's hook/composable/service wraps the same one-shot `getPermissionsAsync`/
 `requestPermissionsAsync` pair in its own lifecycle idiom (auto-fetch on mount, exposed as a
-tuple/object/accessor/signal). Every other export — brightness get/set, the system-brightness-mode
-surface, the listener — is a stateless free-function re-export, written once in `core/` and shared
+tuple/object/accessor/signal). Every other export - brightness get/set, the system-brightness-mode
+surface, the listener - is a stateless free-function re-export, written once in `core/` and shared
 verbatim by every adapter.
 
 ## Use it
 
 ```tsx
-// React — trimmed from examples/expo-react/screens/BrightnessScreen.tsx
+// React - trimmed from examples/expo-react/screens/BrightnessScreen.tsx
 import { useEffect, useState } from 'react';
 import {
   addBrightnessListener,
@@ -105,7 +105,7 @@ function BrightnessScreen() {
 
   useEffect(() => {
     getBrightnessAsync().then(setBrightness);
-    // iOS only — never fires on Android, so there the value only changes via setBrightnessAsync.
+    // iOS only - never fires on Android, so there the value only changes via setBrightnessAsync.
     const subscription = addBrightnessListener(event =>
       setBrightness(event.brightness),
     );
@@ -130,7 +130,7 @@ function BrightnessScreen() {
 ```
 
 ```vue
-<!-- Vue — trimmed from examples/expo-vue-sfc/screens/BrightnessScreen.vue -->
+<!-- Vue - trimmed from examples/expo-vue-sfc/screens/BrightnessScreen.vue -->
 <script setup lang="ts">
 import { onMounted, onUnmounted, ref } from 'vue';
 import {
@@ -173,7 +173,7 @@ onUnmounted(() => subscription?.remove());
 ```
 
 ```svelte
-<!-- Svelte — trimmed from examples/expo-svelte/screens/BrightnessScreen.svelte -->
+<!-- Svelte - trimmed from examples/expo-svelte/screens/BrightnessScreen.svelte -->
 <script lang="ts">
   import {
     addBrightnessListener,
@@ -214,7 +214,7 @@ onUnmounted(() => subscription?.remove());
 ```
 
 ```tsx
-// Solid — trimmed from examples/expo-solid/screens/BrightnessScreen.tsx
+// Solid - trimmed from examples/expo-solid/screens/BrightnessScreen.tsx
 import { createSignal, onCleanup } from 'solid-js';
 import {
   addBrightnessListener,
@@ -254,7 +254,7 @@ function BrightnessScreen() {
 ```
 
 ```ts
-// Angular — trimmed from examples/expo-angular/src/screens/BrightnessScreen.ts
+// Angular - trimmed from examples/expo-angular/src/screens/BrightnessScreen.ts
 import { Component, inject, signal } from '@angular/core';
 import { SYMBIOTE_ELEMENTS } from '@symbiote-native/angular';
 import {
@@ -307,7 +307,7 @@ export class BrightnessScreen {
 The real demo screens (`examples/expo-react/screens/BrightnessScreen.tsx` and its Vue/Svelte/
 Solid/Angular twins in `examples/expo-vue-sfc`, `examples/expo-vue-tsx`, `examples/expo-svelte`,
 `examples/expo-solid`, `examples/expo-angular`) additionally
-gate an Android-only system-brightness-mode card behind `Platform.OS === 'android'` — see
+gate an Android-only system-brightness-mode card behind `Platform.OS === 'android'` - see
 [API](#api) below for that surface's full signatures.
 
 ## API
@@ -317,7 +317,7 @@ its own lifecycle hook/composable/service (matching upstream's own `usePermissio
 
 ```ts
 isAvailableAsync(): Promise<boolean>
-// Whether the brightness API is available — !!native.getBrightnessAsync.
+// Whether the brightness API is available - !!native.getBrightnessAsync.
 
 getBrightnessAsync(): Promise<number>
 setBrightnessAsync(brightnessValue: number): Promise<void>
@@ -325,26 +325,26 @@ setBrightnessAsync(brightnessValue: number): Promise<void>
 
 getSystemBrightnessAsync(): Promise<number>
 setSystemBrightnessAsync(brightnessValue: number): Promise<void>
-// System-wide brightness. On iOS these delegate straight to get/setBrightnessAsync — there is
+// System-wide brightness. On iOS these delegate straight to get/setBrightnessAsync - there is
 // no separate system-level value on that platform.
 
 restoreSystemBrightnessAsync(): Promise<void>
 isUsingSystemBrightnessAsync(): Promise<boolean>
 getSystemBrightnessModeAsync(): Promise<BrightnessMode>       // UNKNOWN / AUTOMATIC / MANUAL
 setSystemBrightnessModeAsync(mode: BrightnessMode): Promise<void>
-// Android only — every one of these is a no-op (or resolves a fixed fallback) on iOS/other
+// Android only - every one of these is a no-op (or resolves a fixed fallback) on iOS/other
 // platforms. setSystemBrightnessModeAsync(UNKNOWN) is also always a no-op, even on Android.
 
 getPermissionsAsync(): Promise<PermissionResponse>
 requestPermissionsAsync(): Promise<PermissionResponse>
-// Plain passthroughs to the native module — no platform gating.
+// Plain passthroughs to the native module - no platform gating.
 
 addBrightnessListener(listener: (event: BrightnessEvent) => void): EventSubscription
-// @platform ios — fires only on iOS; never fires on Android or web.
+// @platform ios - fires only on iOS; never fires on Android or web.
 ```
 
 Plus `BrightnessMode` (enum: `UNKNOWN`/`AUTOMATIC`/`MANUAL`), `BrightnessEvent`, and
-`PermissionStatus`/`PermissionResponse`/`PermissionExpiration` — the latter three re-exported
+`PermissionStatus`/`PermissionResponse`/`PermissionExpiration` - the latter three re-exported
 verbatim from `expo-modules-core`, never the `expo` meta-package.
 
 ```ts
@@ -375,10 +375,10 @@ const [status, request] = usePermissions();
 // Vue
 const { status, request } = usePermissions();
 
-// Svelte — a boxed getter, read as permissions.status
+// Svelte - a boxed getter, read as permissions.status
 const permissions = usePermissions();
 
-// Solid — accessors, so status() is what a tracked scope reads
+// Solid - accessors, so status() is what a tracked scope reads
 const { status, request } = createPermissions();
 
 // Angular
@@ -392,32 +392,43 @@ readonly status = inject(PermissionsService).connect();
   is no separate system-level brightness there); `restoreSystemBrightnessAsync`/
   `setSystemBrightnessModeAsync` no-op, `isUsingSystemBrightnessAsync` resolves `false`, and
   `getSystemBrightnessModeAsync` resolves `BrightnessMode.UNKNOWN` on every other platform.
-- **`addBrightnessListener` is iOS only.** It never fires on Android or web — an app relying on
+- **`addBrightnessListener` is iOS only.** It never fires on Android or web - an app relying on
   it for cross-platform behavior needs its own fallback (e.g. polling `getBrightnessAsync`).
-- **The iOS Simulator never round-trips brightness at all.** `UIScreen.main.brightness` — what
-  `getBrightnessAsync`/`setBrightnessAsync` read and write on iOS — isn't implemented by the
+- **The iOS Simulator never round-trips brightness at all.** `UIScreen.main.brightness` - what
+  `getBrightnessAsync`/`setBrightnessAsync` read and write on iOS - isn't implemented by the
   Simulator: `set` is a silent no-op and `get` always resolves a constant (observed `1.0`),
   regardless of what was written. This is a long-standing Apple Simulator limitation reproducible
-  in any app, including stock Expo Go — not a bug in this wrapper. It only reproduces on a real
+  in any app, including stock Expo Go - not a bug in this wrapper. It only reproduces on a real
   iOS device; Android's emulator has no equivalent gap (see the `symbiote-expo-native-module`
   skill for the verified symptom and the underlying `BrightnessModule.swift` call).
 
+## Common questions
+
+- **iOS change disappears.** `setBrightnessAsync` persists only until the device locks.
+- **Android works only while the app is open.** It applies to the current activity; call
+  `restoreSystemBrightnessAsync` to return to the system value.
+- **System brightness on Android.** `setSystemBrightnessAsync` (experimental) needs `WRITE_SETTINGS`.
+- **Permission result empty after granting.** Reported upstream; re-query after returning from settings.
+
+Sources: [Expo docs: Brightness](https://docs.expo.dev/versions/latest/sdk/brightness/),
+[expo/expo#18967](https://github.com/expo/expo/issues/18967).
+
 ## Test it
 
-No Fabric/Descriptor angle at all — brightness is a pure async-function + listener + permission
+No Fabric/Descriptor angle at all - brightness is a pure async-function + listener + permission
 surface, never a view. Tests inject a fake native-module object in place of the real
 `requireNativeModule` resolution (`src/core/*.test.ts`,
 `src/{react,vue,svelte,solid,angular}/**/*.test.{ts,tsx}`,
-`vitest`), the same pattern `expo-brightness` itself uses upstream — no `installFabric()`, no
+`vitest`), the same pattern `expo-brightness` itself uses upstream - no `installFabric()`, no
 ViewConfig. Native rendering itself is verified on-device (see the parent
 [README](../../README.md) for the project's testing model).
 
 ## Known gaps
 
-- Not yet wired into the public, non-Expo `examples/react` canary — only in `examples/expo-react`
+- Not yet wired into the public, non-Expo `examples/react` canary - only in `examples/expo-react`
   (and its Vue/Svelte/Solid/Angular Expo twins, `examples/expo-vue-sfc`/`examples/expo-vue-tsx`/
   `examples/expo-svelte`/`examples/expo-solid`/`examples/expo-angular`, all of which already have
   full three-layer native wiring: Android `MainApplication.kt` registration + `WRITE_SETTINGS`,
   plus the iOS Podfile/pod install).
-- Tests exercise the JS layer only (fake native module, `vitest`) — no on-device/simulator
+- Tests exercise the JS layer only (fake native module, `vitest`) - no on-device/simulator
   automated smoke test yet, only manual verification.

package/build/angular/services/permissions.service/index.d.ts

@@ -1,12 +1,5 @@
-import { type Signal } from '@angular/core';
+import { PermissionsServiceBase } from '@symbiote-native/angular';
 import { type PermissionResponse } from '../../../core';
-export declare class PermissionsService {
-    private readonly status;
-    private readonly fetchError;
-    private isAutoFetchStarted;
-    /** Why the auto-fetch left `status` at null. Cleared by the next successful get()/request(). */
-    readonly error: Signal<Error | null>;
-    connect(): Signal<PermissionResponse | null>;
-    get(): Promise<PermissionResponse>;
-    request(): Promise<PermissionResponse>;
+export declare class PermissionsService extends PermissionsServiceBase<PermissionResponse> {
+    constructor();
 }

package/build/angular/services/permissions.service/index.js

@@ -1,3 +1,4 @@
+// Angular twin of React's `usePermissions`: `inject(PermissionsService).connect()` gives a signal
 var __esDecorate = (this && this.__esDecorate) || function (ctor, descriptorIn, decorators, contextIn, initializers, extraInitializers) {
     function accept(f) { if (f !== void 0 && typeof f !== "function") throw new TypeError("Function expected"); return f; }
     var kind = contextIn.kind, key = kind === "getter" ? "get" : kind === "setter" ? "set" : "value";
@@ -32,62 +33,26 @@ var __runInitializers = (this && this.__runInitializers) || function (thisArg, i
     }
     return useValue ? value : void 0;
 };
-// Angular twin of React's usePermissions hook and Vue's usePermissions composable.
-// `connect()` auto-fetches once (no ongoing subscription to clean up, so no Injector/effect
-// needed, unlike BatteryStateService) and returns a readonly signal; get()/request() are
-// imperative one-shot methods.
-//
-//   readonly status = inject(PermissionsService).connect();
-//   // template: {{ status()?.granted }}
-//
-// The auto-fetch has nobody to reject to, so its failure lands in the `error` signal instead of
-// escaping as an unhandled rejection: a null status with a non-null error is how a consumer tells
-// "the fetch failed" from "not fetched yet". get()/request() still reject to their direct caller —
-// only the automatic call is made safe.
-import { Injectable, signal } from '@angular/core';
+import { Injectable } from '@angular/core';
+import { PermissionsServiceBase } from '@symbiote-native/angular';
 import { getPermissionsAsync, requestPermissionsAsync, } from '../../../core/index.js';
 let PermissionsService = (() => {
     let _classDecorators = [Injectable({ providedIn: 'root' })];
     let _classDescriptor;
     let _classExtraInitializers = [];
     let _classThis;
-    var PermissionsService = class {
+    let _classSuper = PermissionsServiceBase;
+    var PermissionsService = class extends _classSuper {
         static { _classThis = this; }
         static {
-            const _metadata = typeof Symbol === "function" && Symbol.metadata ? Object.create(null) : void 0;
+            const _metadata = typeof Symbol === "function" && Symbol.metadata ? Object.create(_classSuper[Symbol.metadata] ?? null) : void 0;
             __esDecorate(null, _classDescriptor = { value: _classThis }, _classDecorators, { kind: "class", name: _classThis.name, metadata: _metadata }, null, _classExtraInitializers);
             PermissionsService = _classThis = _classDescriptor.value;
             if (_metadata) Object.defineProperty(_classThis, Symbol.metadata, { enumerable: true, configurable: true, writable: true, value: _metadata });
             __runInitializers(_classThis, _classExtraInitializers);
         }
-        status = signal(null);
-        fetchError = signal(null);
-        isAutoFetchStarted = false;
-        /** Why the auto-fetch left `status` at null. Cleared by the next successful get()/request(). */
-        error = this.fetchError.asReadonly();
-        connect() {
-            // Latched rather than guarded on `status() === null`: a failed fetch leaves status null
-            // forever, so the old guard turned every later connect() into another native call — unbounded
-            // once connect() is reached from a change-detected expression instead of a field initializer.
-            if (!this.isAutoFetchStarted) {
-                this.isAutoFetchStarted = true;
-                this.get().catch((cause) => {
-                    this.fetchError.set(cause instanceof Error ? cause : new Error(String(cause)));
-                });
-            }
-            return this.status.asReadonly();
-        }
-        async get() {
-            const response = await getPermissionsAsync();
-            this.status.set(response);
-            this.fetchError.set(null);
-            return response;
-        }
-        async request() {
-            const response = await requestPermissionsAsync();
-            this.status.set(response);
-            this.fetchError.set(null);
-            return response;
+        constructor() {
+            super(getPermissionsAsync, requestPermissionsAsync);
         }
     };
     return PermissionsService = _classThis;

package/build-ngc/angular/services/permissions.service/index.d.ts

@@ -1,15 +1,8 @@
-import { type Signal } from '@angular/core';
+import { PermissionsServiceBase } from '@symbiote-native/angular';
 import { type PermissionResponse } from '../../../core';
 import * as i0 from "@angular/core";
-export declare class PermissionsService {
-    private readonly status;
-    private readonly fetchError;
-    private isAutoFetchStarted;
-    /** Why the auto-fetch left `status` at null. Cleared by the next successful get()/request(). */
-    readonly error: Signal<Error | null>;
-    connect(): Signal<PermissionResponse | null>;
-    get(): Promise<PermissionResponse>;
-    request(): Promise<PermissionResponse>;
+export declare class PermissionsService extends PermissionsServiceBase<PermissionResponse> {
+    constructor();
     static ɵfac: i0.ɵɵFactoryDeclaration<PermissionsService, never>;
     static ɵprov: i0.ɵɵInjectableDeclaration<PermissionsService>;
 }

package/build-ngc/angular/services/permissions.service/index.js

@@ -1,49 +1,11 @@
-// Angular twin of React's usePermissions hook and Vue's usePermissions composable.
-// `connect()` auto-fetches once (no ongoing subscription to clean up, so no Injector/effect
-// needed, unlike BatteryStateService) and returns a readonly signal; get()/request() are
-// imperative one-shot methods.
-//
-//   readonly status = inject(PermissionsService).connect();
-//   // template: {{ status()?.granted }}
-//
-// The auto-fetch has nobody to reject to, so its failure lands in the `error` signal instead of
-// escaping as an unhandled rejection: a null status with a non-null error is how a consumer tells
-// "the fetch failed" from "not fetched yet". get()/request() still reject to their direct caller —
-// only the automatic call is made safe.
-import { Injectable, signal } from '@angular/core';
+// Angular twin of React's `usePermissions`: `inject(PermissionsService).connect()` gives a signal
+import { Injectable } from '@angular/core';
+import { PermissionsServiceBase } from '@symbiote-native/angular';
 import { getPermissionsAsync, requestPermissionsAsync, } from '../../../core';
 import * as i0 from "@angular/core";
-export class PermissionsService {
-    status = signal(null, /* @ts-ignore */
-    ...(ngDevMode ? [{ debugName: "status" }] : /* istanbul ignore next */ []));
-    fetchError = signal(null, /* @ts-ignore */
-    ...(ngDevMode ? [{ debugName: "fetchError" }] : /* istanbul ignore next */ []));
-    isAutoFetchStarted = false;
-    /** Why the auto-fetch left `status` at null. Cleared by the next successful get()/request(). */
-    error = this.fetchError.asReadonly();
-    connect() {
-        // Latched rather than guarded on `status() === null`: a failed fetch leaves status null
-        // forever, so the old guard turned every later connect() into another native call — unbounded
-        // once connect() is reached from a change-detected expression instead of a field initializer.
-        if (!this.isAutoFetchStarted) {
-            this.isAutoFetchStarted = true;
-            this.get().catch((cause) => {
-                this.fetchError.set(cause instanceof Error ? cause : new Error(String(cause)));
-            });
-        }
-        return this.status.asReadonly();
-    }
-    async get() {
-        const response = await getPermissionsAsync();
-        this.status.set(response);
-        this.fetchError.set(null);
-        return response;
-    }
-    async request() {
-        const response = await requestPermissionsAsync();
-        this.status.set(response);
-        this.fetchError.set(null);
-        return response;
+export class PermissionsService extends PermissionsServiceBase {
+    constructor() {
+        super(getPermissionsAsync, requestPermissionsAsync);
     }
     static ɵfac = i0.ɵɵngDeclareFactory({ minVersion: "12.0.0", version: "22.0.8", ngImport: i0, type: PermissionsService, deps: [], target: i0.ɵɵFactoryTarget.Injectable });
     static ɵprov = i0.ɵɵngDeclareInjectable({ minVersion: "12.0.0", version: "22.0.8", ngImport: i0, type: PermissionsService, providedIn: 'root' });
@@ -51,5 +13,5 @@ export class PermissionsService {
 i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "22.0.8", ngImport: i0, type: PermissionsService, decorators: [{
             type: Injectable,
             args: [{ providedIn: 'root' }]
-        }] });
+        }], ctorParameters: () => [] });
 //# sourceMappingURL=index.js.map

package/build-ngc/angular/services/permissions.service/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../src/angular/services/permissions.service/index.ts"],"names":[],"mappings":"AAAA,mFAAmF;AACnF,4FAA4F;AAC5F,yFAAyF;AACzF,+BAA+B;AAC/B,EAAE;AACF,4DAA4D;AAC5D,yCAAyC;AACzC,EAAE;AACF,gGAAgG;AAChG,kGAAkG;AAClG,mGAAmG;AACnG,wCAAwC;AACxC,OAAO,EAAE,UAAU,EAAE,MAAM,EAAe,MAAM,eAAe,CAAC;AAChE,OAAO,EACL,mBAAmB,EACnB,uBAAuB,GAExB,MAAM,eAAe,CAAC;;AAGvB,MAAM,OAAO,kBAAkB;IACZ,MAAM,GAAG,MAAM,CAA4B,IAAI;+EAAC,CAAC;IACjD,UAAU,GAAG,MAAM,CAAe,IAAI;mFAAC,CAAC;IACjD,kBAAkB,GAAG,KAAK,CAAC;IAEnC,gGAAgG;IACvF,KAAK,GAAyB,IAAI,CAAC,UAAU,CAAC,UAAU,EAAE,CAAC;IAEpE,OAAO;QACL,wFAAwF;QACxF,8FAA8F;QAC9F,8FAA8F;QAC9F,IAAI,CAAC,IAAI,CAAC,kBAAkB,EAAE,CAAC;YAC7B,IAAI,CAAC,kBAAkB,GAAG,IAAI,CAAC;YAC/B,IAAI,CAAC,GAAG,EAAE,CAAC,KAAK,CAAC,CAAC,KAAc,EAAE,EAAE;gBAClC,IAAI,CAAC,UAAU,CAAC,GAAG,CACjB,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,IAAI,KAAK,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,CAC1D,CAAC;YACJ,CAAC,CAAC,CAAC;QACL,CAAC;QACD,OAAO,IAAI,CAAC,MAAM,CAAC,UAAU,EAAE,CAAC;IAClC,CAAC;IAED,KAAK,CAAC,GAAG;QACP,MAAM,QAAQ,GAAG,MAAM,mBAAmB,EAAE,CAAC;QAC7C,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;QAC1B,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC1B,OAAO,QAAQ,CAAC;IAClB,CAAC;IAED,KAAK,CAAC,OAAO;QACX,MAAM,QAAQ,GAAG,MAAM,uBAAuB,EAAE,CAAC;QACjD,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;QAC1B,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC1B,OAAO,QAAQ,CAAC;IAClB,CAAC;uGAnCU,kBAAkB;2GAAlB,kBAAkB,cADL,MAAM;;2FACnB,kBAAkB;kBAD9B,UAAU;mBAAC,EAAE,UAAU,EAAE,MAAM,EAAE"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../src/angular/services/permissions.service/index.ts"],"names":[],"mappings":"AAAA,kGAAkG;AAElG,OAAO,EAAE,UAAU,EAAE,MAAM,eAAe,CAAC;AAC3C,OAAO,EAAE,sBAAsB,EAAE,MAAM,0BAA0B,CAAC;AAClE,OAAO,EACL,mBAAmB,EACnB,uBAAuB,GAExB,MAAM,eAAe,CAAC;;AAGvB,MAAM,OAAO,kBAAmB,SAAQ,sBAA0C;IAChF;QACE,KAAK,CAAC,mBAAmB,EAAE,uBAAuB,CAAC,CAAC;IACtD,CAAC;uGAHU,kBAAkB;2GAAlB,kBAAkB,cADL,MAAM;;2FACnB,kBAAkB;kBAD9B,UAAU;mBAAC,EAAE,UAAU,EAAE,MAAM,EAAE"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@symbiote-native/brightness",
-  "version": "3.0.1",
+  "version": "3.0.3",
   "description": "expo-brightness wrapped for SymbioteNative — one framework-agnostic core, built once and reachable from the React, Vue, Svelte, Solid, and Angular adapters. Screen brightness get/set, Android-only system-brightness-mode control, an iOS-only brightness-change listener, and permission get/request.",
   "license": "MIT",
   "repository": {
@@ -70,7 +70,7 @@
   },
   "dependencies": {
     "expo-brightness": "57.0.1",
-    "expo-modules-core": "57.0.5"
+    "expo-modules-core": "57.0.20"
   },
   "peerDependencies": {
     "@angular/core": ">=20",
@@ -80,12 +80,12 @@
     "solid-js": ">=1.9.0",
     "svelte": ">=5.56.0",
     "vue": ">=3.5.0",
-    "@symbiote-native/angular": "^3.1.1",
-    "@symbiote-native/engine": "^1.3.0",
-    "@symbiote-native/react": "^3.0.3",
-    "@symbiote-native/solid": "^3.0.3",
-    "@symbiote-native/svelte": "^3.0.3",
-    "@symbiote-native/vue": "^3.0.3"
+    "@symbiote-native/angular": "^3.2.0",
+    "@symbiote-native/engine": "^1.5.0",
+    "@symbiote-native/react": "^3.2.0",
+    "@symbiote-native/solid": "^3.1.0",
+    "@symbiote-native/svelte": "^3.1.0",
+    "@symbiote-native/vue": "^3.2.0"
   },
   "peerDependenciesMeta": {
     "@symbiote-native/angular": {
@@ -133,13 +133,13 @@
     "solid-js": "^1.9.14",
     "svelte": "^5.56.0",
     "typescript": "~6.0.0",
-    "@symbiote-native/angular": "3.1.1",
-    "@symbiote-native/engine": "1.3.0",
-    "@symbiote-native/react": "3.0.3",
-    "@symbiote-native/solid": "3.0.3",
-    "@symbiote-native/svelte": "3.0.3",
-    "@symbiote-native/test-utils": "0.4.3",
-    "@symbiote-native/vue": "3.0.3"
+    "@symbiote-native/angular": "3.2.0",
+    "@symbiote-native/engine": "1.5.0",
+    "@symbiote-native/react": "3.2.0",
+    "@symbiote-native/solid": "3.1.0",
+    "@symbiote-native/svelte": "3.1.0",
+    "@symbiote-native/test-utils": "0.4.6",
+    "@symbiote-native/vue": "3.2.0"
   },
   "scripts": {
     "typecheck": "tsc --build",

package/src/angular/services/permissions.service/index.ts

@@ -1,16 +1,7 @@
-// Angular twin of React's usePermissions hook and Vue's usePermissions composable.
-// `connect()` auto-fetches once (no ongoing subscription to clean up, so no Injector/effect
-// needed, unlike BatteryStateService) and returns a readonly signal; get()/request() are
-// imperative one-shot methods.
-//
-//   readonly status = inject(PermissionsService).connect();
-//   // template: {{ status()?.granted }}
-//
-// The auto-fetch has nobody to reject to, so its failure lands in the `error` signal instead of
-// escaping as an unhandled rejection: a null status with a non-null error is how a consumer tells
-// "the fetch failed" from "not fetched yet". get()/request() still reject to their direct caller —
-// only the automatic call is made safe.
-import { Injectable, signal, type Signal } from '@angular/core';
+// Angular twin of React's `usePermissions`: `inject(PermissionsService).connect()` gives a signal
+
+import { Injectable } from '@angular/core';
+import { PermissionsServiceBase } from '@symbiote-native/angular';
 import {
   getPermissionsAsync,
   requestPermissionsAsync,
@@ -18,40 +9,8 @@ import {
 } from '../../../core';
 
 @Injectable({ providedIn: 'root' })
-export class PermissionsService {
-  private readonly status = signal<PermissionResponse | null>(null);
-  private readonly fetchError = signal<Error | null>(null);
-  private isAutoFetchStarted = false;
-
-  /** Why the auto-fetch left `status` at null. Cleared by the next successful get()/request(). */
-  readonly error: Signal<Error | null> = this.fetchError.asReadonly();
-
-  connect(): Signal<PermissionResponse | null> {
-    // Latched rather than guarded on `status() === null`: a failed fetch leaves status null
-    // forever, so the old guard turned every later connect() into another native call — unbounded
-    // once connect() is reached from a change-detected expression instead of a field initializer.
-    if (!this.isAutoFetchStarted) {
-      this.isAutoFetchStarted = true;
-      this.get().catch((cause: unknown) => {
-        this.fetchError.set(
-          cause instanceof Error ? cause : new Error(String(cause)),
-        );
-      });
-    }
-    return this.status.asReadonly();
-  }
-
-  async get(): Promise<PermissionResponse> {
-    const response = await getPermissionsAsync();
-    this.status.set(response);
-    this.fetchError.set(null);
-    return response;
-  }
-
-  async request(): Promise<PermissionResponse> {
-    const response = await requestPermissionsAsync();
-    this.status.set(response);
-    this.fetchError.set(null);
-    return response;
+export class PermissionsService extends PermissionsServiceBase<PermissionResponse> {
+  constructor() {
+    super(getPermissionsAsync, requestPermissionsAsync);
   }
 }