Infeasible
Status Update
Comments
wi...@google.com <wi...@google.com> #2
This mentioned interface was removed only starting 7.2
, so you shouldn't have problems with using firebase with AGP 7.1
. Are you sure you don't have a dependency somewhere (maybe buildSrc?) on AGP or just gradle-api
7.2?
wi...@google.com <wi...@google.com> #3
I checked the project and there is no reference to AGP 7.2
I looked in ~/.gradle/caches/modules-2/files-2.1/com.android.tools.build/gradle-api and ~/.gradle/caches/modules-2/files-2.1/com.android.tools.build/gradle
Only 7.1.0-beta04 and 7.1.0-beta05 is there.
I checked with a new project. This problem only occurs when I enable the com.google.gms.google-services
and com.google.firebase.firebase-perf plugin.
Without these plugins everything works fine.
I looked in ~/.gradle/caches/modules-2/files-2.1/com.android.tools.build/gradle-api and ~/.gradle/caches/modules-2/files-2.1/com.android.tools.build/gradle
Only 7.1.0-beta04 and 7.1.0-beta05 is there.
I checked with a new project. This problem only occurs when I enable the com.google.gms.google-services
and com.google.firebase.firebase-perf plugin.
Without these plugins everything works fine.
wi...@google.com <wi...@google.com> #4
This is a known issue, we are working with those teams so they release a compatible plugin.
sh...@google.com <sh...@google.com> #6
When can we expect an update on this?
kv...@google.com <kv...@google.com>
wi...@google.com <wi...@google.com> #7
Last communication from firebase-perf team stated a release is scheduled for this week.
sh...@google.com <sh...@google.com> #8
But it looks like not only perf but androidx.navigation.safeargs.gradle.SafeArgsPlugin
also has this issue.
kv...@google.com <kv...@google.com> #9
Yep, androidx.navigation.safeargs.gradle.SafeArgsPlugin
seems to be an issue too.
Description
When connecting to a SQL Server instance that has "Require SSL/TLS" checked when using the Cloud SQL connectors (proxy binary, or Dialer, or Java JDBC Socket Factory), the connections fail with an error message like:
This is unintended behavior since the Cloud SQL connectors do provide encryption between the client and proxy server. This behavior only occurs with SQL Server - MySQL/Postgres instances are unaffected.
The workaround is to use self-managed SSL/TLS cert when connecting through the Cloud SQL Auth Proxy. There are no known workarounds for the other connectors.