Using android studio on an apple silicon mac, I signed in using my google account, then downloaded some apps to try them. Once I closed and then reopened the app, I was signed out and the apps were gone. Is this intentional? If so, how do I fix it. If it's not intentional, what have I done wrong?
I tried pressing command+S to see if that would save it. It flashed the screen white but still didn't save.
Related
I upgraded to Android Studio Bumblebee 2021.1.1 and realized that I cannot fully control the emulator with the touchscreen of my notebook anymore. Press events on the touchscreen (like mouse clicks) are still recognized correctly, but when I swipe nothing happens in the emulator.
Unfortunately, I did not note down the previous version of Android Studio that I had installed before, but with previous Android Studio versions I was always able to fully control the Android emulator via the touchscreen (as if I was actually testing my app on a real mobile phone).
My Google searches did not show any results related to this issue. Does anyone have an idea what the root cause could be and if it is possible to fix it?
Disabling launch in tool window in Settings::Tools::Emulator fixed it for me (requires emulator restart to take effect).
Credits to YuriBlaise on reddit
First post--be gentle. Can't find any posts on Android Studio 4.0, so I hope this isn't a repeat. I updated Android Studio from 3.6.3 to 4.0 on Windows 10 (1909). Had created a couple of virtual devices in 3.6.3 (a Pixel 2 running API 28 and a Pixel 3 running API 29)--both worked great in AS-3.6.3 and I could develop apps, compile, load, and run them with no problem.
After the update to AS-4.0, the virtual devices no longer appear in the devices box at the top of the GUI--it just says "No Devices". When I open the AVD Manager, I can see them, and I can start them (although when I start them I get a pop-up saying "AVD Manager: Unable to locate adb"), but I can't get any code to download and execute on it. On the Pixel 3 emulator, I also get another pop-up saying "Detected ADB: Could not automatically detect an ADB binary.", and it gives instructions to resolve it, which don't make any difference (jump into extended controls and toggle "Use detected ADB location").
When I try to open a past project and run it, I get the same behavior--no devices found.
I've also tried making new emulators, hoping the new setup would recognize them, but to no avail. Tried starting and restarting AS, as well as the computer, also to no avail. I have Android SDK Build-Tools 30-rc4, the latest Android SDK Command-line Tools, Android Emulator 30.0.12 Android SDK Platform-Tools 30.0.1, and the Intel x86 Emulator Accelerator all installed.
I've Googled and spoken words of fierce power over this for several days now. Any suggestions for how to get AS-4.0 to recognize the emulators? I've resisted uninstalling everything and starting over--was hoping it was just a configuration thing.
Thanks in advance,
Uber
After some more Googling, I found the answer here (I think my constraint of wanting an answer for AS-4.0 specifically kept me from finding it):
Could not automatically detect an ADB binary - Android Studio
I had to redownload the SDK platform-tools zip file and reinstall it. I don't know why the old one got messed up with the migration from AS-3.6.3 to 4.0, but there you go--such is life with complicated software.
As soon as I replaced the old platform-tools directory with the new one, all my old emulators showed up and I was back in business.
Thanks anyway!
Uber
A young friend of mine would like to push a game created using www.buildbox.com to his Samsung Android Tablet. He is using Windows 10 and Android Studio 3.6.1.
But the Device Drop Down is greyed out and for some reason the AVD Manager, the SDK Manager and the Connection Assistant are missing from this tools menu.
On my Android Studio 3.4 I can still see the Connection Assistant
I checked the Release notes but could not find anything.
https://developer.android.com/studio/releases
I checked that Windows can see the tablet as a USB device and the friend told me that developer mode is enabled.
Any ideas what is going on ?
So I got a chance to look further into the problem.
It turned out, that the problem seems to be with Buildbox not generating a proper Android project. In particular the generated project is missing a proper module and a proper app configuration. Once I added those the missing connection tool reappeared.
However I still got an error.
I am using an old smartphone as a device to run my app on in Android Studio. I recently switched to a new computer, so I reinstalled AS on that computer according to the docs. Android Studio recognises my device, but I'm nota ble to run my (Flutter) app on it, and the name of the device is marked with a small green dot.
I'm not entirely sure if that was the problem causing this, but AS said that my Dart SDK was not installed. After installing and restarting, I was able to use a device to run my Flutter app.
I just clicked the update button on Android Studio. It downloaded packages and it got stuck at the point shown in the image.
I had the very same issue on MacOS High Sierra while updating Android Wear x86 Oreo emulator image.
Since the updating window blocked me from using Android Studio, I got out of patience and hit the cancel button. The "stopping" operation of this apparently non cancellable operation continued for minutes in the background (showing at the bottom of the IDE), and then finally finished.
It seems the operation was not cancellable since there was no update to do aftewards, so if the emulator image patching operation is taking time, "cancelling" it to get use of your IDE back is the way to go as of Android Studio 3.1 Canary 9
I have similar issue just now on Windows and Mac OS, and my solution is by removing manually, related system image that required update, from Tools menu => SDK Manager => SDK Platforms. Then re-install this system image after that from the same menu.
check your internet connection if it not works then force quit it and clear cache and restart android studio then update it again