Could not find setVariantDir after 4.3.6 #176
Comments
This reverts commit 7a0daa6 Issue: google/play-services-plugins#176
|
The same issue on Gradle version: 6.7.1 and Android Studio version: 4.1.3. |
|
Has anyone found a solution? or should we just wait for google to update something? *I am new here, I have the same error as described by op. |
|
Use version |
|
@MasterMind917
For now changing -- classpath 'com.google.gms:google-services:4.3.6' to -- classpath 'com.google.gms:google-services:4.3.5' works. |
|
thanks for the comment, i did change it to 4.3.5. build is successful after this. but, when I try to use the add firebase authentication sdk button in the firebase assistant it tells me to accept codes dependencies and one of the changes is changing -classpath 'com.google.gms:google-services:4.3.5' to classpath 'com.google.gms:google-services:4.3.6' ------- without accepting this I cannot go ahead with firebase connection. *i have successful connect to firebase part |
|
Try adding Firebase to your Android project without using Firebase Assistant in Android Studio. More information here: https://firebase.google.com/docs/android/setup#console Another option is to wait until a version greater-than |
|
Will try manual connection, but I assume Google might be working on this and maybe they'll release it sooner rather than later. |
|
I wouldn't assume anything about Google if I were you. They have long history of very weird decisions about their libraries, including issues priorities |
|
I have the same issue like MasterMind917 ...and it is my dissertation, bloody Google. |
|
This is easily resolved by just using 4.3.5 for the moment @DaniDana - however, if the google firebase-android-sdk team (which did a release referencing this version) is not aware of this since it is a showstopper referenced in their release notes before Google I/O they might be interested @tejasd @schmidt-sebastian (sorry for pinging but I just picked the top two contributors from last month) ? |
|
Also appears @davidmotson is the core contributor here - tagging just in case |
|
Version Should be available anytime soon on maven.google.com. |
|
Version 4.3.7 is indeed out, i used it as well, but then it gives the following error now. *i have the apply plugin: 'com.google.gms.google-services' in place in the gradle:app |
|
Hey folks, We are working on a fix, will update the issue once it's available, thanks |
|
Perfect! My dissertation deadline is Friday 21st ..firebase is the only option I know how to implement. Hopefully it will be fixed by then. |
|
@DaniDana you should be able to use |
|
I would like to understand the release process of this plugin. Version 4.3.7 is really published to maven repo |
|
Hi folks, we had some release issues this week leading to the problems with 4.3.6 and 4.3.7. We have a fix going live shortly, in 4.3.8, that will resolve the problem. Until then, 4.3.5 is the last good version. |
|
I cannot Auth users with 4.3.5, asks me to upgrade. It is like catch 22. If this issue it is not resolved by the time I need to submit my dissertation, Google will need to tAlk to my university. |
Just downgrade the Auth library. It's not like everything is broken beyond reason. Older versions are working fine and I guess they will for a long time |
|
Quick update: version We'll be looking at ways to prevent such issues in the future. Sorry for the inconvenience |
includes bump to android gradle plugin 4.2.1 and associated lint fix includes bumps to all of the google / firebase gradle plugins
|
i got a simiar issue please can any1 help me. A problem occurred evaluating project ':app'.
` |
|
@eliot19970927 It's not related in any way. It seems like you are trying to call |
Describe the bug
A clear and concise description of what the bug is. Also, if the code base looks familiar, feel free to update the existing tests (or add new ones) in a Fork of the Repo to explain the issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No errors.
Desktop (please complete the following information):
Additional context
See source code.
The text was updated successfully, but these errors were encountered: