Some issues with EAS build
See original GitHub issueSummary
1 - TextInput has weird horizontal padding. You can compare screenshots below. The text “horizontalpadding” starts exactly on the edge in 2nd screenshot. First picture is eas build sdk41 while second is Expo GO client or expo build
2 - Translucent status set in app.json is ignored. Setting translucent in runtime doesn’t work either and also looks odd
3- Splash screen no longer shows up. This happens on iOS as well
4 - If you have expo-branch installed. You get crash when launching the app
Here’s my app.json
{
"expo": {
"name": "Stillwhite",
"slug": "Stillwhite",
"privacy": "public",
"facebookScheme": "fb123",
"facebookAppId": "123",
"facebookDisplayName": "Stillwhite",
"backgroundColor": "#000000",
"androidStatusBar": {
"barStyle": "light-content",
"translucent": true
},
"platforms": [
"ios",
"android"
],
"primaryColor": "#2699FB",
"version": "1.6.4",
"scheme": "stillwhite",
"orientation": "portrait",
"icon": "./assets/icon.png",
"splash": {
"backgroundColor": "#2699FB"
},
"updates": {
"fallbackToCacheTimeout": 0
},
"assetBundlePatterns": [
"**/*"
],
"hooks": {
"postPublish": [
{
"file": "sentry-expo/upload-sourcemaps",
"config": {
"organization": "stillwhite",
"project": "stillwhite",
"authToken": "xxxxxxx"
}
}
]
},
"userInterfaceStyle": "automatic",
"ios": {
"buildNumber": "28",
"supportsTablet": false,
"bundleIdentifier": "com.stillwhite.app",
"appStoreUrl": "https://apps.apple.com/us/app/stillwhite-wedding-dresses/id1483180828",
"googleServicesFile": "./GoogleService-Info.plist",
"config": {
"branch": {
"apiKey": "key_live_Xxxxxxxxxxxxx"
}
}
},
"android": {
"versionCode": 28,
"package": "com.stillwhite.app",
"useNextNotificationsApi": true,
"playStoreUrl": "https://play.google.com/store/apps/details?id=com.stillwhite.app",
"adaptiveIcon": {
"backgroundColor": "#2699FB",
"foregroundImage": "./assets/adaptive/icon-foreground.png"
},
"backgroundColor": "#FFFFFF",
"googleServicesFile": "./google-services.json",
"config": {
"branch": {
"apiKey": "key_live_Xxxxxxxxxxxxx"
}
}
},
"notification": {
"iosDisplayInForeground": true,
"icon": "./assets/push_icon.png"
}
}
}
Managed or bare workflow? If you have ios/
or android/
directories in your project, the answer is bare!
managed
What platform(s) does this occur on?
Android
SDK Version (managed workflow only)
41
Environment
Expo CLI 4.4.3 environment info: System: OS: macOS 11.3 Shell: 5.8 - /bin/zsh Binaries: Node: 14.16.1 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 7.10.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4 Android SDK: API Levels: 25, 26, 28, 29, 30 Build Tools: 28.0.3, 29.0.2, 29.0.3 System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom IDEs: Android Studio: 4.1 AI-201.8743.12.41.7199119 Xcode: 12.5/12E262 - /usr/bin/xcodebuild npmPackages: expo: 41.0.0 => 41.0.0 react: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz => 0.63.2 react-navigation: ^4.4.4 => 4.4.4 npmGlobalPackages: expo-cli: 4.4.3 Expo Workflow: managed
Reproducible demo or steps to reproduce from a blank project
The summary is probably applicable to any blank project
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (6 by maintainers)
Top GitHub Comments
@brentvatne I was able to reproduce the issues except the map one - I’ll update here if I manage to reproduce it.
For the carousel issue, I found out the cause of it. It seems like images with insecure url (http) don’t render while https ones do.
Also I found another problem; the default colour for text/icon should be black and they are displayed black in the emulator and iOS but not in EAS android build.
All the issues here are only present on EAS build for Android.
The repo is here: https://github.com/kessris/Expo-EAS-Android-Build-Issue
we don’t plan on supporting expo-branch on eas build, instead we hope that there will be a config plugin built to support the react-native-branch library. closing this because the other issues discussed here should be resolved, please create a new issue for any specific issue that persists. also, note that these fixes are only available on sdk 42+