fastlane/lib/fastlane/actions/gradle.rb in fastlane-2.217.0 vs fastlane/lib/fastlane/actions/gradle.rb in fastlane-2.218.0
- old
+ new
@@ -66,10 +66,10 @@
# If we didn't build, then we return now, as it makes no sense to search for apk's in a non-`assemble` or non-`build` scenario
return result unless gradle_task =~ /\b(assemble)/ || gradle_task =~ /\b(bundle)/
apk_search_path = File.join(project_dir, '**', 'build', 'outputs', 'apk', '**', '*.apk')
aab_search_path = File.join(project_dir, '**', 'build', 'outputs', 'bundle', '**', '*.aab')
- output_json_search_path = File.join(project_dir, '**', 'build', 'outputs', 'apk', '**', 'output*.json') # output.json in Android Stuido 3 and output-metadata.json in Android Studio 4
+ output_json_search_path = File.join(project_dir, '**', 'build', 'outputs', 'apk', '**', 'output*.json') # output.json in Android Studio 3 and output-metadata.json in Android Studio 4
mapping_txt_search_path = File.join(project_dir, '**', 'build', 'outputs', 'mapping', '**', 'mapping.txt')
# Our apk/aab is now built, but there might actually be multiple ones that were built if a flavor was not specified in a multi-flavor project (e.g. `assembleRelease`)
# However, we're not interested in unaligned apk's...
new_apks = Dir[apk_search_path].reject { |path| path =~ /^.*-unaligned.apk$/i }