Repository navigation
Closed
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: existing-appsIntegration with existing apps via the add-to-app flowIntegration with existing apps via the add-to-app flowc: regressionIt was better in the past than it is nowIt was better in the past than it is nowfound in release: 3.3Found to occur in 3.3Found to occur in 3.3found in release: 3.4Found to occur in 3.4Found to occur in 3.4has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-androidAndroid applications specificallyAndroid applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versiontoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Description
Q1:On the master channel flutter build aar --no-debug --no-profile will result in also creating modules for debug and profile.
see: #108000
Q2:the dependencies version format does not work on 3.1.0~3.3.2
Steps to Reproduce:
1.flutter checkout master
2.flutter create -t module module_test
3.flutter build aar --no-debug --no-profile --build-number 1.0.0
Expected results:
On stable the following files are created: on 3.0.5
Logs
build/host/outputs/repo/com/example/
└── module_test
└── flutter_release
├── 1.0
│ ├── flutter_release-1.0.aar
│ ├── flutter_release-1.0.aar.md5
│ ├── flutter_release-1.0.aar.sha1
│ ├── flutter_release-1.0.pom
│ ├── flutter_release-1.0.pom.md5
│ └── flutter_release-1.0.pom.sha1
├── maven-metadata.xml
├── maven-metadata.xml.md5
└── maven-metadata.xml.sha1
implementation 'com.example.module_test:flutter_release:1.0.0'
Actual results:
On master these files are created: on 3.1.0~3.3.2
Logs
build/host/outputs/repo/com/example/
└── module_test
├── flutter
│ ├── 1.0
│ │ ├── flutter-1.0-debug.aar
│ │ ├── flutter-1.0-debug.aar.md5
│ │ ├── flutter-1.0-debug.aar.sha1
│ │ ├── flutter-1.0-debug.aar.sha256
│ │ ├── flutter-1.0-debug.aar.sha512
│ │ ├── flutter-1.0-profile.aar
│ │ ├── flutter-1.0-profile.aar.md5
│ │ ├── flutter-1.0-profile.aar.sha1
│ │ ├── flutter-1.0-profile.aar.sha256
│ │ ├── flutter-1.0-profile.aar.sha512
│ │ ├── flutter-1.0-release.aar
│ │ ├── flutter-1.0-release.aar.md5
│ │ ├── flutter-1.0-release.aar.sha1
│ │ ├── flutter-1.0-release.aar.sha256
│ │ ├── flutter-1.0-release.aar.sha512
│ │ ├── flutter-1.0.module
│ │ ├── flutter-1.0.module.md5
│ │ ├── flutter-1.0.module.sha1
│ │ ├── flutter-1.0.module.sha256
│ │ ├── flutter-1.0.module.sha512
│ │ ├── flutter-1.0.pom
│ │ ├── flutter-1.0.pom.md5
│ │ ├── flutter-1.0.pom.sha1
│ │ ├── flutter-1.0.pom.sha256
│ │ └── flutter-1.0.pom.sha512
│ ├── maven-metadata.xml
│ ├── maven-metadata.xml.md5
│ ├── maven-metadata.xml.sha1
│ ├── maven-metadata.xml.sha256
│ └── maven-metadata.xml.sha512
├── flutter_debug
│ ├── 1.0
│ │ ├── flutter_debug-1.0.aar
│ │ ├── flutter_debug-1.0.aar.md5
│ │ ├── flutter_debug-1.0.aar.sha1
│ │ ├── flutter_debug-1.0.aar.sha256
│ │ ├── flutter_debug-1.0.aar.sha512
│ │ ├── flutter_debug-1.0.module
│ │ ├── flutter_debug-1.0.module.md5
│ │ ├── flutter_debug-1.0.module.sha1
│ │ ├── flutter_debug-1.0.module.sha256
│ │ ├── flutter_debug-1.0.module.sha512
│ │ ├── flutter_debug-1.0.pom
│ │ ├── flutter_debug-1.0.pom.md5
│ │ ├── flutter_debug-1.0.pom.sha1
│ │ ├── flutter_debug-1.0.pom.sha256
│ │ └── flutter_debug-1.0.pom.sha512
│ ├── maven-metadata.xml
│ ├── maven-metadata.xml.md5
│ ├── maven-metadata.xml.sha1
│ ├── maven-metadata.xml.sha256
│ └── maven-metadata.xml.sha512
├── flutter_profile
│ ├── 1.0
│ │ ├── flutter_profile-1.0.aar
│ │ ├── flutter_profile-1.0.aar.md5
│ │ ├── flutter_profile-1.0.aar.sha1
│ │ ├── flutter_profile-1.0.aar.sha256
│ │ ├── flutter_profile-1.0.aar.sha512
│ │ ├── flutter_profile-1.0.module
│ │ ├── flutter_profile-1.0.module.md5
│ │ ├── flutter_profile-1.0.module.sha1
│ │ ├── flutter_profile-1.0.module.sha256
│ │ ├── flutter_profile-1.0.module.sha512
│ │ ├── flutter_profile-1.0.pom
│ │ ├── flutter_profile-1.0.pom.md5
│ │ ├── flutter_profile-1.0.pom.sha1
│ │ ├── flutter_profile-1.0.pom.sha256
│ │ └── flutter_profile-1.0.pom.sha512
│ ├── maven-metadata.xml
│ ├── maven-metadata.xml.md5
│ ├── maven-metadata.xml.sha1
│ ├── maven-metadata.xml.sha256
│ └── maven-metadata.xml.sha512
└── flutter_release
├── 1.0
│ ├── flutter_release-1.0.aar
│ ├── flutter_release-1.0.aar.md5
│ ├── flutter_release-1.0.aar.sha1
│ ├── flutter_release-1.0.aar.sha256
│ ├── flutter_release-1.0.aar.sha512
│ ├── flutter_release-1.0.module
│ ├── flutter_release-1.0.module.md5
│ ├── flutter_release-1.0.module.sha1
│ ├── flutter_release-1.0.module.sha256
│ ├── flutter_release-1.0.module.sha512
│ ├── flutter_release-1.0.pom
│ ├── flutter_release-1.0.pom.md5
│ ├── flutter_release-1.0.pom.sha1
│ ├── flutter_release-1.0.pom.sha256
│ └── flutter_release-1.0.pom.sha512
├── maven-metadata.xml
├── maven-metadata.xml.md5
├── maven-metadata.xml.sha1
├── maven-metadata.xml.sha256
└── maven-metadata.xml.sha512
implementation 'com.example.module_test:flutter:1.0.0:release'
The following methods will not work
implementation 'com.example.module_test:flutter:1.0.+:release'
implementation 'com.example.module_test:flutter:1.+:release'
implementation 'com.example.module_test:flutter:1.0.0-SNAPSHOT:release'
I want the implementation to support fuzzy matching. for example:
implementation 'com.example.module_test:flutter_release:1.0.+'
implementation 'com.example.module_test:flutter_release:1.+'
implementation 'com.example.module_test:flutter_release:1.0.0-SNAPSHOT'
Reacted by Hyukjoong (Chuck) Kim
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work lista: existing-appsIntegration with existing apps via the add-to-app flowIntegration with existing apps via the add-to-app flowc: regressionIt was better in the past than it is nowIt was better in the past than it is nowfound in release: 3.3Found to occur in 3.3Found to occur in 3.3found in release: 3.4Found to occur in 3.4Found to occur in 3.4has reproducible stepsThe issue has been confirmed reproducible and is ready to work onThe issue has been confirmed reproducible and is ready to work onplatform-androidAndroid applications specificallyAndroid applications specificallyr: fixedIssue is closed as already fixed in a newer versionIssue is closed as already fixed in a newer versiontoolAffects the "flutter" command-line tool. See also t: labels.Affects the "flutter" command-line tool. See also t: labels.
Activity
[-][tool][add-2-app] the dependencies version format in not work when flutter build aar on 3.1.0~3.3.2[/-][+][tool][add-2-app] the dependencies version format does not work when flutter build aar on 3.1.0~3.3.2[/+]exaby73 commentedon Sep 15, 2022
Hello @JunhuaLin. The directory structure seems to be identical for me. Am I missing something here?
These are the steps I took:
On stable:
flutter create -t module issue_111643cd issue_111643flutter build aar --no-debug --no-profile --build-number 1.0.0tree /F .\build\host\outputs\repo\com\example\issue_111643Logs
On master (copied the same steps from stable):
flutter create -t module issue_111643cd issue_111643flutter build aar --no-debug --no-profile --build-number 1.0.0tree /F .\build\host\outputs\repo\com\example\issue_111643Logs
I used an online diff tool to check and found them both to be identical.
Flutter Doctor
flutter doctor -v(Stable)flutter doctor -v(Master)JunhuaLin commentedon Sep 16, 2022
Expected stable on 3.0.5:
The expected dependency format:
group:name:version,for example:Now, on 3.1.0~3.3.2 or master ,the dependency format is
group:name:version:classifierI hope
:classifiercan be removed!Rollback the dependency format from
group:name:version:classifiertogroup:name:version,for example:[-][tool][add-2-app] the dependencies version format does not work when flutter build aar on 3.1.0~3.3.2[/-][+][tool][add-2-app] the dependencies version format is wrong when flutter build aar on 3.1.0~3.3.2[/+][-][tool][add-2-app] the dependencies version format is wrong when flutter build aar on 3.1.0~3.3.2[/-][+]Revert file naming convention of `.aar` files to support fuzzy matching in `build.gradle`[/+]JunhuaLin commentedon Sep 19, 2022
Thanks. When is this expected to be reverted?
Hope to deal with as soon as possible, affect the upgrade to the latest version!
exaby73 commentedon Sep 19, 2022
@JunhuaLin The team would have to assign a priority to this issue. You can see the process here. When a team member is available to take up issues, it will be prioritized and eventually worked on.
You could also submit a PR for this issue :)
JunhuaLin commentedon Sep 20, 2022
#101276
The problem here comes from this PR
AesSedai101 commentedon Sep 20, 2022
hi,
If you read through the comments on that PR, you'll see that I attempted to keep the old structure, but because of gradle internals, we couldn't do that. It's possible that there is a workaround that I missed though.
GaryQian commentedon Sep 20, 2022
cc @GaryQian (myself) for reference
JunhuaLin commentedon Sep 22, 2022
The main problem here is generating publications and task dependencies, I made some adjustments:
#112149
JunhuaLin commentedon Sep 22, 2022
sound good! It's done.
JunhuaLin commentedon Sep 28, 2022
Hope to deal with as soon as possible, affect the upgrade to the latest version!
We don't want to stay at 3.0.5 for too long!
This problem is holding up the build flutter.
I think we can add the P3 label!
@GaryQian @exaby73
christopherfujino commentedon Sep 28, 2022
Please see Issue hygiene for more information about how the Flutter team prioritizes issues.
However, as you have submitted a PR I don't think the priority is relevant.
github-actions commentedon Oct 18, 2022
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.