This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@capacitor/background-runner@1.1.0
Minor Changes
142e96d: (iOS) KV: calling get on an non-existent key returns null instead of empty object
(iOS) Fixed an issue within Runner that could potentially cause EXC_BAD_ACCESS crashes
18f72b6: More reliability fixes for the JS Engine used in the Background Runner:
(Android) Fixes in runtime during background execution
(Android) Improvements in native lib handling for testing
When updating, if you have an existing Android app, be sure to delete the android-js-engine-release.aar from android/src/main/libs, and add the following to android/app/build.gradle:
d6511b2: (Android): Fixing issue that disabled appStateChange events
b09f30e: Reliability fixes for the JS Engine used in the Background Runner:
(Android) Improvements to QuickJS integration
(Android / iOS) Improvements in the handling of multiple dispatched events
Patch Changes
174f2fe: Fixing incorrect method name in CapacitorGeolocation
11124d2: (iOS): Removing unnecessary run loop thread causing spike in CPU while the app was in the foreground
android-js-engine@1.1.0
Minor Changes
18f72b6: More reliability fixes for the JS Engine used in the Background Runner:
(Android) Fixes in runtime during background execution
(Android) Improvements in native lib handling for testing
When updating, if you have an existing Android app, be sure to delete the android-js-engine-release.aar from android/src/main/libs, and add the following to android/app/build.gradle:
142e96d: (iOS) KV: calling get on an non-existent key returns null instead of empty object
(iOS) Fixed an issue within Runner that could potentially cause EXC_BAD_ACCESS crashes
Patch Changes
11124d2: (iOS): Removing unnecessary run loop thread causing spike in CPU while the app was in the foreground
All notable changes to this project will be documented in this file.
See Conventional Commits for commit guidelines.
example-app@1.0.6
Patch Changes
Updated dependencies [174f2fe]
Updated dependencies [11124d2]
Updated dependencies [142e96d]
Updated dependencies [18f72b6]
Updated dependencies [d6511b2]
Updated dependencies [b09f30e]
@capacitor/background-runner@1.1.0
All notable changes to this project will be documented in this file.
See Conventional Commits for commit guidelines.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@capacitor/background-runner@1.1.0
Minor Changes
142e96d: (iOS) KV: calling
get
on an non-existent key returns null instead of empty object (iOS) Fixed an issue within Runner that could potentially cause EXC_BAD_ACCESS crashes18f72b6: More reliability fixes for the JS Engine used in the Background Runner:
When updating, if you have an existing Android app, be sure to delete the
android-js-engine-release.aar
fromandroid/src/main/libs
, and add the following toandroid/app/build.gradle
:d6511b2: (Android): Fixing issue that disabled
appStateChange
eventsb09f30e: Reliability fixes for the JS Engine used in the Background Runner:
Patch Changes
android-js-engine@1.1.0
Minor Changes
18f72b6: More reliability fixes for the JS Engine used in the Background Runner:
When updating, if you have an existing Android app, be sure to delete the
android-js-engine-release.aar
fromandroid/src/main/libs
, and add the following toandroid/app/build.gradle
:ios-engine@1.1.0
Minor Changes
get
on an non-existent key returns null instead of empty object (iOS) Fixed an issue within Runner that could potentially cause EXC_BAD_ACCESS crashesPatch Changes
All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.
example-app@1.0.6
Patch Changes
All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.