@woosmap/react-native-plugin-geofencing 1.0.0-beta.2 → 1.0.0-beta.3

package/CHANGELOG.md

@@ -1,5 +1,5 @@
 ## 1.0.0
-- Enhancement: Introduced the `WoosmapGeofencingTurbo` TurboModule (New Architecture). The region-CRUD and key/radius methods — `addRegion`, `removeRegions`, `getRegions`, `setPoiRadius`, and `setWoosmapApiKey` — now dispatch through the generated codegen path. All other methods continue to flow through the legacy `PluginGeofencing` module. The public JS API is unchanged.
+- Enhancement: Completed the `WoosmapGeofencingTurbo` TurboModule migration (New Architecture). The module now extends `RCTEventEmitter` so it can both expose native methods and fire JS events, making `NativeEventEmitter(WoosmapGeofencingTurbo)` the single event source. All 33 methods — including `initialize`, `requestPermissions`, `requestBLEPermissions`, `requestNotificationPermissions`, `watchLocation`, `watchRegions`, and their clear variants — now dispatch through the generated codegen path. The legacy `PluginGeofencing` module (iOS `PluginGeofencing.swift`/`.mm` and Android `PluginGeofencingModule`/`PluginGeofencingPackage`) has been removed now that all methods live on the TurboModule. The public JS API is unchanged.
 
 ## 0.14.0
 - Breaking: Raised minimum supported React Native to `0.85.x`; React `19.2.3`.

package/README.md

@@ -19,12 +19,3 @@ If you are looking for the Woosmap Geofencing React Native plugin documentation,
 - iOS `>=15.1`
 - Android: JDK 17, `minSdk` 24, `compileSdk`/`targetSdk` 36
 - Node.js `>=22`
-
-### React Native architectures
-
-This release supports both the legacy bridge and the New Architecture (Fabric / TurboModules):
-
-- **Legacy bridge** (`newArchEnabled=false` on Android, `RCT_NEW_ARCH_ENABLED=0` on iOS): the plugin is loaded natively as before.
-- **New Architecture** (`newArchEnabled=true` / `RCT_NEW_ARCH_ENABLED=1`): the plugin is loaded through React Native's **interop layer**. No additional setup is required in your app — the plugin's native modules and event emitters are automatically wrapped as TurboModule-compatible instances at runtime.
-
-A full TurboModule / Fabric-native rewrite is planned for a future major release. Until then, consumer apps can opt into the New Architecture without any changes to how they consume this plugin.

package/android/build.gradle

@@ -48,7 +48,7 @@ def supportsNamespace() {
 
 android {
   if (supportsNamespace()) {
-    namespace "com.reactnativeplugingeofencing"
+    namespace "com.woosmap.reactnativeplugingeofencing"
 
     sourceSets {
       main {

package/android/src/main/java/com/{reactnativeplugingeofencing → woosmap/reactnativeplugingeofencing}/AbstractPushHelper.java

@@ -1,4 +1,4 @@
-package com.reactnativeplugingeofencing;
+package com.woosmap.reactnativeplugingeofencing;
 
 import java.util.Map;
 

package/android/src/main/java/com/{reactnativeplugingeofencing → woosmap/reactnativeplugingeofencing}/AirshipPushHelper.java

@@ -1,4 +1,4 @@
-package com.reactnativeplugingeofencing;
+package com.woosmap.reactnativeplugingeofencing;
 
 import android.content.Context;
 import android.util.Log;

package/android/src/main/java/com/{reactnativeplugingeofencing → woosmap/reactnativeplugingeofencing}/WoosLocationReadyListener.java

@@ -1,4 +1,4 @@
-package com.reactnativeplugingeofencing;
+package com.woosmap.reactnativeplugingeofencing;
 
 import android.location.Location;
 import com.facebook.react.bridge.ReactApplicationContext;

package/android/src/main/java/com/{reactnativeplugingeofencing → woosmap/reactnativeplugingeofencing}/WoosRegionReadyListener.java

@@ -1,4 +1,4 @@
-package com.reactnativeplugingeofencing;
+package com.woosmap.reactnativeplugingeofencing;
 
 import com.facebook.react.bridge.ReactApplicationContext;
 import com.facebook.react.modules.core.DeviceEventManagerModule;