Closed tprochazka closed 4 years ago
Do you think that warning is even necessary? It's there because it used to be an error, and we've just kind of carried it along. I'd be fine completely removing it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I agree, that it is probably not necessary. I think that the android build plugin directly will warn that it is missing.
Killed. 👍
Would be possible to move this check
Signing not ready for Gradle Play Publisher. Be sure to specify a signingConfig for variant 'defaultCcaDebuggableReleaseNoProguard'.
toproject.afterEvaluate {}
to be sure that setup of this is really done?I have own plugin which setup custom signing, but I also need to do it in afterEvaluate , because I have custom setup for it, something like
So I cannot setup it directly when my plugin is applied. And I not found a way how to react on the moment when myConfig is finished, so I'm waiting to
afterEvaluate
, but gradle-play-publisher meantime write this error and it is confusing for users.