Android Studio Canary Build is stuck on Splash Screen on Windows 10 - android

I'm stuck on pop-up splash screen with the loading progress indicator at 100%
I had Android Studio 4.2 Canary 16 previously installed and updated the Kotlin Plugin from 1.4.10 to 1.4.21. After installing the new version of the plugin I closed and restarted Android Studio which then crashed with error saying that the previous version of the Kotlin plugin failed to be uninstalled.
Subsequent restarts would then always crash Android Studio right before loading my Project.
I then uninstalled both the stable and canary(unzipped folder) Android studio programs and followed the steps as per How to completely uninstall Android Studio from windows(v10)?
I then reinstalled the latest Canary build - Arctic Fox 2020.3.1 and then the previous 4.2 Canary 16 but got the same issue on both versions getting stuck in the splash loading screen.
However installing the latest stable 4.1.1 build seems to work just fine. But I need to use the Canary builds to program Jetpack Compose Projects.
Is the canary build generating different files that the stable build does not? If so can I delete them to create to set up a fresh re-install?

This sounds to me alike a file-system permission or exclusive access issue:
the previous version of the Kotlin plugin failed to be uninstalled
You probably have to manually remove some leftovers from the previous install; on Windows these files are literally distributed all over the place. This may even be required when upgrading stable builds, as I recently had it with the "Fabric for Android Studio" plugin. Launching from the command-line might provide some more clue where it gets stuck (with high probability, when scanning the plugin directory). I've just checked; the Jetbrains Toolbox doesn't even uninstall old versions; %USERPROFILE%\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio (may vary) is where to find the plugins and where to check for file-system permissions. Also make sure, that the desktop shortcut actually points to the one version to run - or try to run studio64.exe directly.

Related

After Android Studio Update Bumblebee, The project is not a Gradle-based project

I had fully working Flutter android app. Got an Android Studio update message and updated. Now it shows "The project is not a Gradle-based project" it doesnt detected as flutter dart app. And can't run anymore. How can i fix? build gradle is already exist on android folder and was fully working. Latest Android Studio update caused the problem.
Note: I downloaded previous version (arctic fox) of Android Studio and everything works. Something is wrong in latest version.
I lost an entire morning yesterday after updating to Bumblebee. It broke my Flutter project so badly. I couldn't do Android builds or iOS builds anymore (it was insisting I didn't have cocoa pods installed even though I did - even flutter doctor confirmed I did) and after spending hours trying to fix it all I gave up and went back to Arctic Fox and everything was fine again.
I'm glad it's not just me that's had Flutter problems with Bumblebee.
I suggest rolling back to Arctic Fox and waiting for the next patch release before trying to upgrade again.
As an aside... I'm on an M1 Mac, so I don't know whether there's some compatibility issue with that.
You may wish to try uninstalling and reinstalling your Flutter and Dart plugins in Android Studio, but that didn't work for me.

How to update gradle without android studio?

I have run into some issues with gradlew failing to run in my nativescript application. People have told me that it's a gradle issue and I need to update it, but wherever I search I see instructions for updating gradle using android studio. But I've just installed my SDKs using the sdkmanager and avdmanager. Is there any way to update gradle using them?
I don't want to update my emulator images etc. only gradle.
When you update android studio you should be able to keep settings from past versions I've been using android studio on the same computer for 3 to 4 years and all my old images/ SDKs are still there, plus if you update grade without updating android studio the grade may not be recognized by that version of android studio. If I was in your place I would update android studio to the latest stable version.

Android Studio in Windows 10 not launch after installing Google Sceneform Tools (Beta)

in windows 10 in Android Studio 3.2.1
the application is worked correctly after first time of installing but after installing Google Sceneform Tools (Beta) from :
File > Settings > Plugins > Browse Repositories
after installing the plugin android studio should restart and then it's can't launch anymore
anyone can help please ?
One cannot just use any version of Google Sceneform Tools ​(Beta)​ with any version of Android Studio. As this one comment suggests, even if it's about other versions (also see the other comments there):
A temporary solution: install Android Studio 3.5.1 + Sceneform 1.5, make sfb file, place in project in Android Studio 3.6.
So in your case, you might probably have to update to Android Studio version 3.5.3 or any other version, which works with the current version 1.16.0, as the Android Studio which you are using appears rather outdated.
If you just want to be able to start Android Studio again, then manually delete the plugin directory from %USERPROFILE%/.AndroidStudio3.2/config/plugins, in order to perform a manual uninstall, as it might be required in order to update Android Studio.
Besides "it's not working" is not an error description. You'd have to start Android Studio from the command line, in order to get some meaningful error message, by which you then could search in the issues on GitHub (if the reason why it doesn't start up anymore might have another cause).
I have had issue #377 filed for this plugin since Oct 16, 2018, and unfortunately it is still open now.
I will update this answer if it is solved or a solution is found.
Update 1 :
the github [repository]2 for this plugin has been archived and it seems no longer supported after reading the documentation here

How to get gradl sync going again on Android Studio 3.1

After having this issue on Mac OSX, I reinstalled everything for Android Studio. (Studio itself, SDK's), ... Gradle Sync just does not work anymore. Anybody experiences this also? JAVA SDK Installed is 1.8.0_161.
"Uninitialized object exists on backward branch 70" on gradl sync (see screenshot)
error
android studio version
Bintray was experiencing an outage this morning. This is where a lot of Gradle's Android dependencies are hosted, so it was most likely affecting your Gradle Sync Process. Keep an eye on the status page here, and try again if it turns green. http://status.bintray.com/
This is a bug of JDK old versions. Go to the project structure and change your project to latest JDK version like 1.80_72 or later
After upgrading my Android Studio (on Ubuntu 14.04) to version 3.1.4 I also experienced a build problem:
Gradle sync failed: Uninitialized object exists on backward branch 70
Exception details: error in bytecode
Found out it was due to an old JDK version I have installed locally.
Instead of updating my local JDK I changed the project settings to use the embedded JDK, which, by the way, Android Studio says is the recommended option, and that solved the problem.

Project Doesn't Build in Android Studio 2.3.1 at all

Yesterday I updated my Android Studio version from 2.3 to 2.3.1 and today when I tried to create a New Project this familiar screen should disappear after sometime but it didn't disappeared after 30 minutes of waiting. Anyhow I managed to close android studio by Task Manager and started Android Studio again and created a new project again and the same thing happened again.
Although when I open my previous projects again they are working fine but the problem is with the new project creation only. I am having a good working internet connection along with the latest version of gradle 3.4.1
Any idea why this would be happening?
How to resolve this?
I had this "problem" with android studio but after looking here and there I found out that when I update gradle version for my project, for example from 2.2 to 2.2.1, if I do not have that gradle version already android studio tries to download gradle distribution for that version to build the project and since I have poor internet connection, it was the download which was taking time.
Maybe your android studio is downloading the gradle too and it takes time.

Categories

Resources