fails to build with 4.2.1

[mbiebl]

Starting with 4.2.1-ose, I get the following build failure:

> Task :app:packageStandardRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':app:packageStandardRelease' (type 'PackageApplication').
  - In plugin 'com.android.internal.version-check' type 'com.android.build.gradle.tasks.PackageApplication' property 'signingConfigData.signingConfigData.storeFile' file '/dev/null' is not a file.
    
    Reason: Expected an input to be a file but it was a unexpected file type.
    
    Possible solutions:
      1. Use a file as an input.
      2. Declare the input as a unexpected file type instead.
    
    Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#unexpected_input_file_type for more details about this problem.

* Try:
> 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.

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

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

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

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

BUILD FAILED in 5m 40s
285 actionable tasks: 285 executed

Afaics this is caused by this commit d3c10c3

Does that mean, signing has become mandatory?

[rfc2822]

You can safely remove d3c10c3#diff-51a0b488f963eb0be6c6599bf5df497313877cf5bdff3950807373912ac1cdc9R83, then everything should work as before.

[mbiebl]

Sure, but this makes it inconvenient to build directly from git if one has to remember to revert that commit.
I assume the /dev/null fallback does not work as intended.

[rfc2822]

It does – it's a valid file name that doesn't break the syntax, but actually doesn't work.

Debug builds (like test runs) should work like before. It only applies to the release flavor. What is your use case of a release flavor without signing config?

[mbiebl]

I'm just used to run ./gradlew assemble on the command line. But you have a point. I guess I'll just use ./gradlew assembleDebug from now on. Thanks