Skip to content

[CP] Add namespace to module build file templates #128136

Description

@camsim99

issue_link

#126403

Commit Hash

31a665c

Target

stable

pr_link

#126963
#128360

Changelog Description

Adds namespace configuration to module build.gradle file templates that is required when using >= Gradle 8.0.

Impacted Users

Flutter devs using add-to-app on Android wanting to use Gradle 8.0+

Impact Description

Flutter developers generating Flutter modules to use for android-add-to-app with an Android app using Gradle 8.0+ will receive a vague error describing an issue with namespace in its build.gradle configuration files as described in #126403 (comment).

Workaround

A developer may work around the issue by adding the namespace configuration manually to the module's build.gradle configuration files.

Risk

low

Test Coverage

yes

Validation Steps

Once you checkout my fix, you need to find an existing Android app or create one to use for testing. Modify it if necessary to use Gradle 8.0+. Then, create a Flutter module to add to an existing Android app using the command listed here. Finally, try running the app or building the apk and verify that it is successful.

Activity

  1. itsjustkevin commented on Jun 2, 2023

    @itsjustkevin
    Contributor

    @reidbaker for review.

  2. reidbaker commented on Jun 2, 2023

    @reidbaker
    Contributor

    @reidbaker for review.

    On vacation for 2 weeks you will need another reviewer

  3. itsjustkevin commented on Jun 2, 2023

    @itsjustkevin
    Contributor

    Handoff to @gmackall and @stuartmorgan for review.

  4. gmackall commented on Jun 6, 2023

    @gmackall
    Member

    Is this missing a link to the cherry-pick pr? The pr_link points to the pr to master

  5. camsim99 commented on Jun 6, 2023

    @camsim99
    ContributorAuthor

    Is this missing a link to the cherry-pick pr? The pr_link points to to the pr to master

    Oh, @CaseyHillers do I need to open another PR to stable?

  6. CaseyHillers commented on Jun 6, 2023

    @CaseyHillers
    Contributor

    Yes, CP authors need to send the CP PR as well. Otherwise, we don't have the ability to assess the risk it has on the branch.

  7. camsim99 commented on Jun 8, 2023

    @camsim99
    ContributorAuthor

    @CaseyHillers @Jasguerrero I think this is ready for another look!

  8. self-assigned this
    on Jun 9, 2023
  9. github-actions commented on Jun 29, 2023

    @github-actions

    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 -v and a minimal reproduction of the issue.

  10. locked as resolved and limited conversation to collaborators on Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

cp: approvedApproved cherry-pick requestcp: merge-to-stableCherry-picks that should be merged to stablecp: mergedCherry-pick has been merged to the release branch.cp: reviewCherry-picks in the review queue

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions