Bump xmldom, plist and react-native-background-geolocation

[dependabot]

Removes xmldom. It's no longer used after updating ancestor dependencies xmldom, plist and react-native-background-geolocation. These dependencies need to be updated together.

Removes xmldom

Updates plist from 3.0.1 to 3.0.6

Changelog

Sourced from plist's changelog.

3.0.5 / 2022-03-23

• [96e2303d05] Prototype Pollution using .parse() #114 (mario-canva)
• update browserify from 16 to 17

3.0.4 / 2021-08-27

• inline xmldom@0.6.0 to eliminate security warning false positive (Mike Reinstein)

3.0.3 / 2021-08-04

• update xmldom to 0.6.0 to patch critical vulnerability (Mike Reinstein)
• remove flaky saucelabs teseting badge (Mike Reinstein)

3.0.2 / 2021-03-25

• update xmldom to 0.5.0 to patch critical vulnerability (Mike Reinstein)
• update saucelab credentials to point at mreinstein's saucelabs account (Mike Reinstein)
• remove a bunch of test versions from the matrix because they weren't working in zuul + sauce (Mike Reinstein)

Commits

• See full diff in compare view

Updates react-native-background-geolocation from 3.7.0 to 4.9.3

Changelog

Sourced from react-native-background-geolocation's changelog.

4.9.3 — 2022-10-26

• [Android] Fix logic error with getCurrentPosition not respecting timeout.

4.9.2 — 2022-10-25

• [Android] play-services:location has introduced a breaking change in v21, breaking the plugin. googlePlayServicesLocationVersion will be capped with a maximum of v20. The next major release (4.10.0) will set a minimum required version of v21.
• [Expo] The plugin now implements an Expo plugin for automated Setup.
• [iOS] Fix bug in iOS scheduler firing on days where it should not.
• [iOS] Rebuild TSLocationManager.xcframework with XCode 13 (instead of XCode 14).
• [Android] Add new Config Notification.channelId for custom customizing the NotificationChannel id. Some use rs have an existing foreground-service and NotificationChannel so wish to have the plugin's foreground-service s share the same notification and channel. This option should generally not be used.
• [Android] Add permission android.permission.POST_NOTIFICATIONS for Android 13 (targetSdkVersion 33). Requ ired to allow enabling notifications in Settings->Apps.
• [Android] Add new Config option Authorization.refreshHeaders for full control over HTTP headers sent to Author ization.refreshUrl when refreshing auth token.
• [Android] Add null check when executing PowerManager.isPowerSaveMode()
• [Android] Add new Config.disableProviderChangeRecord (default false) to allow disabling the automatical HTTP POST of the onProviderChange location record. Some users do not want this automatically uploaded locatio n whenever the state of location-services is changed (eg: Location-services disabled, Airplane mode, etc).
• [Android] Fix bug with disableMotionActivityUpdates: true and calling .start() followed immediately by .changePace(true). The SDK would fail to enter the moving state, entering the stationary state instead.
• [iOS] Add new iOS 15 CLLocation attribute Location.ellipsoidal_altitude The altitude as a height above the World Geodetic System 1984 (WGS84) ellipsoid, measured in meters. Android Location.altitude has always returned ellipsoidal altutude, so both Location.altitude and Location.ellipsoidal_altitude will return the same value.

4.8.2 — 2022-08-08

• [Android] Fix java.lang.IllegalArgumentException TSProviderManager.handleProviderChangeEvent`.
• [Android] startOnBoot: false with stopOnTerminate: false could start-on-boot.
• [Android] State.enabled returned by calling .stop() returns true due to implementation running in a background-thread but callback executed immediately on the main-thread. However, requesting .getState() immediately after calling .stop would return the correct value of State.enabled
• [Android] Fix notification.sticky not being respected.

4.8.1 — 2022-06-28

• Fix issue for react-native 0.69: They made a breaking change with the old, unused react-native.config.js, causing builds to fail. Simply delete the file react-native.config.js.

4.8.0 — 2022-06-21

• [Android] Fix bug in onProviderChange event: not properly detecting when location-services disabled.
• [Android] Android 12: Guard Context.startForegroundService with try / catch: the plugin will now catch exception ForegroundServiceStartNotAllowedException and automatically retry with an AlarmManager oneShot event.
• [Android] Android 12: Refactor foreground-service management for Android 12: A way has been found to restore the traditional behaviour of foreground-services, allowing them to stop when no longer required (eg: where the plugin is in the stationary state).
• [Android] Refactor application life-cycle management. Remove deprecated permission android.permission.GET_TASKS traditionally used for detecting when the app has been terminated. The new life-cycle mgmt system can detect Android headless-mode in a much more elegant manner.
• [Android] Better handling for WhenInUse behaviour: The plugin will not allow .changePace(true) to be executed when the app is in the background (since Android forbids location-services to initiated in the background with WhenInUse).
• [Android] Refactor useSignificantChangesOnly behaviour. Will use a default motionTriggerDelay with minimum 60000ms, minimum distanceFilter: 250 and enforced stopTimeout: 20.
• [iOS] iOS 15 has finally implemented Mock Location Detection. location.mock will now be present for iOS when the location is mocked, just like Android.
• [Android] Re-factor onProviderChange. Add broadcast-receiver for AIRPLANE_MODE detection.
• [Android] Add guard against Android 12 issue where location-services fail to turn off after terminate and plugin enters stationary state.
• [Android] Prevent recording motionchange position from running after onProviderChange.
• [Android] Fix bug in Android 12 support for executing .start() in background while terminated. Used JobScheduler ONESHOT instead of AlarmManager.
• [Android] Plugin could be placed into an infinite loop requesting motionchange position in some cases.
• [Android] Address ConcurrentModificationException in onPermissionGranted.

4.7.1 — 2022-05-12

• [Android] If on device reboot location-services fails to provide a location (eg: timeout, airplane mode), the plugin would rely on motion API events to try again. This is a problem if the motion api is disabled. Instead, the SDK will keep trying to retrieve a location.
• [Android] Android 12 support for ForegroundServiceStartNotAllowedException: immediately launch the SDK's TrackingService as soon as .start() executes. If a location-timeout occurs while fetching the onMotionChange position after device reboot with startOnBoot: true, the ForegroundServiceStartNotAllowedException could be raised.
• [Android] Add two new attributes android:enabled and android:permission to the SDK's built-in BootReceiver:

</tr></table> 

... (truncated)

Commits

• 855f564 Merge pull request #1578 from transistorsoft/getCurrentPosition-timeout
• b53ff3a Re-generate docs
• 7745b68 [Android] Fix logic error with getCurrentPosition timeout not being respected
• abb3a4f Update INSTALL-EXPO.md
• 832fb33 Update INSTALL-EXPO.md
• e5d845c Merge branch 'setup'
• cc2c023 Expo Setup
• 5af054d Merge branch 'setup'
• 6693e40 Copy Expo background-fetch Setup into background-geolocation setup
• 557b96e Merge branch 'release-4.9.2'
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.