maplibre-react-native
maplibre-react-native copied to clipboard
maplibre breaks expo-web-browser on iOS 18.2 (release build)
Describe and reproduce the Bug
- merely installing maplibre and adding it to
app.jsoncausesexpo-web-browserto hang on release builds - it seems to only happens on
iOS 18.2(works on17.5) - repo to reproduce https://github.com/mwmcode/maplibre-expo-web
same repo has a branch w/o maplibre that works fine
@maplibre/maplibre-react-native Version
10.0.1
Which platforms does this occur on?
iOS Simulator
Which frameworks does this occur on?
Expo
Which architectures does this occur on?
New Architecture
Environment
expo-env-info 1.2.2 environment info:
System:
OS: macOS 15.2
Shell: 3.7.1 - /opt/homebrew/Cellar/fish/3.7.1/bin/fish
Binaries:
Node: 22.13.1 - ~/n/bin/node
Yarn: 4.2.2 - ~/n/bin/yarn
npm: 10.9.0 - /opt/homebrew/bin/npm
Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.1 - /Users/mm/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
Android SDK:
API Levels: 30, 33, 34, 35
Build Tools: 30.0.3, 33.0.0, 33.0.1, 34.0.0, 35.0.0
System Images: android-29 | Google APIs ARM 64 v8a, android-30 | Google APIs ARM 64 v8a, android-31 | Google Play ARM 64 v8a, android-33 | Intel x86_64 Atom, android-33 | Google APIs ARM 64 v8a, android-34 | Google Play ARM 64 v8a
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12700392
Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
npmPackages:
expo: ~52.0.28 => 52.0.28
expo-router: ~4.0.17 => 4.0.17
react: 18.3.1 => 18.3.1
react-native: 0.76.6 => 0.76.6
npmGlobalPackages:
eas-cli: 14.5.0
Expo Workflow: bare
-
Expected behavior (on iOS 17.5)
-
Issue (on iOS 18.2)
Thanks for the report, can you test if it works fine on the old arch?
Just tried. Same result :\
"newArchEnabled": false,inapp.jsonexpo prebuild --clean- ... build and load onto
iOS 18.2emulator
result 👇 (could it be related to react-native-safe-area-context since it's going out of safe area view when this is happening?)
Hard to tell what's causring this. Are there any similar reports on the Expo repository regardin expo-web-browser?
The only potentially related issue I could see is this one re expo-web-browser not surfacing errors :\