Repository navigation
Pubspec for a plugin should be able to capture build dependencies #9214
Description
From @collinjackson: If you try to build an app that consumes a plugin with gmscore dependencies, it fails until you add something like this to build.gradle of the app:
classpath 'com.google.gms:google-services:3.0.0'
apply plugin: 'com.google.gms.google-services'
It would be better if you could specify these dependencies in the pubspec.yaml file of the plugin and than have the build step inject this into the app.
Activity
mit-mit commentedon Apr 5, 2017
Tentatively tagging M2 as this impacts our hero scenario for that
eseidelGoogle commentedon Apr 11, 2017
Tentatively punting. Please feel free to pull back if you feel it's important.
mit-mit commentedon Sep 13, 2017
Need to investigate
Hixie commentedon Dec 18, 2017
Leaving in current milestone since this seems like plugin framework maintenance work, which is considered a top priority according to our priority list.
cbracken commentedon Feb 23, 2018
@mravn-google triaging - any updates?
mit-mit commentedon Apr 6, 2018
Postponing to milestone 4.
amirh commentedon Mar 29, 2019
@mit-mit any updates? should this be tracked as a pub issue as well?
stuartmorgan-g commentedon Feb 21, 2023
Is this describing an obsolete issue? Generally plugin native dependencies are handled automatically by the build, and don't need app-level intervention.
mit-mit commentedon Feb 22, 2023
Yeah, I think this is stale
github-actions commentedon Mar 8, 2023
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.