Release 1.0.5#56
Merged
Merged
Conversation
Merge 'master' into 'develop' after release
…example Bump plugin version in example to 1.0.4
Migrate examples/MindboxExpoExample from SDK 54 to SDK 55:
- Bump expo to ^55.0.0; align managed deps via `expo install --fix`
(react 19.2.0, react-native 0.83.6, expo-* on ~55.0.x,
react-native-screens ~4.23.0, react-native-safe-area-context ~5.6.2)
- Bump @types/react to ~19.2.0
- Drop obsolete devDeps: @react-native-community/cli (RN 0.83
ships its own CLI) and @types/react-native (types are bundled
with react-native since 0.71)
- Remove `newArchEnabled` from app.json (default since SDK 53)
- Remove `edgeToEdgeEnabled` from android config (mandatory in SDK 55)
- Regenerate yarn.lock
Verified with `npx expo-doctor` (18/18) and `npx expo config`.
The plugin itself (mindbox-expo-plugin) is left on @expo/config-plugins
^54 — this change scope is example-only.
expo-notifications@55.0.0 renamed its iOS pod from `EXNotifications` to `ExpoNotifications` (expo/expo#42009), so the previous `import EXNotifications` injected by withMindboxIos breaks the build on SDK 55. Additionally, the SDK 55 AppDelegate template declares `internal import Expo`, which under Swift's SE-0409 access-level imports rule requires all imports of the same module to be consistent. Wrap the injected import in `#if canImport(ExpoNotifications)`: - SDK 55: `internal import ExpoNotifications` (matches Expo's access level) - SDK 54 and earlier: `import EXNotifications` (unchanged) Verified: example project (SDK 55, RN 0.83, Xcode 26.5, iOS 26.5 simulator) compiles, links, signs, and installs successfully.
Upgrade to expo 55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated PR: merge
release/1.0.5intomasterVersions:
1.0.5