| #
b8addc5d |
| 11-Sep-2023 |
Will Schurman <[email protected]> |
[ios] Remove dead code (#24316)
|
| #
0502d1f9 |
| 18-May-2023 |
Tomasz Sapeta <[email protected]> |
Remove Amplitude from Expo Go (#22523)
|
| #
413f104b |
| 10-Sep-2020 |
Eric Samelson <[email protected]> |
[ios] fix fallbackToCacheTimeout logic from EXShell (#10129)
|
| #
734a9caa |
| 31-Aug-2020 |
Eric Samelson <[email protected]> |
[android][ios] pass app.json updates config to expo-updates in standalone apps (#9985)
|
| #
b8e86ac0 |
| 06-May-2020 |
Tomasz Sapeta <[email protected]> |
[ios][et] Remove Fabric and Crashlytics on iOS (#8160)
# Why
Part of #8047 - not closing yet because I'm gonna make separate PR for Android.
# How
I removed:
- Fabric and Crashlytics from
[ios][et] Remove Fabric and Crashlytics on iOS (#8160)
# Why
Part of #8047 - not closing yet because I'm gonna make separate PR for Android.
# How
I removed:
- Fabric and Crashlytics from `Podfile` and run `pod install`.
- code calling Fabric & Crashlytics libraries.
- `et ios-run-fabric` command and its `run-fabric.sh` build phase in general.
- modifying `Info.plist` while generating dynamic macros, it was used only to apply fabric's api key.
- `et ios-cleanup-dynamic-macros` command - no longer needed if we don't modify `Info.plist`.
- Fabric's key from `Info.plist`.
## Side notes
Previously, once Crashlytics detects a crash, we set a flag in user defaults and then if that flag is set we invalidated cached kernel's bundle. After these changes, kernel's bundle won't be invalidated. I chatted with James and he agrees that we actually don't need this anymore.
# Test Plan
Xcode project builds and works as expected.
show more ...
|
| #
b16fc45c |
| 20-May-2019 |
Michael Gallagher <[email protected]> |
Enable User Defined Build Settings in Release Channel (#2093)
Xcode's User Defined Build Settings can (unfortunately) only be used in Info.plist so this allows you to set Expo's Release Channel ther
Enable User Defined Build Settings in Release Channel (#2093)
Xcode's User Defined Build Settings can (unfortunately) only be used in Info.plist so this allows you to set Expo's Release Channel there. When you're detached, this is helpful in order to automate different Release Channels for dev, staging, prod. Additionally, when you're detached, the Version and Build of the binary should generally be part of release channel as well. Version and Build can be stored in User Defined Build Settings and used to set both CFBundleShortVersionString, CFBundleVersion and as part of ExpoReleaseChannel to avoid duplication.
show more ...
|
| #
1fa9f0a4 |
| 20-Jun-2018 |
Eric Samelson <[email protected]> |
set isDebugXCodeScheme in EXEnvironment (#2711)
fbshipit-source-id: 697040c
|
| #
9b1cfd94 |
| 24-May-2018 |
Ben Roth <[email protected]> |
Clean up EXEnvironment, remove deprecated shell development config behavior
fbshipit-source-id: f4d4d01
|
| #
249f6b8a |
| 24-May-2018 |
Ben Roth <[email protected]> |
Remove deprecated flag that allowed old standalone apps to skip the splash API
fbshipit-source-id: d49d57d
|
| #
36851f71 |
| 24-May-2018 |
Ben Roth <[email protected]> |
Remove isShell property because it is now identical to isDetached
Also clean up a few other props that had shell in the name
closes https://github.com/expo/universe/issues/2460
fbshipit-source-id:
Remove isShell property because it is now identical to isDetached
Also clean up a few other props that had shell in the name
closes https://github.com/expo/universe/issues/2460
fbshipit-source-id: fac520e
show more ...
|
| #
00fcd3c6 |
| 24-May-2018 |
Ben Roth <[email protected]> |
EXShellManager -> EXEnvironment
fbshipit-source-id: 2347314
|