I also modified my cacerts file to include a corpo firewall CA cert, but instead of having to reinstall Android Studio, I just Download the full .zip from Google’s Archive that corresponded to my current version (in my case 3.1.3), then Extract the cacerts file and replaced my modified one. Run the update patch normally. … Read more
The error seems to be caused by corrupt Jetified files. Delete ONLY the corrupted .aar from the Gradle caches folder: rm ~/.gradle/caches/modules-2/files-2.1/path-to/some-release.aar The “path-to” will be probably be the package name e.g., com.example.somerelease Sometimes it is possible to get the path of the file to delete from the error message itself and cut and paste … Read more
For me, the error was appearing due to invalid import statement. Android Studio didn’t show anything regarding the same. I had to go to every single file, then studio shown the invalid import error. Fixed it and the build error’s gone.
You should click on “text” tab in navigation editor (xml file of the navigation graph), and add: tools:layout=”@layout/layout_name” inside destination element. Should be something like this: <fragment android:id=”@+id/someFragment” android:name=”com.freesoulapps.navigationtest.fragments.SomeFragment” android:label=”Some Fragment” tools:layout=”@layout/layout_name”> </fragment>
Beginning with Android Studio 3.2 Canary 11, the source for AAPT2 (Android Asset Packaging Tool 2) is Google’s Maven repository. To use AAPT2, make sure that you have a google() dependency in your build.gradle file, as shown here: buildscript { repositories { google() // here jcenter() } dependencies { classpath ‘com.android.tools.build:gradle:3.2.0-alpha12’ } } allprojects { … Read more
I fix this with two steps 1) File -> Invalidate Caches / restart… 2) Build -> Clean project