@burnt-labs/expo-satya-attest 0.2.2 → 0.2.4

package/PUBLISHING.md

@@ -59,7 +59,7 @@ Build them from the module directory:
 ```bash
 cd platform_sdks/expo-satya-attest
 npm run build:native:android
-npm run build:native:ios
+SATYA_IOS_INCLUDE_SIMULATOR=1 npm run build:native:ios
 ```
 
 iOS artifacts can only be built on macOS with Xcode command line tools. Android artifacts
@@ -72,10 +72,9 @@ diagnostic unstripped iOS build:
 SATYA_IOS_STRIP=0 npm run build:native:ios
 ```
 
-By default, the iOS release build includes only the physical-device `arm64` slice. That
-is intentional: the real App Attest flow does not work on the iOS simulator, and shipping
-simulator slices makes the npm package much larger without helping the production claim
-path.
+Publishing builds include the physical-device `arm64` slice plus simulator slices so
+Expo development clients can install the SDK in simulator fallback flows. The real App
+Attest path still only works on physical devices.
 
 ## Release Checks
 
@@ -100,6 +99,7 @@ npm run clean
 npm run build
 npm run lint
 npm run test:providers
+npm run test:publishing-workflows
 npm run check:example
 npm run check:native-artifacts
 npm run check:pack
@@ -113,6 +113,7 @@ What each check covers:
 | `clean` + `build` | Rebuilds TypeScript output in `build/`. |
 | `lint` | Runs ESLint over `src/`. |
 | `test:providers` | Validates provider ids, template hashes, parser hashes, request match rules, HTTPS proof URLs, SNI, and SPKI pins. |
+| `test:publishing-workflows` | Confirms publish workflows build iOS artifacts with simulator slices and matching Rust targets. |
 | `check:example` | Type-checks the Expo example when its dependencies are installed. |
 | `check:native-artifacts` | Fails if Android `.so`, generated Kotlin, iOS XCFramework, or generated Swift glue are missing. |
 | `check:pack` | Runs `npm pack --dry-run --json` and verifies the actual tarball contents. |
@@ -294,8 +295,8 @@ Keep watching:
 - `npm run check:pack` for npm tarball and unpacked package size.
 - Whether every release includes only the ABIs you actually support.
 
-Current default iOS output includes only device `arm64`. If you need simulator artifacts
-for local fallback/debug work, opt in explicitly:
+Current local iOS output includes only device `arm64` unless you opt in explicitly.
+Publish workflows and release builds should use:
 
 ```bash
 SATYA_IOS_INCLUDE_SIMULATOR=1 npm run build:native:ios
@@ -307,8 +308,8 @@ For Apple-Silicon-simulator-only fallback builds:
 SATYA_IOS_SIMULATOR_TARGETS="aarch64-apple-ios-sim" npm run build:native:ios
 ```
 
-Do not publish simulator slices unless you intentionally support a simulator fallback
-experience. They are not useful for real App Attest verification.
+Simulator slices are only for simulator fallback and development-client installability;
+they are not useful for real App Attest verification.
 
 If the tarball becomes too large for npm or painful for app installs, the next design
 step is a binary-release model:

package/README.md

@@ -68,10 +68,10 @@ npm run build:native:ios
 npm run build:native:android
 ```
 
-`build:native:ios` strips local/debug symbols from the XCFramework and publishes a
-physical-device `arm64` iOS slice by default because the real App Attest flow does not
-work on simulator. See [`PUBLISHING.md`](./PUBLISHING.md) for optional simulator fallback
-builds and other binary-size knobs.
+`build:native:ios` strips local/debug symbols from the XCFramework. Local builds include
+the physical-device `arm64` iOS slice by default; publishing builds set
+`SATYA_IOS_INCLUDE_SIMULATOR=1` so simulator fallback slices ship too. See
+[`PUBLISHING.md`](./PUBLISHING.md) for release and binary-size knobs.
 
 Build TypeScript after editing `src/*.ts` or `src/*.tsx`:
 

package/android/build.gradle

@@ -4,13 +4,13 @@ plugins {
 }
 
 group = 'expo.modules.satyaattest'
-version = '0.2.2'
+version = '0.2.4'
 
 android {
   namespace "expo.modules.satyaattest"
   defaultConfig {
     versionCode 1
-    versionName "0.2.2"
+    versionName "0.2.4"
     // StrongBox key attestation needs API 28+; basic Keystore attestation API 24+.
     minSdkVersion 24
   }

package/ios/Frameworks/libsatya_ffi-rs.xcframework/Info.plist

@@ -20,6 +20,25 @@
 			<key>SupportedPlatform</key>
 			<string>ios</string>
 		</dict>
+		<dict>
+			<key>BinaryPath</key>
+			<string>libsatya_ffi.a</string>
+			<key>HeadersPath</key>
+			<string>Headers</string>
+			<key>LibraryIdentifier</key>
+			<string>ios-arm64_x86_64-simulator</string>
+			<key>LibraryPath</key>
+			<string>libsatya_ffi.a</string>
+			<key>SupportedArchitectures</key>
+			<array>
+				<string>arm64</string>
+				<string>x86_64</string>
+			</array>
+			<key>SupportedPlatform</key>
+			<string>ios</string>
+			<key>SupportedPlatformVariant</key>
+			<string>simulator</string>
+		</dict>
 	</array>
 	<key>CFBundlePackageType</key>
 	<string>XFWK</string>

package/ios/Frameworks/libsatya_ffi-rs.xcframework/ios-arm64_x86_64-simulator/Headers/module.modulemap

@@ -0,0 +1,7 @@
+module satya_ffiFFI {
+    header "satya_ffiFFI.h"
+    export *
+    use "Darwin"
+    use "_Builtin_stdbool"
+    use "_Builtin_stdint"
+}