Anyone have a problem like this when upgrade Andro...

# android

[Sam]

Anyone have a problem like this when upgrade Android Gradle Plugin to 4x?

com.android.tools.build:gradle:4.0.1 
distributionUrl=https\://services.gradle.org/distributions/gradle-6.1.1-all.zip

My error

Could not resolve all dependencies for configuration ':app:stagingDebugRuntimeClasspath'.
Could not create task ':app:packageProdDebug'.
Could not get unknown property 'outputScope' for task ':app:packageProdDebug' of type com.android.build.gradle.tasks.PackageApplication.

[gildor]

Gradle -> Android Gradle Plugin 😄

[Sam]

Changed, thanks @gildor

[gildor]

Do you have stracktrace? looks that some of your plugins uses some non-public API and this API changed

[Sam]

My current log on AS like this.

[Sam]

Screen Shot 2020-07-20 at 12.55.04.png

[Sam]

I have no idea which plugins is outdate. :((

[gildor]

so it’s an issue of this plugin com.deploygate

[gildor]

see, https://github.com/DeployGate/gradle-deploygate-plugin/issues/100

[gildor]

you should update it

[gildor]

in such cases always check stracktraace to see who actually access missing API

[Sam]

@gildor I’m still stuck on these errors, please help me about this

1. I don’t use constraintlayout-2.0.0-beta2 on my project.
2. Attribute already added in project and run successfully on previous Android Gradle Plugin 3.5.2
Thanks.

[gildor]

I don’t use constraintlayout-2.0.0-beta2 on my project.

But some of your dependencies probably does

[gildor]

It looks that they become more strict about attributes names in 4.0, I also update one of our own attributes to avoid conflict with one from material design

[gildor]

Try add format explitly to attribute

[Sam]

@gildor

I don't use constraintlayout-2.0.0-beta2 on my project.

1. Where can I find it?
2. How to force my project to use specific version (stable version)?
Thanks.

[gildor]

check dependencies graph

[gildor]

How to force my project to use specific version (stable version)?

You can use resolutionStrategy.force but keep in mind, there are new features in constraint layouts 2.0, so it will not run with old version if Flow tag is used for example, and it will crash on runtime, not compile time

[Sam]

Thanks @gildor