Open fulcrum6378 opened 1 year ago
Same here...
Oh I didn't see this issue before: https://github.com/tommybuonomo/dotsindicator/issues/170
At least I know when this happened, which is when the project version went from 4.2 to 4.3.
I compared the related commits to v4.2 and v4.3 releases and the only Gradle-related changes that had been done were 2 things:
Here's another guy in StackOverflow with the same situation (the 2nd one above) and the same problem: https://stackoverflow.com/questions/64758477/android-buildtypes-vs-productflavors-error The guy had upgraded from AGP 3.5.x to 4.10 (and to Gradle 6.5). So it seems that it would throw the same error on a custom build flavor too!!
Using this guide, I found a solution for the module which implements a custom build variant: https://developer.android.com/build/build-variants#resolve_matching_errors
buildTypes {
create("debuggee") {
...
matchingFallbacks += listOf("debug")
}
}
buildTypes {
debuggee {
...
matchingFallbacks = ['debug']
}
}
But is there a solution for the library NOT TO REQUIRE ALL THESE EFFORTS, just like the other libraries?
First of all, thank you for developing such a useful utility. I've been using it for a year.
Because of some app signing reasons I had to make a very simple custom build type: "debuggee" instead of "debug". Like this:
At first I used the version 4.2 and everything was fine. But when you released the versions 4.3 and even 5.0 and I upgraded, I always encountered a weird error in the assembleDebugee Gradle process (not the initial build). It's been months since I encounter this error, therefore I downgraded it to 4.2 and suppressed the upgrade warning using "//noinspection GradleDependency".
Summary:
Here's a complete log of the assembleDebuggee Gradle process: build log.txt
There is also a weird warning every time I switch between build types, no matter it is release, debug or debuggee: warning.txt
Thank you again.