How to get the Dependencies(direct & transitive) for android modules built using soong (Android.bp) - android-source

In aosp module containing Android.bp file uses soong m to build them
In gradle project we can get the dependecies using
gradle dependencies
https://stackoverflow.com/a/35235229/2018343
Is there similar command in soong? or is there anyother way to do get the dependencies?

Related

Flutter project can't be build because of plugin Geolocator

Since I have included the geolocator plugin in my flutter project, the build fails with the message
A problem occurred evaluating root project 'android'.
Basedir C:\Users\<user>\flutter\.pub-cache\hosted\pub.dartlang.org\geolocator-8.1.1\android does not exist
It's true that this directory does not exist but that's the way is done in github project.
do you have implement geolocator for a platform like android or ios?
after you have implemented you can try:
run: flutter clean and try again
Make sure your Android project uses gradle version 3.5.0 and gradle-wrapper 5.6.2.

Deep AR Flutter: Direct local .aar file dependencies are not supported when building an AAR

I'm following the documentation as given in the plugin page on camera_deep_ar
I have set the minimumSdkVersion to 19
Given the permissions correctly in the AndroidManifest.xml
Set up the proguard-android.txt file correctly
And used the sample code given in the docs
This is the error it gives me on running the app.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':camera_deep_ar:bundleDebugAar'.
> Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error).
The error seems to be thrown from the camera_deep_ar plugin. Try rebuilding the Flutter project to check if this can solve the references in the project. To do this, run flutter clean then flutter pub get.

I am having this error in flutter while using google map through dependency map_view kindly help me

The Android Gradle plugin supports only Kotlin Gradle plugin version 1.3.10 and higher.
The following dependencies do not satisfy the required version:
project ':map_view' -> org.jetbrains.kotlin:kotlin-gradle-plugin:1.2.50
Your gradle plugin version that is supported in your project is 1.3.10 and higher, the plugin you are trying to install is using gradle 1.2.50 there for not supported. I suggest you find another plugin since the only map view plugin i found states that is discontinued. I suggest when you pick a plugin to use to check how often it get updated and when the last update happent.

Reference Local Path Package in Dart-Web Application

I sucessfully split up a flutter mobile application in to packages. One package is referenced by the flutter mobile app by using the following in the pubspec.yaml:
app:
path: /path/app
The fultter app builds and runs just fine and no problem is reported by the IDE (visual code) when it does the 'pub get'
When I do the same thing in the web-project the IDE complains on 'pub get' with:
Error on line 8, column 5 of pubspec.yaml: A version constraint must be a string.
When trying to build web project by issuing the command:
webdev build
I get the following error:
build_web_compilers:entrypoint on web/main.dart (cached): Unable to find modules for some sources, this is usually the result of either a
bad import, a missing dependency in a package (or possibly a dev_dependency
needs to move to a real dependency), or a build failure (if importing a
generated file).
I even tried to use Windows native top level path (C:\path\package) but without a changed outcome. It seems that webdev does not support local path packages like described by the official PackageDependencies | Dart manual page.
When using shorthand and creating the web project it does not create a dependencies section in the pubspec.yaml file. I added another dependency (package) right under the environment section where the SDK is also configured.
It does not complained about the package dependency being under environment but it complains about a package dependency that has no version but a path.
I only noticed when I used a symlink to add the lib's source folder (lib) directly to the web project as it kept complaining about not finding this said package dependency.
Checking the packages file the package was not mentioned and in the pubspec.lock file the package was listed under the 'sdks:' section.
By creating a 'dependencies:' section and putting both dependencies under it, it now works as intended... . Case closed!

Android Studio Gradle and Plug-in Error

Since the last update, 1.0, I got this problem with gradle:
Gradle project sync failed. Basic Functionality(e.g. editing, debugging) will not work properly.
I also get this plug-in error:
Error:The 'java' plugin has been applied, but it is not compatible with the Android plugins.
How do I recitify this error?
In one of your build scripts, you have both of these lines:
apply plugin: 'java'
apply plugin: 'com.android.application'
Note that the Android plugin in the second line could be 'com.android.library' or possibly 'android' or 'android-library'. In any event this means that you're trying to have both the Java Gradle plugin and the Android Gradle plugin in the same build script, and these two are not compatible with each other. If this module is an Android module, then you need to keep the Android plugin statement; if it's a Java module, keep the Java one.
If you're trying to use some build script plugin or feature in an Android module that requires the Java plugin, then it simply won't work and you'll have to find an alternative.
It's not always that you have two plugins name written sometimes it could be a problem because of updating of SDK i:e updating from sdk 19 to sdk 23.....
you just have to do following in this case....for gradle image solution
Here 23 is given place of 19 just change it in build.gradle file in your Application->src->build.gradle and not in gradle section