What’s Changed
The Step exports the mapping file in the final output dir, and ignores intermediate copies. This is only relevant for builds still exporting an apk, bundles (*.aab) include the mapping file.
Breaking changes
Two input defaults changed, to ignore intermediates dir. It is not expected to cause actual breakage for most users.
mapping_file_exclude_filter
- */tmp/*
+ */tmp/*
+ */intermediates/*
+ *compose-mapping.txt
test_apk_file_exclude_filter
- (empty)
+ */intermediates/*
If you want the previous behaviour, set the old defaults explicitly:
- gradle-runner@6:
inputs:
- mapping_file_exclude_filter: "*/tmp/*"
- test_apk_file_exclude_filter: ""
If you already set these inputs yourself, note that a filter input replaces the defaults rather than extending them, so copy the new patterns into your own list to get the fix:
- mapping_file_exclude_filter: |-
*/tmp/*
*/intermediates/*
*compose-mapping.txt
*/your-own-pattern/*
Known limitation
With several minified variants in one build, each variant’s published mapping.txt still collides by name in the deploy directory, so all but the first get a timestamped name and $BITRISE_MAPPING_PATH still points at only one of them. Use mapping_file_include_filter to narrow the export to the variant you deploy, for example */productionRelease/mapping.txt.