@marktiderman/genesis-native 0.4.1 → 0.4.2

package/README.md

@@ -454,6 +454,19 @@ typed text, the link and the notifier's notification id. A backend that sets
 `usesInstallationId` gets this install's id (made once, kept across sign-ins)
 as `register`'s fourth argument; `supabasePushBackend` doesn't.
 
+An app with its own device functions (its own `register` / `forget` RPCs) doesn't
+stub `loadPreferences` / `savePreferences`: it spreads in the notifier's, and
+Settings → Notifications works.
+
+```ts
+import { notificationsPushPreferences } from "@marktiderman/genesis-notifications/native";
+
+const backend: PushBackend = { register, forget, ...notificationsPushPreferences(supabase) };
+```
+
+Spread it after your own keys: a `loadPreferences` or `savePreferences` written later in the object
+replaces its functions.
+
 ```ts
 // lib/push.ts
 import * as Notifications from "expo-notifications";
@@ -624,9 +637,22 @@ What it sets:
   minimum iOS and team. The app embeds it and depends on it.
 - **EAS:** `extra.eas.build.experimental.ios.appExtensions`. The extension is
   a separate bundle id, so it needs its own provisioning profile. EAS Build
-  reads this entry and creates the App ID, its capability and the profile with
-  the app's. You don't create them by hand. A local `expo run:ios` on a device
-  needs an Apple team (`ios.appleTeamId`) that can sign both.
+  reads this entry and registers the extension's App ID with the app's, but on
+  a first build its capability sync can fail ("invalid value at
+  bundleIdCapabilities attributes") and leave the extension without a profile.
+  Before the first build with the plugin, once per app:
+  1. In the Apple developer portal (Certificates, Identifiers & Profiles →
+     Identifiers), open the `<bundle id>.NotificationService` App ID (create it
+     if EAS hasn't) and enable **Communication Notifications**. Leave it off
+     with `communication: false`.
+  2. From a checkout that has the plugin in its app config, run
+     `eas credentials --platform ios`, pick the **production** profile, then
+     **Build Credentials** → **All: Set up all the required credentials to
+     build your project**. EAS makes the extension's provisioning profile
+     (and the app's, if missing) with that capability.
+
+  After that, EAS Build reuses the profiles. A local `expo run:ios` on a
+  device needs an Apple team (`ios.appleTeamId`) that can sign both.
 
 **The payload contract.** The sender sets `mutableContent: true`, or the
 extension never runs. `richPushMessage(message, { image, senderAvatar })`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@marktiderman/genesis-native",
-  "version": "0.4.1",
+  "version": "0.4.2",
   "private": false,
   "type": "module",
   "sideEffects": false,
@@ -76,10 +76,10 @@
     "README.md"
   ],
   "dependencies": {
-    "@marktiderman/genesis-core": "^1.9.0",
+    "@marktiderman/genesis-core": "^1.10.0",
     "@marktiderman/genesis-design-system": "^1.5.0",
-    "@marktiderman/genesis-features": "^0.4.0",
-    "@marktiderman/genesis-ui-native": "^2.4.1"
+    "@marktiderman/genesis-features": "^0.4.1",
+    "@marktiderman/genesis-ui-native": "^2.5.0"
   },
   "peerDependencies": {
     "@tanstack/query-async-storage-persister": "^5.0.0",