react-native-background-geolocation 4.15.2 → 4.16.1

package/ios/RNBackgroundGeolocation/TSLocationManager.xcframework/ios-arm64_x86_64-simulator/TSLocationManager.framework/_CodeSignature/CodeResources

@@ -46,7 +46,7 @@
 		</data>
 		<key>Headers/TSAuthorizationEvent.h</key>
 		<data>
-		Wn2hOqYVOsqarkCWuGd+3MDO/rU=
+		ShGAskjpRwHpN6rzYDc1Rkg4N2w=
 		</data>
 		<key>Headers/TSCallback.h</key>
 		<data>
@@ -138,7 +138,7 @@
 		</data>
 		<key>Info.plist</key>
 		<data>
-		9Ah+6zsh37uyMxc3a3M82claxog=
+		nUtA4kXT1L8G3cbyS8SfciSSpik=
 		</data>
 		<key>Miniball/Miniball.hpp</key>
 		<data>
@@ -148,6 +148,10 @@
 		<data>
 		ucUpjMCXhdSrrHC6f1a3/h7dQec=
 		</data>
+		<key>PrivacyInfo.xcprivacy</key>
+		<data>
+		eIiWJYOAAQYc3q8Z8126HoAj0sY=
+		</data>
 	</dict>
 	<key>files2</key>
 	<dict>
@@ -265,11 +269,11 @@
 		<dict>
 			<key>hash</key>
 			<data>
-			Wn2hOqYVOsqarkCWuGd+3MDO/rU=
+			ShGAskjpRwHpN6rzYDc1Rkg4N2w=
 			</data>
 			<key>hash2</key>
 			<data>
-			39Dl3JzmUFOB1jZ1UIcODGYk3u2bYiRCQBzFxE8K7j4=
+			yUaplVw0pzlGq5AFHHIXcJnT4+heZYnQ9PzTzLSwNEk=
 			</data>
 		</dict>
 		<key>Headers/TSCallback.h</key>
@@ -536,6 +540,17 @@
 			tYgWR9aNISh3EH0+KpcgrXdy/E0HZzDIQmvYu4csu9Y=
 			</data>
 		</dict>
+		<key>PrivacyInfo.xcprivacy</key>
+		<dict>
+			<key>hash</key>
+			<data>
+			eIiWJYOAAQYc3q8Z8126HoAj0sY=
+			</data>
+			<key>hash2</key>
+			<data>
+			Mqmebi7LJeFXux1wzarbNggySwBA8KVz+iSXJ/17rss=
+			</data>
+		</dict>
 	</dict>
 	<key>rules</key>
 	<dict>

package/ios/Resources/PrivacyInfo.xcprivacy

@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<!--
+   PrivacyInfo.xcprivacy
+   TSLocationManager
+
+   Created by Christopher Scott on 2024-03-20.
+   Copyright (c) 2024 Christopher Scott. All rights reserved.
+-->
+<plist version="1.0">
+<dict>
+    <key>NSPrivacyTrackingDomains</key>
+    <array/>
+
+    <key>NSPrivacyAccessedAPITypes</key>
+    <array>
+        <dict>
+            <key>NSPrivacyAccessedAPIType</key>
+            <string>NSPrivacyAccessedAPICategoryUserDefaults</string>
+
+            <key>NSPrivacyAccessedAPITypeReasons</key>
+            <array>
+                <string>CA92.1</string>
+                <string>1C8F.1</string>
+            </array>
+        </dict>
+    </array>
+
+    <key>NSPrivacyCollectedDataTypes</key>
+    <array/>
+
+    <key>NSPrivacyTracking</key>
+    <false/>
+</dict>
+</plist>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-background-geolocation",
-  "version": "4.15.2",
+  "version": "4.16.1",
   "description": "The most sophisticated cross-platform background location-tracking & geofencing module with battery-conscious motion-detection intelligence",
   "scripts": {
     "build": "yarn run build:expo",
@@ -30,7 +30,7 @@
   },
   "homepage": "https://www.transistorsoft.com/shop/products/react-native-background-geolocation",
   "dependencies": {
-    "react-native-background-fetch": "~4.2.1"
+    "react-native-background-fetch": "~4.2.5"
   },
   "devDependencies": {
     "@expo/config-plugins": "^4.1.0",

package/src/declarations/BackgroundGeolocation.d.ts

@@ -725,7 +725,7 @@ declare module "react-native-background-geolocation" {
     * });
     * ```
     *
-    * ### ⚠️ Warning: You must call `#ready` **once** and **only** once, each time your app is launched.
+    * ### ⚠️ Warning: You must call __`.ready(confg)`__ **once** and **only** once, each time your app is launched.
     * - Do not hide the call to `#ready` within a view which is loaded only by clicking a UI action.  This is particularly important
     * for iOS in the case where the OS relaunches your app in the background when the device is detected to be moving.  If you don't ensure that `#ready` is called in this case, tracking will not resume.
     *
@@ -733,6 +733,16 @@ declare module "react-native-background-geolocation" {
     *
     * If you wish, you can use the [[reset]] method to reset all [[Config]] options to documented default-values (with optional overrides):
     *
+    * ### [[Config.reset]]: false
+    *
+    * Configuring the plugin with __`reset: false`__ should generally be avoided unless you know *exactly* what it does.  People often find this from the *Demo* app.  If you do configure `reset: false`, you'll find that your `Config` provided to `.ready` is consumed **only at first launch after install**.  Thereafter, the plugin will ignore any changes you've provided there.  The only way to change the config then is to use [[setConfig]].
+    * 
+    * You will especially not want to use `reset: false` during development, while you're fine-tuning your `Config` options.
+    * 
+    * The reason the *Demo* app uses `reset: false` is because it hosts an advanced "*Settings*" screen to tune the `Config` at runtime and we don't want those runtime changes to be overwritten by `.ready(config)` each time the app launches.
+    * 
+    * ⚠️ If you *don't* undestand what __`reset: false`__ does, **NO NOT USE IT**.  If you blindly copy/pasted it from the *Demo* app, **REMOVE IT** from your `Config`.
+    *
     * @example
     * ```typescript
     * BackgroundGeolocation.reset();

package/src/declarations/interfaces/AuthorizationEvent.d.ts

@@ -14,9 +14,13 @@ declare module "react-native-background-geolocation" {
 	* ```
 	*/
 	interface AuthorizationEvent {
-		/**
-		* `true` when an authorization request to [[Authorization.refreshUrl]] was successful.
-		*/
+    /**
+     * HTTP Status returned from your [[Authorization.refreshUrl]] (or `0` if the HTTP request failed).
+     */
+    status:number;
+    /**
+    * `true` when an authorization request to [[Authorization.refreshUrl]] was successful.
+    */
 	  success: boolean;
 	  /**
 	  * When [[success]] is `false`, this is the error message from [[Authorization.refreshUrl]].  Otherwise, `null`.

package/.github/stale.yml

@@ -1,41 +0,0 @@
-# Configuration for probot-stale based on: https://github.com/facebook/react-native/blob/master/.github/stale.yml
-
- # Number of days of inactivity before an Issue or Pull Request becomes stale
-daysUntilStale: 60
-
- # Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
-daysUntilClose: 7
-
- # Issues or Pull Requests.
-exemptLabels:
-  - pinned
-  - security
-  - discussion
-
- # Set to true to ignore issues in a project (defaults to false)
-exemptProjects: false
-
- # Set to true to ignore issues in a milestone (defaults to false)
-exemptMilestones: false
-
- # Set to true to ignore issues with an assignee (defaults to false)
-exemptAssignees: false
-
- # Label to use when marking as stale
-staleLabel: stale
-
- # Comment to post when marking as stale. Set to `false` to disable
-markComment: >
-  This issue has been automatically marked as stale because it has not had
-  recent activity. It will be closed if no further activity occurs. Thank you
-  for your contributions. You may also mark this issue as a "discussion" and I
-  will leave this open.
- # Comment to post when closing a stale Issue or Pull Request.
-closeComment: >
-  Closing this issue after a prolonged period of inactivity. Fell free to reopen
-  this issue, if this still affecting you.
- # Limit the number of actions per hour, from 1-30. Default is 30
-limitPerRun: 30
-
- # Limit to only `issues` or `pulls`
-only: issues