[dependabot]

Bumps expo from 57.0.28 to 58.0.19.

Release notes

Sourced from expo's releases.

expo-location@58.0.19

Patch Changes

• [Android] Use jsLogger for logging where possible, add more logs in silent failure spots. (#51987 by @​HubertBer)

expo-modules-jsi@58.0.19

Patch Changes

• [iOS] Add JavaScriptObject.tryUnsetNativeState(), which returns false when the native state can't be removed, for example from a frozen object. unsetNativeState() now ignores that case instead of raising a C++ exception that Swift can't catch. (#52095 by @​tsapeta)

expo@58.0.19

Patch Changes

• Updated dependencies. (#52096)
  • expo-modules-core@58.0.26

expo-asset@58.0.18

Patch Changes

• Updated dependencies.
  • expo-constants@58.0.13

expo-updates@58.0.18

Patch Changes

• Updated dependencies. (#51946)
  • @​expo/env@​2.5.3

expo-modules-jsi@58.0.17

Patch Changes

• [iOS] Write the generated jsi module map under EXPO_CUSTOM_BUILD_ROOT when it is set, so a custom build writes nothing into the package directory. Without it, the module map stays at apple/.generated/module.modulemap. (#51588 by @​chrfalch)

• [iOS] Publish the ExpoModulesJSI ABI descriptor with the package, at prebuilds/abi/ExpoModulesJSI/arm64-apple-ios-simulator.abi.json. (#51835 by @​alanjhughes)

• [iOS] Build ExpoModulesJSI during the Xcode build of a Swift Package Manager app, against the app's React Native. Expo source packages compile against the ExpoModulesJSIHeaders XCFramework that expo-modules-jsi ships, and the new "Build ExpoModulesJSI" build phase runs a script in expo-modules-jsi that builds, links and embeds the framework.

  The build phase copies the framework's dSYM to the app's dSYM folder, so archives symbolicate ExpoModulesJSI crashes.

  Sync fails with an error that names both versions when the ExpoModulesJSIHeaders XCFramework comes from another version of expo-modules-jsi than the installed sources.

  (#51588 by @​chrfalch)

• [iOS] Add JavaScriptObject.setProperty(_:value:) and JavaScriptObject.withUnownedProperty(_:_:) overloads that take a JavaScriptPropNameID. JavaScriptPropNameID.init(_:string:) now borrows the runtime, so code that only borrows a runtime can create property names without copying it. (#51905 by @​tsapeta)

expo@58.0.17

Patch Changes

• Resolve expo/tsconfig.base in tools that follow package.json exports. (#51751 by @​daemosity)

• [iOS] Build ExpoModulesJSI during the Xcode build of a Swift Package Manager app, against the app's React Native. Expo source packages compile against the ExpoModulesJSIHeaders XCFramework that expo-modules-jsi ships, and the new "Build ExpoModulesJSI" build phase runs a script in expo-modules-jsi that builds, links and embeds the framework.

  The build phase copies the framework's dSYM to the app's dSYM folder, so archives symbolicate ExpoModulesJSI crashes.

... (truncated)

Changelog

Sourced from expo's changelog.

58.0.19

Patch Changes

• Updated dependencies. (#52096)
  • expo-modules-core@58.0.26

58.0.18

Patch Changes

• [iOS] A buildFromSource pattern such as ".*" no longer fails the SwiftPM sync when it matches a module that Swift Package Manager cannot build from source, ExpoModulesCore included: the plugin links that module precompiled and prints one warning naming it. An entry that names such a module exactly still fails the sync. (#52073 by @​chrfalch)
• [iOS] The SwiftPM plugin links an Expo module's precompiled XCFramework whenever one exists, unless the app lists the module in its buildFromSource autolinking option, which the plugin now honours as CocoaPods does. A module built from source whose checked-in Package.swift depends on the ExpoModulesCoreHeaders product is built from that manifest as it stands. (#51661 by @​chrfalch)
• Updated dependencies. (#52017, #51966, 4a6ae65, #52093, #51934, #51922, #52124, #52123, #51782, #51961)
  • expo-modules-autolinking@58.0.15
  • expo-modules-core@58.0.25
  • @​expo/config@​58.0.8
  • expo-font@58.0.10
  • expo-file-system@58.0.11
  • expo-modules-cli@0.3.2
  • @​expo/cli@​58.1.15
  • @​expo/local-build-cache-provider@​58.0.8
  • @​expo/metro-config@​58.0.17
  • babel-preset-expo@58.0.20

58.0.17

Patch Changes

• Resolve expo/tsconfig.base in tools that follow package.json exports. (#51751 by @​daemosity)

• [iOS] Build ExpoModulesJSI during the Xcode build of a Swift Package Manager app, against the app's React Native. Expo source packages compile against the ExpoModulesJSIHeaders XCFramework that expo-modules-jsi ships, and the new "Build ExpoModulesJSI" build phase runs a script in expo-modules-jsi that builds, links and embeds the framework.

  The build phase copies the framework's dSYM to the app's dSYM folder, so archives symbolicate ExpoModulesJSI crashes.

  Sync fails with an error that names both versions when the ExpoModulesJSIHeaders XCFramework comes from another version of expo-modules-jsi than the installed sources.

  (#51588 by @​chrfalch)

• Updated dependencies. (#50388, #51872, #51946, #51986, #51730, #51854, #51905, #51923, #51906, #51504, #51937, #52008, #51868, #51932, #51714, #51913)

  • expo-modules-autolinking@58.0.14
  • @​expo/cli@​58.1.14
  • @​expo/config-plugins@​58.0.10
  • expo-modules-core@58.0.24
  • @​expo/fingerprint@​0.21.6
  • @​expo/metro-config@​58.0.16
  • @​expo/log-box@​58.0.13
  • @​expo/config@​58.0.7
  • expo-constants@58.0.13
  • babel-preset-expo@58.0.19
  • @​expo/local-build-cache-provider@​58.0.7

... (truncated)

Commits

• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[github-actions]

👋 Hello @dependabot[bot]! Thank you for contributing to FINORA 🎬.

To ensure high code quality, our automated bot noticed a few missing details:

• ⚠️ Incomplete checklist: Please check at least the applicable boxes in the quality & security checklist.

👉 Please edit your Pull Request description to complete these items.