-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: FlavorDimension doesn't support more than one dimension, or at least Android Studio doesn't #1590
Comments
Could you share your code snippet and screenshot? |
Like for example
The fact is that the Build Variants are correctly created, but in the "Project Structure" menu the error "Flavor banana has no dimension" pops up, for each module. The build project obviously doesn't work , it seems that something has stop to function, so I kinda think and pull the fault to Android Studio. No amount of Invalidate Cache , clean works against this, so |
@Edodums |
Yep, this is the problem I was talking about. It defies the utility of having gradle plugin and build logic. |
I'm not fully understand this issue, but if the problem is related with Android Studio. Here is not a right place. |
I'll report it but, as you can see that "invalid" I don't get why that happens. |
I can see it, It is hard to know what had been happened in the behind scene. |
Is there an existing issue for this?
Is there a StackOverflow question about this issue?
What happened?
Try to define a second FlavorDimension ( for example "environment" ) ,
Add a flavor, called for "prod”.
Sync, you'll notice no problem is there, build variant are correctly created.
Try now to go to "project structure" and you'll notice that it will tell you that Flavor "x" has no dimension, for each module and for each flavor.
I don't know why this happens but it's making me mad, because it's a recent problem, and it doesn't let me to use succesfully "build project"
Relevant logcat output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: