Closed GantMan closed 9 years ago
is #18 solving this too @GantMan ?
This looks to be a different issue. (sorry for butting in here)
"play-services" by itself contains no jars inside. Perhaps it only exists as a placeholder to chain dependencies?
If that's that case and jarless aars are a thing, its a quick fix in the same method as #18 changed.
I'm not that familiar with gradle to know without Googling for sure. In theory it makes sense. As does communism.
correct, I doubt that #18 fixed this. I'll try to give it a check when I can, but I'm pretty packed with TODOs on Android right now :(
@GantMan can you try master with the latest fix please (2c45c09d6338f9e0f5a4d646dc7f68b3ae42c9a8) ? And also check if you don"t have regressions on other projects, I didn't find any but...
looks good! thanks bud
@GantMan awesome I will do a release
@GantMan Forgot to tell, I have seen some google play service libs use .aidl files which are not yet supported by RM, we could try to support it directly in motion-gradle if needed I guess, and then backport it in RM, let me know if you do some work that uses a lib with aidl files inside, I could try to fix it.
AIDL files are very important. Not just for this, but it's really biting me/us in a few other places. Elevating the importance of AIDL files would be greatly appreciated.
In an app, you can specify a single, or even a set of google play services
And this will compile just fine.
But should you decide to render ALL google play services
This will pass
gradle:install
but cause the actual application to fail to compile with the error:Seems to be some kind of disconnect in the communication of Gradle files with RMA.