Did you change your Gradle configs, related to the APK’s name? It seems that you did set a filter to only copy/deploy app-stage-release.apk, but this Gradle step no longer generates an APK with that file name.
If you want to copy/deploy a single APK, you have to specify the APK’s file name in the Gradle Runner step’s APK file include filter input/option (the APK’s file name which will be generated by the gradle task you specified for the Gradle Runner step).
If you want to copy/deploy all generated APK files, you can use a wildcard filter like: *.apk
That’s exactly what I meant, that you specified a filter app-stage-release.apk, but your Gradle task does not generate an APK with that file name (app-stage-release.apk).
You should check what’s the generated APK’s file name is, and set that as the include filter.
Checking btirise logs looks it’s the right name: /bitrise/src/app/build/outputs/apk/app-stage-release.apk
I did also check locally and it’s indeed the file being generated: app-stage-release.apk
OK, we found the issue and it’s indeed related to the new Gradle Runner step version. Fortunately the issue is really simple to fix: just add a * prefix to the filter.
E.g. instead of:
app-stage-release.apk
use:
*app-stage-release.apk
or
*/app-stage-release.apk
Basically the change was that the filter is no longer applied on the file name, but instead on the path, so if you specify an exact value without * then the full path have to match that. The advantage of the new filter method is that you can now filter by the path too, and not just by the apk’s name. E.g. previously this wasn’t possible: */apk/release/*.apk but now it is!