Android builds with PKCS#12 keystores failing
See original GitHub issueNew Issue Checklist
- I read the Contribution Guidelines.
- I read docs.expo.io (Managed Workflow > Distributing Your App).
- I searched for existing GitHub issues.
Issue Description
Hi guys, not sure if this is the right place to report this but my build has been failing without any error logs. I’ve waited for quite some time for the logs to appear but none has appeared. This is the only error that I can see:
Your build is errored. No logs exist for this build yet. Once a build has logs they will appear here.
This is my build: https://expo.io/accounts/stackideas/builds/79adb602-b58e-4c61-9b60-4a73c1ecae20/logs
Command executed
expo build:android --non-interactive --release-channel easysocial-builder-33 --keystore-path=$EXPO_ANDROID_KEYSTORE_FILE --keystore-alias=$EXPO_ANDROID_KEYSTORE_ALIAS
Environment
Expo CLI 3.28.4 environment info: System: OS: macOS 10.15.7 Shell: 5.7.1 - /bin/zsh Binaries: Node: 14.4.0 - /usr/local/bin/node Yarn: 1.22.5 - /usr/local/bin/yarn npm: 6.14.8 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.9.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.1, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0 IDEs: Android Studio: 4.0 AI-193.6911.18.40.6626763 Xcode: 12.1/12A7403 - /usr/bin/xcodebuild npmPackages: expo: ^39.0.0 => 39.0.3 react: 16.13.1 => 16.13.1 react-native: https://github.com/expo/react-native/archive/sdk-39.0.3.tar.gz => 0.63.2 react-navigation: ^4.4.0 => 4.4.2 npmGlobalPackages: expo-cli: 3.28.4 Expo Workflow: managed
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Creating a new Key store (PKCS12) (Android Studio)
Everytime I would like to create a new Keystore two error messages appear (see below). First one: Warning: No support for different storage...
Read more >Known issues with Android Studio and Android Gradle Plugin
This update causes an underlying behavior change related to signing keys. To work around this issue, enter the same password for both the...
Read more >KeyStore - Android Developers
PKCS12 -DEF, 1-8 ... IOException, if there is an I/O or format problem with the keystore data, if a password is required but...
Read more >apksigner - Android Developers
Learn about the apksigner tool which allows you to sign APKs and to confirm that an APK's signature will be verified successfully on...
Read more >Android Keystore system - Android Developers
On this page · Security features. Extraction prevention; Hardware security module · Choose between a keychain and the Android Keystore provider ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hi all, we’ve deployed a fix to our servers. Android builds with PKCS#12 keystores should be working now. If someone could please confirm this is the case, that’d be great. Thanks! @kratoskp
great to hear 👍