Status Update
No update yet.
Comments
uc...@google.com
de...@activelogic.com
This is to confirm that we plan to resume the rollout of the new cross-signed root CA certificate as described in
The rollout will be very gradual, with incremental launches across the Google Maps Platform services and regions, and its phases will proceed depending on engineering evaluations rather than by a defined timetable. The change will be transparent to the vast majority of Google Maps Platform API clients, including all mainstream maintained OS versions.
For more information, please see the FAQ resources listed in
[Deleted User] <[Deleted User]>
At this stage, the best course of action is to ensure that your client TLS stack can dynamically work with intermediary certificates signed by any of the (~40) root CAs from
In other words, the root CA signing intermediary certificates for requests to
We have published FAQs at the following addresses:
sk...@trading-point.com
Here are several sources that can be used to help you split the root.pem file into 1 file per certificate, if required by your tooling and software environment:
-
-
-
As an immediate fix to get your Google Maps Platform requests working again, the main certificate to install is the "GTS Root R1" certificate, which begins at line 896 in the current roots.pem file. Please note that this issue may reoccur in the future if you don't install all the certificates.
il...@google.com
To help customers using Java or Mozilla NSS, we have updated the Java keytool and NSS certutil sections in our
Description
AI-201.7223.91.42.6568795, JRE 1.8.0_242-release-1644-b3-6222593x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.6, screens 3360x1890, 1440x2560; Retina
AS: 4.2 Canary 1; Kotlin plugin: 1.3.72-release-Studio4.1-4; Android Gradle Plugin: 4.0.0; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read
Issues with Jetpack navigation libraries 2.3.0-alpha06 and above (perhaps lower as well)
I was attempting to integrate Safe Args into my project. Since Android Studio 4.1 I noticed that my main navigation graph was not rendering correctly in the Design Editor. I had the same issue in 4.2 and tried to fix it, to no avail. I just gave up on visualizing my graph and used the XML exclusively.
Now the main problem was integrating SafeArgs. I followed the instructions in the documentation and saw that the actual FragmentDirections classes WERE being generated, but were not compiling in my code.
After trying many steps to fix the issue (clean + rebuild), invalidate-cache + restart, etc I decided to try out AS 4.0 stable.
Both the nav graph and FragmentDirections are displaying/compiling correctly. I also tried using AS 4.1 Beta01, same problem as with AS 4.2.
I can provide additional data as needed.