Error in building with EAS build for Android

Hi.

I have tried EAS build after I did 1 month ago, I got error as below.

The key error appears to be the paragraph,

Execution failed for task ‘:app:validateSigningRelease’.

Keystore file not set for signing config release

I already set up Keystore before…
I don’t know the exact reason.
How can I solve it?

If needed, you can check the error log and eas.json under here.

Expo build log

> Task :app:collectReleaseDependencies

1698

> Task :app:configureReleaseDependencies

1699

> Task :app:parseReleaseIntegrityConfig

1700

> Task :app:validateSigningRelease FAILED

1701

w: Detected multiple Kotlin daemon sessions at build/kotlin/sessions

1702

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.

1703

Use '--warning-mode all' to show the individual deprecation warnings.

1704

See https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings

1705

899 actionable tasks: 899 executed

1706[stderr]

FAILURE: Build failed with an exception.

1707[stderr]

* What went wrong:

1708[stderr]

Execution failed for task ':app:validateSigningRelease'.

1709[stderr]

> Keystore file not set for signing config release

1710[stderr]

* Try:

1711[stderr]

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

1712[stderr]

* Get more help at https://help.gradle.org

1713[stderr]

BUILD FAILED in 11m 25s

1714

``Preformatted text```
Error: Gradle build failed with unknown error. Please see logs for the “Run gradlew” phase.




eas.json
{

  "builds": {

    "android": {

      "release": {

        "workflow": "managed",

        "withoutCredentials": true

      },

      "base": {

        "workflow": "managed",

        "withoutCredentials": true

      },

      "development": {

        "buildType": "development-client",

        "distribution": "internal",

        "workflow": "managed"

      }

    },

    "ios": {

      "release": {

        "workflow": "managed"

      },

      "development": {

        "buildType": "development-client",

        "distribution": "internal",

        "workflow": "managed"

      }

    }

  }

}

I found another problem. My app for iOS in App store connect have the status “invalid binary”.

Got this email from Apple

Dear Developer,

We identified one or more issues with a recent delivery for your app, “RoundsMap” 1.3.2 (1.3.2). Please correct the following issues, then upload again.

ITMS-90562: Invalid Bundle - One or more dynamic libraries that are referenced by your app are not present in the dylib search path.

ITMS-90562: Invalid Bundle - There’s an issue with the app’s bitcode compilation. Rebuild the app using the current public (GM) version of Xcode and upload it again.

Best regards,

The App Store Team

Why have you set withoutCredentials to true? This means EAS won’t configure credentials for your project, which is what the error message is complaining about

Yeah you are right!
I have tunerd it off, then works.

I don’t know why the previous build worked with the option.

Thank you!

But the problem in ios still exists…
Maybe I should find which node module is something wrong and delete it?

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.