-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android EAS build failing on Github Actions #1935
Comments
Hi, I googled it and it seems like an issue connected with a missing Do you have push notifications set up for your project? |
Thanks for the reply! Nope, no push notifications set up, I though EAS automatically takes the google-service-account.json file and transforms it into that one for the Android build process. |
As additional info, I tried the following:
|
So the EAS Build manages the Android build credentials needed for signing your build https://docs.expo.dev/app-signing/app-credentials/ The The contents of {
"project_info": {...},
"client": [...],
} https://developers.google.com/android/guides/google-services-plugin#processing_the_json_file Could you let me know if the file you provided has this structure? Or more like {
"type": "service_account",
"project_id": "PROJECT_ID",
"private_key_id": "KEY_ID",
"private_key": "-----BEGIN PRIVATE KEY-----\nPRIVATE_KEY\n-----END PRIVATE KEY-----\n",
"client_email": "SERVICE_ACCOUNT_EMAIL",
"client_id": "CLIENT_ID",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/SERVICE_ACCOUNT_EMAIL"
} (which is the service account json structure)? |
Oh wait, I have a doubt now: it's the first time I use |
This question is asked only for iOS |
Do you use Firebase in your app? |
Nope, not really. Maybe it's faster this way, is there a proven way to submit automatically when merging on main? I went through the docs and found some scattered instructions, including the Github Actions example, but it does not cover the example of submitting as well |
So basically using the |
You're completely right, it's build-related and that needs to be solved first. I am unsure though, until some days ago simply using This error I am getting now is unexpected since I do not even have the |
Did you add some new external dependencies between your last successful build and now? |
Sorry, had other prios to work on. Back to this, I have only added some scripts for Github Actions, which should not be the cause for the failing build correct? Is there any command I could run to get more debug info on why is a google.services.json expected, since I am in the managed workflow and I do not even have android/ios folder in my project? Thanks for your help! |
Silly me, I got confused by the guide in the environment variables section regarding EAS build, where they mentioned a google services file. I assumed it was the one I needed (google-service-account.json), but it's referring indeed to Firebase. Sorry and thanks for helping out, I managed to save the contents of the Google Service Account file encoded as base64 in my Github repo secrets and in the CI step I am decoding it and writing it in the file. If there is a better way to do this, feel free to add a comment but it seems to work. |
Build/Submit details page URL
https://expo.dev/accounts/quantoz/projects/qbs-test-app/builds/6708f5ba-dec0-4b4d-b474-440039bedffc#run-gradlew
Summary
Notes
Building locally with the same setup works
Expected
With the provided Github actions YML file below, a build should be created for both Android and iOS and the submission should take place thanks to the
--auto-submit
flag.Actual behavior
iOS works perfectly, but the Android build fails with the error output below.
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.1
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
Yarn: 1.22.15 - ~/.nvm/versions/node/v16.15.0/bin/yarn
npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm
Watchman: 2023.04.17.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
npmPackages:
expo: ~48.0.18 => 48.0.20
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.71.8 => 0.71.8
npmGlobalPackages:
eas-cli: 3.15.1
expo-cli: 6.3.9
Expo Workflow: managed
Expo doctor:
Check package.json for common issues
✔ Validate global prerequisites versions
✔ Validate Expo Config
✔ Check for conflicting global packages in project
✔ Check for incompatible packages
✔ Verify prebuild support package versions are compatible
✔ Check compatible dependency versions for the installed Expo SDK
Didn't find any issues with the project!
Error output
Reproducible demo or steps to reproduce from a blank project
I think it might be something simple I am missing or that I could not find in the docs, if that's not the case I will try to create a new app and create the app on the google play console.
The text was updated successfully, but these errors were encountered: