simplejsble 0.0.35 → 0.0.36

package/NitroSimplejsble.podspec

@@ -11,8 +11,8 @@ Pod::Spec.new do |s|
   s.authors      = package["author"]
 
   s.platforms    = {
-    :ios => '13.4',
-    :osx => '10.13'
+    :ios => '15.8',
+    :osx => '13.0'
   }
 
   s.source = { :path => "." }

package/apple/SimpleBLE.xcframework/Info.plist

@@ -10,7 +10,7 @@
 			<key>HeadersPath</key>
 			<string>Headers</string>
 			<key>LibraryIdentifier</key>
-			<string>ios-arm64</string>
+			<string>ios-arm64-simulator</string>
 			<key>LibraryPath</key>
 			<string>libsimpleble.a</string>
 			<key>SupportedArchitectures</key>
@@ -19,6 +19,8 @@
 			</array>
 			<key>SupportedPlatform</key>
 			<string>ios</string>
+			<key>SupportedPlatformVariant</key>
+			<string>simulator</string>
 		</dict>
 		<dict>
 			<key>BinaryPath</key>
@@ -43,7 +45,7 @@
 			<key>HeadersPath</key>
 			<string>Headers</string>
 			<key>LibraryIdentifier</key>
-			<string>ios-arm64-simulator</string>
+			<string>ios-arm64</string>
 			<key>LibraryPath</key>
 			<string>libsimpleble.a</string>
 			<key>SupportedArchitectures</key>
@@ -52,8 +54,6 @@
 			</array>
 			<key>SupportedPlatform</key>
 			<string>ios</string>
-			<key>SupportedPlatformVariant</key>
-			<string>simulator</string>
 		</dict>
 	</array>
 	<key>CFBundlePackageType</key>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "simplejsble",
-  "version": "0.0.35",
+  "version": "0.0.36",
   "description": "React Native Bluetooth Low Energy library using SimpleBLE with Nitro Modules",
   "main": "lib/index",
   "module": "lib/index",

package/android/SIMPLEDROIDBRIDGE_INTEGRATION.md

@@ -1,77 +0,0 @@
-# SimpleDroidBridge Integration Decision
-
-## Current Approach
-
-In `build.gradle`, the simpledroidbridge Java sources are included directly:
-
-```gradle
-sourceSets {
-  main {
-    java.srcDirs += ["../simpledroidbridge/src/main/java"]
-  }
-}
-```
-
-## Why Not Use `implementation project(":simpledroidbridge")`?
-
-### Option 1: `java.srcDirs` (Current)
-
-Compiles simpledroidbridge sources directly into the main library.
-
-**Pros:**
-- No configuration needed in consumer app
-- Works seamlessly in npm package context
-- No build config conflicts
-- React Native autolinking works out of the box
-
-**Cons:**
-- Sources compiled together (single output)
-
-### Option 2: `implementation project(":simpledroidbridge")`
-
-Would treat simpledroidbridge as a separate Gradle module dependency.
-
-**Pros:**
-- Cleaner separation of modules
-- Could be reused independently
-
-**Cons:**
-- Requires consumer app's `settings.gradle.kts` to include:
-  ```kotlin
-  include(":simpledroidbridge")
-  project(":simpledroidbridge").projectDir = File("node_modules/simplejsble/simpledroidbridge")
-  ```
-- `simpledroidbridge/build.gradle.kts` has its own SDK versions (`compileSdk = 31`, `minSdk = 31`) which may conflict with consumer apps
-- React Native autolinking doesn't handle transitive local project dependencies
-- Complex path resolution for npm packages
-
-## Comparison
-
-| Aspect | `java.srcDirs` | `project(":simpledroidbridge")` |
-|--------|----------------|--------------------------------|
-| Consumer setup | None required | Must modify settings.gradle |
-| Build config conflicts | None | Possible SDK version conflicts |
-| npm package compatibility | Works out of the box | Complex path resolution |
-| Autolinking | Works | Not supported |
-
-## Conclusion
-
-The `java.srcDirs` approach is the right choice for npm package distribution. Converting to a project dependency would add unnecessary friction for package consumers.
-
-## Package Structure
-
-The npm package bundles simpledroidbridge (defined in `package.json`):
-
-```json
-{
-  "files": [
-    "android/",
-    "simpledroidbridge/",
-    ...
-  ]
-}
-```
-
-This allows the relative path `../simpledroidbridge/src/main/java` to work correctly from the `android/` folder in both:
-- Monorepo development
-- npm package installation (`node_modules/simplejsble/`)