I was working smoothly on my mac on Android Studio , when suddenly my studio hanged and stopped working. I re-stared my mac, and when studio relaunched I could not see my project anymore. I have tried everything, only solution was to uninstall and then install which is very long process. No time.
I did it twice though but its happening continously.
Pleas help.
You have to uninstall your Fabric`s plugin and restart Android Studio.
Related
I upgraded to Android studio 4.1.2 and now backspace and enter keys are not working in the terminal window. I haven't changed any keymaps. Any idea why?
Tried several things and nothing worked. Only solution was to uninstall Android Studio and reinstalling it.
I'm new to Android Studios. After trying to press play on my Pixel 3a device emulator on AVD Manager this pops up. Error Message : Unable to locate adb
However my emulator runs just fine, I just can't run the "flutter run" command and the flutter app on the emulator. Emulator
I'm on Android Studios 4.0. Here's what I've tried so far to solve this issue.
AVG Antivirus
I added the adb.exe path in the exception section of my antivirus. AVG Antivirus
Android SDK Location
I went to SDK Manager, pressed edit beside the Android SDK Location box. All SDK components are already updated. Android SDK LocationUpdated SDK Components
SDK Platform Tools
I unchecked and checked SDK Platform Tools on SDK Tools.
Platform Tools
I've tried everything but still no luck. It's been a week and it's getting really annoying. I really do hope someone can help me. Really much appreciate it. Thanks in advance 😊
I've been tearing my hair out about this since I updated to v4.0 about an hour ago! :) This is what worked for me in the end (the other solutions about stopping starting adb server etc. just didn't work at all). YMMV.
Go into SDK manager, and uninstall :
Android Emulator
SDK platform tools
SDK command line tools
Close SDK manager and/or android studio completely.
Make sure the directories for these tools under AppData/ .. /Sdk have all been removed properly. Just zap them if they haven't.
Restart Android Studio and re-install all these packages.
I did another stop/restart after this, just to be sure.
Step 3: Profit!
Seems that upgrading the existing packages maybe didn't work properly, even if AS thought it did.
Still seem to be having issues using the geolocator package now (which was working fine before, so thinking this is setup too), but the emulator is starting OK now with no adb issues.
I tried reinstalling Android SDK after deleting the platform-tools dir but with no success. What did work for me were the following steps:
In Android Studio go to File > Project Structure (Ctrl + Alt + Shift + S in windows);
Under Project Settings>Project>Project SDK must have a valid Android SDK selected;
emulate a new device;
check if the adb daemon is running and recognizes the emulated device: open cmd prompt, run %ANDROID_HOME%\platform-tools\adb.exe devices and it should list the device you have on atm.
If you already have installed the Sdk tools at ~/Android/Sdk, you can add this to your .bashrc or .zshrc, alias adb=/home/USER/Android/Sdk/platform-tools/adb (change USER to your user) and restarting android studio, not invalidate caches/restart but closing it and re-opening it, which should pick the new adb alias from the shell.
The answers didn't work for me. So I removed/uninstalled everything and install a new android studio.
How to remove android studio correcly:
After Updating Android Studio to the version 3.6, I am unable to install an app directly to device by using Run button.
It just updates the gradle and shows gradle updated popup that's it.
I tried invalidating cache and recreating the emulator device but no luck yet.
Let me know if anyone could help as am creating APK and installing it manually in emulator.
I have installed the Android Studio 3.6 and suddenly existing project stopped running. I tried the following thing and it worked.
Android Studio -> Run -> Edit Configurations -> Installation options -> Select Nothing instead of Default apk.
I am not able to post this as comment, but maybe someone finds this info useful.
I faced same problem after updating Android Studio to 3.6.1 on Mac OS.
I tried to use gradle task for installing and launching my application and I found strange log in console about missing adb in platform-tools folder.
So, as result: after update folder platform-tools was moved into folder with same name (was: sdk/platform-tools become: sdk/platform-tools/platform-tools). I just move it manually back and everything is worked as a charm.
Hope it helps.
I have installed Android Studio 3.6 yesterday. I have tried both way to install APK.
Directly by Run button. [DEVICE - Working, Emulator - Working]
Generated APK, Drag and Drop to Emulator. (Its also working)
Hope It will work for you too. Just drag n drop APK file to emulator.
Bonus - May your emulator is older, You can update your Emulator from
SDK Manager and Create New.
Trying to launch the android emulator from android studio using avd manager but it keeps crashing. Sometimes may launch, but would crash after the debug apk is installed. I have Android Studio 3.4. The emulator also behaves very sluggish and extremely slow. How could I accelerate the emulator?
you have to upgrade your react native version to solve OSX problem
Please provide your system details. Meanwhile, try updating all the packages and then run the emulator.
Few days ago, I have update android studio 3.4.
Now, when I open any project or build new project it's stuck on indexing.
I have try many solution like "Invalid catch and restart", remove ".android", remove ".gradle" and remove ".AndroidStudio3.4" folder but still I have facing this issue in android studio 3.4.
When I forcefully close android studio from windows task manager then after android studio not starting again until restart system and task manager in showing android studio running.
How can I solved this issue?
Try reinstalling. No need to uninstall, you just need to follow the steps in the setup to remove that version. If your computer tells you that there are files with the same name then simply overwrite.