I want to use Bluestacks as android studio emulator, but when I try to run app I get this error:
com.android.ddmlib.SyncException: unknown command 'SEND' (444e4553)
Error while Installing APK
I tried adb kill and start server, reinstalling Bluestacks, but nothing helps
I had the same problem and solved it. I had trouble finding an up-to-date Q&A thread so I am glad you asked this question in 2019.
As of 2019, two meaningful changes have occurred that you need to look out for.
Bluestacks has now INTENTIONALLY BLOCKED adb connections out-of-the-box
Android Studio has introduced instant run feature, which may be kinda broken in different development setups
You should check issue 1 first before moving on to checking issue 2
Instructions for issue 1:
Open bluestacks. Find the actual settings for the bluestacks program itself, which is a gear symbol in the grey bar at the top. To do this, select the gear icon, the click "settings". click the preferences tab then make sure "Enable Android Debug Bridge (ADB)" is checked. This should be unchecked by default in newest version of bluestacks.
Instructions for issue 2:
Go to android studio. From the menu items at the top. Click File->Settings, which opens a dialog. Click the "Build, Execution, Deployment" item on the left. THis will expand and you will see "instant run" as a sub option. Click it, then make sure the "enable instant run" checkbox on the right is unchecked.
Finally, as some side pointers:
Always open bluestacks first before android studio. This avoids the need for any adb commands. If you for got this, then do the adb kill-server, adb start-server, but don't forget to run adb connect localhost:5555 after you have killed then started the adb server. Since the sdk/platform-tools is usally in a very strange appdata location, I recommend adding the sdk/platform-tools folder to your path.
I have not tested whether it is actually necessary to disable instant run, if you make sure adb is enabled on bluestacks. You may need to test this for yourself. However I do not know if instant-run is that beneficial so I jsut choose to not use it just in case.
Related
I can't launch my app anymore on Android. The iOS counterpart seems to be fine.
The full error is:
ADB0000: Could not determin the installation path for package.com.company.appname.
'adb shell pm path com.company.appname' returned.
It was working. I pulled some changes from the repo, none of which should have affected any app properties. Actually it was initially launching, but I was getting some odd behavior within the app, so I uninstalled the whole thing off of my phone. Now I cannot launch it at all. What I could find about this error was that my AndroidManifest.xml might have a typo, but I couldn't find anything that stuck out. And like I said, there shouldn't have been any changes in there recently. Any help would be greatly appreciated.
Steps I have already taken:
1. Clean and rebuild
2. restart VS
3. delete obj and bin folders
4. search for solution on here and xamarin forums
UPDATE:
I just successfully launched it on another android device. So it seems to be a problem with my Pixel 2 XL. How do I make sure all traces of the app are gone so I can start fresh?
This usually happens when you have more than one user in an Android device (I still cannot figure out why is this).
As mentioned in the comment by using the adb uninstall full.package.name command it will uninstall the app.
But there's another way which does not require command line or nothing related to that.
If you go to the Settings -> Apps and Notifications on the Android device you will be able to uninstall it from there.
Let's use the UnoQuickStart.Droid app as example here. As you can see it's already in the same state as it was yours.
Once in the App details both Uninstall and Force Stop are disabled. But do you see those 3 dots image at the right upper corner? Click on it.
This will bring you a context menu with a single option "Uninstall for all users". You can click on it with confidence.
As expected, a warning message telling you what's gonna happen. Just click "Ok".
As you can see the App is not longer installed and you will now be able to install it again.
Hope this helps.-
As per apineda's instructions, using adb unistall com.company.appname fixed the problem. I was able to get to the ADB location by navigating through Visual Studio -> Tools -> Android -> Android ADB Command Prompt.
Before I did that, I looked at the App list for my phone, which listed the app, but apparently not installed for this user. The Uninstall and Force Stop buttons were disabled and several of the fields just said loading... or something like that.
I installed Xamarian and have the most recent version of Visual Studio. Every time I open a project that uses Xamarin, I get this message box:
No matter where I click on it, it never takes me to the update page.
1) Do I really need an update?
2) If not, how can I get rid of that dialog box?
Check the icons near your clock, there probably is an Xamarin icon there.
Also if that doesn't work, go to Tools > Options and find the 'Xamarin' page. There should be an 'Check now' link there which should give you a dialog with info!
Here you can also decide whether you want to receive stable, beta or alpha updates. Remember to set the same setting in you Mac counterpart if you are using a Mac build machine, as it uses the Mac agent.
Whether or not you really need the update is up to you! Check out the release notes and decide if it is worth your while to do the upgrade. As far as I know there isn't a way to get rid of the message without upgrading and I don't think you should want that. The upgrade isn't there for nothing, things are better and fixed!
I setup a bot to build the project then test on all the simulators. This has been working, but today the integration had 28 errors. Each said the same thing (but for each simulator device name):
Xcode cannot launch apps on the simulated device “Resizable iPad”, as
it is currently running an app on “iPhone 5s”. Only one simulated
device may be used at a time...
After manually running the bot I received no warnings. What could cause this? (I enjoy the success streak)
I only had one project running and had the same issue. Control Quit out of xcode and start it back up.
I had this same problem. I had multiple projects open and a different one still had
'Running appName on deviceName' displayed
Currently open projects can be accessed from the Window section on the toolbar on top. Pressing the Stop button (or the command from the Product Menu) on any projects that were still 'running' freed that particular device for other projects.
Alternatively, Rebooting Xcode works as it closes all projects.
See: https://stackoverflow.com/a/22267017/5172836
I encountered the same error today with the simulator.
The only way i've find is to reboot Xcode. After that the error disappeared and the application launch corectely in the simulator.
I don't know how the error has been originally produce, but Xcode is not a reliability model, so...
I started to get this error when trying to run my CordovaApp in Debug Mode: Unable to attach.Operation timed out. First i was getting it quite often but still sometimes it was able to attach and now i'm always getting it.
The application is deployed and started successfully in the emulator or on my Android Device.
How can I solve this? Is it possible to increase timeout threshold? (maybe if I wait more it can attach as sometimes it was working before).
EDIT:
Reproducible on 3 different machines.
I had the same issue,
find some workaround that works for me without restarting.
all is done in emulator UI
in the emulator -> apps (show all apps installed including yours that refuse to run)
side bar -> click "menu" and select "Manage Apps"
scroll down to your app
click "clear data" and "force stop"
go back to apps and click on your app.
cross your fingers and wait few seconds ..
hope it's helps
Every time I install a fresh copy of my app on my testing device the debugger is not showing any output. Rebuilding the project solves it.
What could be the problem, or any suggestions how to explore this.
Thanks
After eliminating many options we found that the cause is the voip (Voice Over IP) flag in the UIBackgroundModes inside the info.plist causes this problem.
We have reported Apple about this.
Thanks for any help suggested.
Start by deleting the app from your device and then cleaning your derived data. Do a clean build (Command + Shift + K) and see if that helps.
You should also check your project scheme, by clicking on the scheme, Edit Scheme.... Then check for the debugger settings there.
To run your app, plug in your device, and hit Command + R. The debugger should appear in the bottom corner. If not, hit Command + Shift + Y (in Xcode 4) to bring up the console and debug panels.
Hello i have 3 ways to resolve that:
Check if The phone's name contain's an apostrophe if it has remove it and try again.
Disconnect your device from the MAC. Remove your development provisioning profile from your device, power down the device, wait a minute, power on, reconnect to MAC, and let XCode reinstall profile.
Before do this second way, if you have another device try it, to have sure if it's not from xcode, if it's not the device, try to reinstall xcode, if it's the device, return the device to default factory settings and try it.