| #
489c2041 |
| 15-Sep-2023 |
Will Schurman <[email protected]> |
[ios] Remove legacy notifications module code (#24325)
|
| #
19a0af8d |
| 15-Sep-2023 |
Will Schurman <[email protected]> |
[go] Load embedded bundle and manifest in release builds (#24412)
|
| #
b8addc5d |
| 11-Sep-2023 |
Will Schurman <[email protected]> |
[ios] Remove dead code (#24316)
|
| #
5f54863a |
| 08-Sep-2023 |
Will Schurman <[email protected]> |
[tools] Switch expo home publishing to EAS update (#24216)
|
| #
529650a2 |
| 06-Sep-2023 |
Kudo Chien <[email protected]> |
[go] fix ios expo go crash from exceptions (#24305)
# Why
potentially to fix the strange ios crash after login
# How
- the root cause is that we didn't implement correct `RCTExceptionsManag
[go] fix ios expo go crash from exceptions (#24305)
# Why
potentially to fix the strange ios crash after login
# How
- the root cause is that we didn't implement correct `RCTExceptionsManagerDelegate` protocol from react-native upgrade. that would probably cause the error stacktrace:
```
Last Exception Backtrace:
0 CoreFoundation 0x1c938ce38 __exceptionPreprocess + 164 (NSException.m:202)
1 libobjc.A.dylib 0x1c25238d8 objc_exception_throw + 60 (objc-exception.mm:356)
2 CoreFoundation 0x1c950181c -[NSObject(NSObject) doesNotRecognizeSelector:] + 136 (NSObject.m:140)
3 CoreFoundation 0x1c93a2ce8 ___forwarding___ + 976 (NSForwarding.m:3620)
4 CoreFoundation 0x1c940b320 _CF_forwarding_prep_0 + 96 (:-1)
5 Expo Go 0x105588678 -[RCTExceptionsManager reportSoft:stack:exceptionId:extraDataAsJSON:] + 244 (RCTExceptionsManager.mm:50)
6 Expo Go 0x105589010 -[RCTExceptionsManager reportException:] + 1320 (RCTExceptionsManager.mm:156)
7 CoreFoundation 0x1c93f76b4 __invoking___ + 148 (:-1)
8 CoreFoundation 0x1c93a3b1c -[NSInvocation invoke] + 428 (NSForwarding.m:3377)
9 CoreFoundation 0x1c93a3534 -[NSInvocation invokeWithTarget:] + 64 (NSForwarding.m:3474)
10 Expo Go 0x105542a60 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 388 (RCTModuleMethod.mm:584)
11 Expo Go 0x105544ac0 facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 456 (RCTNativeModule.mm:197)
12 Expo Go 0x105544710 facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int)::$_0::operator()() const + 68 (RCTNativeModule.mm:114)
13 Expo Go 0x105544710 invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 112 (RCTNativeModule.mm:105)
14 libdispatch.dylib 0x1d09a3460 _dispatch_call_block_and_release + 32 (init.c:1518)
15 libdispatch.dylib 0x1d09a4f88 _dispatch_client_callout + 20 (object.m:560)
16 libdispatch.dylib 0x1d09ac640 _dispatch_lane_serial_drain + 672 (inline_internal.h:2632)
17 libdispatch.dylib 0x1d09ad18c _dispatch_lane_invoke + 384 (queue.c:3940)
18 libdispatch.dylib 0x1d09b7e10 _dispatch_workloop_worker_thread + 652 (queue.c:6876)
19 libsystem_pthread.dylib 0x217604df8 _pthread_wqthread + 288 (pthread.c:2618)
20 libsystem_pthread.dylib 0x217604b98 start_wqthread + 8 (:-1)
```
- add `-Werror=protocol` to have compiler error if we don't implement correct protocol in the future.
# Test Plan
expo go release build + local build production home with some `console.error()`
show more ...
|
| #
3273f84b |
| 12-Aug-2023 |
Alan Hughes <[email protected]> |
[sqlite] Address feedback to #23791 (#23813)
|
| #
0e11aa5a |
| 10-Aug-2023 |
Kudo Chien <[email protected]> |
[go][sqlite] fix broken state for ios expo go (#23885)
# Why
ios expo-go has a couple error in the mean time, this pr is to address them all.
# How
- `pod install` error: outdated podfile.l
[go][sqlite] fix broken state for ios expo go (#23885)
# Why
ios expo-go has a couple error in the mean time, this pr is to address them all.
# How
- `pod install` error: outdated podfile.lock since #23858
- build error from sqlite, since expo-go mixes ios builtin sqlite3 and community sqlite3. for example, sqlite3 `create_filename` is different. we should use older sqlite3 to make sure everything is compatible.
- `char *(*create_filename)(const char*,const char*,const char*,
int,const char**);`
- `const char *(*create_filename)(const char*,const char*,const char*,
int,const char**);`
- missing some files to build for versioned expo-go, when testing with versioned expo-go. it will have runtime error because of missing modules.
# Test Plan
- ci passed
- versioned expo go + NCL `EXPO_SDK_VERSION=UNVERSIONED npx expo start`
show more ...
|
| #
560b3806 |
| 08-Aug-2023 |
Tomasz Sapeta <[email protected]> |
[iOS] Update pbxproj in Expo Go after updates in expo-sqlite
|
| #
8b02c6d0 |
| 20-Jul-2023 |
Tomasz Sapeta <[email protected]> |
[iOS] Refactor version manager in Expo Go (#23624)
|
| #
af2ec015 |
| 26-Jun-2023 |
Tomasz Sapeta <[email protected]> |
Add versioned code for SDK 49 on iOS (#23071)
|
| #
5b564ca4 |
| 26-Jun-2023 |
Wojciech Dróżdż <[email protected]> |
Remove react-native-shared-element from Expo Go (#22970)
|
| #
60ad5af1 |
| 21-Jun-2023 |
Kudo Chien <[email protected]> |
[go] add network inspector support (#22741)
# Why
add network inspector support for expo go
close ENG-8010
# How
integrate the ExpoRequestCdpInterceptor from expo-modules-core. unlike expo
[go] add network inspector support (#22741)
# Why
add network inspector support for expo go
close ENG-8010
# How
integrate the ExpoRequestCdpInterceptor from expo-modules-core. unlike expo-dev-launcher to use hacky solution, we want to enable the network inspector on release mode, so the implementation follows formal way.
- on ios, we leverage the `RCTSetCustomNSURLSessionConfigurationProvider` from react-native to create dedicated `URLSessionConfiguration`.
- on android, we already have a dedicated okhttp client from expo go. this pr just adds the interceptors.
- found image requests are not intercepted, it is because we don't use okhttp for fresco image pipeline. this pr tries to use the okhttp for fresco as react-native.
- android expo go has multiple react instances. however, the network inspector currently only support single inspector target to metro-inspector-proxy. as the result, we only limit the current foreground activity to send network inspector events.
# Test Plan
ncl + expo go to test the network inspector
show more ...
|
| #
c0a96678 |
| 07-Jun-2023 |
Kudo Chien <[email protected]> |
Upgrade react-native 0.72.0-rc.5 (#22588)
# Why
upgrade react-native 0.72 for sdk 49
close ENG-8011
# How
- bump package versions
- `react-native 0.71.3 -> 0.72.0-rc.5`
- `metro-reac
Upgrade react-native 0.72.0-rc.5 (#22588)
# Why
upgrade react-native 0.72 for sdk 49
close ENG-8011
# How
- bump package versions
- `react-native 0.71.3 -> 0.72.0-rc.5`
- `metro-react-native-babel-preset 0.73.9 -> 0.76.5`
- [bare-expo][templates][fabric-tester] migrate template base on [upgrade-helper](https://react-native-community.github.io/upgrade-helper/?from=0.71.7&to=0.72.0-rc.5)
- [expo-template-tabs] remove the metro version overrides for expo-router.
- [core][dev-laucher][dev-menu][media-library][screen-orientation][splash-screen][updates-interface][updates] add the `install_modules_dependencies` to support new architecture + use_frameworks!
- [core][autolinking] fix some new architecture error on ios
- [react-native-lab] update our fork to 0.72.0-rc.5 based
- [go][tools] fix **react-native-lab/react-native/packages/react-native** path move because of react-native's repo monorepo changes
- [go][android] fix gradle 8 errors
- [go][ios] add `RCT_REMOTE_PROFILE=0` to fix the `RCT_ENABLE_INSPECTOR needs to be set to fulfill RCT_REMOTE_PROFILE` build error
- [ncl] remove `ProgressViewIOS` / `ProgressBarAndroid` since they are deprecated/removed in 0.72
- [dev-menu][dev-launcher] rebuild bundles
# Note
- react-native-web is not bumped because of the [issue](https://github.com/necolas/react-native-web/issues/2523), so it's still react-native-web@~0.18.10.
- currently disable ci typecheck for @expo/cli because of upstream metro typescript support. i'll have another pr to fix those errors.
- updates e2e ci on android is broken at [here](https://github.com/expo/expo/blob/fada3d764957779fbfc3d7b723d185db1d933d95/packages/expo-updates/e2e/fixtures/Updates.e2e.ts#L518). i doubt if that's related to the react scheduler change. i'd disabled the failed test case.
- the react-native upstream [migrated away the `@types/jest`](https://github.com/facebook/react-native/pull/36068). i was afraid that will be a breaking change to the existing jest test code since it requires the explicit `@jest/globals` import. i didn't do this in this upgrade.
# Test Plan
- ✅ fabric-tester (without expo-dev-client)
- ✅ ci passed. there are some errors which are known:
- updates e2e on android: as mentioned above
- ios expo go on eas build: versioned expo go are broken on eas build m1 worker. this is also happening on main.
- android client: no space left on the ubuntu worker. this is also happening on main.
- ✅ bare-expo
- ✅ unversioned expo go + ncl
---------
Co-authored-by: Tomasz Sapeta <[email protected]>
show more ...
|
| #
68515061 |
| 05-Jun-2023 |
Tomasz Sapeta <[email protected]> |
[ios] Remove SDK 46 on iOS (#22731)
|
| #
4ab2fd68 |
| 29-May-2023 |
aleqsio <[email protected]> |
Make expo go work on M1 simulator (#21249)
Co-authored-by: Expo Bot <[email protected]>
|
| #
ae642c8a |
| 25-May-2023 |
aleqsio <[email protected]> |
Remove face detector from iOS Expo Go (#22619)
Co-authored-by: Expo Bot <[email protected]>
|
| #
0502d1f9 |
| 18-May-2023 |
Tomasz Sapeta <[email protected]> |
Remove Amplitude from Expo Go (#22523)
|
| #
506f58dd |
| 06-May-2023 |
Will Schurman <[email protected]> |
[expo-updates][expo-go] Support new SDK version field in new manifests (#22356)
|
| #
a2cc5e74 |
| 18-Feb-2023 |
Tomasz Sapeta <[email protected]> |
[autolinking][ios] Generate the modules provider in the build phase script (#21108)
|
| #
fe5cfb17 |
| 06-Feb-2023 |
Tomasz Sapeta <[email protected]> |
[ios] Add versioned code for SDK 48 (#21091)
|
| #
86dbd8e0 |
| 02-Feb-2023 |
aleqsio <[email protected]> |
[stripe] Upgrade stripe to 0.23.1 (#20964)
|
| #
84f418d7 |
| 17-Jan-2023 |
Kudo Chien <[email protected]> |
[1/3] upgrade react-native 0.71 (#20799)
# Why
upgrade react-native 0.71 for sdk 48
close ENG-7192
# How
- update package versions
- `react: 18.1.0 -> 18.2.0`
- `react-native 0.70.5
[1/3] upgrade react-native 0.71 (#20799)
# Why
upgrade react-native 0.71 for sdk 48
close ENG-7192
# How
- update package versions
- `react: 18.1.0 -> 18.2.0`
- `react-native 0.70.5 -> 0.71.0`
- `react-dom: 18.1.0 -> 18.2.0`
- `react-test-renderer: 18.1.0 -> 18.2.0`
- `react-native-web: 0.18.9 -> 0.18.10`
- `babel-plugin-react-native-web: 0.18.9 -> 0.18.10`
- `metro-react-native-babel-preset: 0.72.3 -> 0.73.5`
- upgrade three project templates based on [upgrade-helper](https://react-native-community.github.io/upgrade-helper/?from=0.70.6&to=0.71.0)
- bare-expo
- expo-template-bare-minimum
- fabric-tester (this is based on `npx expo prebuild --clean --no-install --template /path/to/expo-template-bare-minimum.tgz`) so it includes some inconsistent changes
- [@expo/config-plugins]: support 0.71 template transform. the `namespace` in build.gradle and the files in `release` build variants
- [fbjni] upgrade 0.3.0 to align 0.71 (also ndk version)
- [expo-updates] move the `EX_UPDATES_NATIVE_DEBUG` `bundleInDebug` setup to templates. unfortunately, because RNGP setups the task dependencies pretty early. the original setup in expo-updates build.gradle is too late. note that the change doesn't reference any files from templates to expo-updates package. somehow it's not tightly coupled.
- [native-tests / expo-modules-test-core / expo-modules-autolinking] fix ios unit test build error because jsc now in a dedicated podspec. in theory, the ios native unit test could now run on hermes as well.
- for other details, please check commit histories one by one.
# Test Plan
- bare-expo ios / android
- fabric ios / android
- ci passed (except ios)
- test-suite ios is broken for unknown reasons. it breaks only on github actions and hermes. for nightlies testing, i also [changed it to jsc](https://github.com/expo/expo/blob/1e029c89c4247802cc4880e27e116a6b4c71c502/tools/src/commands/SetupReactNativeNightly.ts#L287-L293) to make ci green. i'll try to follow up and investigate the root cause.
show more ...
|
| #
89486d34 |
| 11-Jan-2023 |
Tomasz Sapeta <[email protected]> |
[ios] Remove versioned code for SDK 45
|
| #
7c3ed0c0 |
| 14-Dec-2022 |
Douglas Lowder <[email protected]> |
[Expo Go][iOS] No remote home app loads in release builds (#20416)
# Why
Per ENG-7047, we need to disable remote loading of home app, and
checking for home app updates, for release builds.
Upda
[Expo Go][iOS] No remote home app loads in release builds (#20416)
# Why
Per ENG-7047, we need to disable remote loading of home app, and
checking for home app updates, for release builds.
Updates and loading from the packager will still work in debug builds.
# How
Add `#ifdef DEBUG` in several places in
`Exponent/Kernel/AppLoader/EXAppLoader.m`
# Test Plan
- CI should pass
- Test Expo Go builds locally and verify that updates are not loaded,
and that nothing else is broken
# Checklist
<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->
- [x] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [x] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [x] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).
show more ...
|
| #
72c1d89f |
| 22-Nov-2022 |
Kudo Chien <[email protected]> |
[ios] fixed versioned expo go build error
|