Description

The issue was that the script was configuring the dependency on libapp.so without taking the flavor into consideration. There should only be one libapp.so per ABI, but when there are multiple flavor, the num of variants is: num build types * num flavors.

Related Issues

Fixes: #31922 (comment), #34598

• What went wrong:
  Execution failed for task ':app:transformNativeLibsWithMergeJniLibsForProductionRelease'.
  More than one file was found with OS independent path 'lib/armeabi-v7a/libapp.so'

Tests

I added the following tests:

• App bundle content using flavors without explicit target platform

Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I signed the CLA.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flutter developers to manually update their apps to accommodate your change?

• Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
• No, this is not a breaking change.