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.
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 need to completely reinstall Xcode 6 and remove all the files and settings with it.
I know that it is uninstalled so that you go to mission control, long click on it and then click on the X button, like on iPhone.
I also know that you can drag it to trash from applications.
But after all those, when I install it again through AppStore and open the last project I was working on, Xcode will open the project on exactly the same class where i t was shut down and even show the last error I faced!
I don't want that. That means that some User Preferences are still saved somewhere and I want to get rid of them as I have never ever had Xcode installed on my Mac.
How to do that?
You can use several uninstall programs like you would uninstall any other Mac application.
So some examples might be App Cleaner or Clean My Mac.
Hope that helps :)
I am using Xcode 5.0.2 and yesterday I did nothing special but used its source control function to check out and update from svn.
Today, Xcode continues crashing over and over again when it launches. I googled a solution that is disabling the source control in Xcode's Preference.
But since it crashes when it launches, I don't have change to go into the Preference Panel to do the operations.
So is there command that I can do in Terminal to disable the source control of Xcode?
!!!UPDATE:
actually this is not the real problem I ran into. I thought my Xcode crash because of the source control issue. So I send this post and got an answer quickly. Thanks #zzyclark .
But after I did as the post in the link said, my Xcode still crash. I've used other way and got the problem done.
I am gonna keep this post for the people who really want to disable Xcode source control in Terminal.
But if the admin think this is not the propriety. You could delete this post.
rather than close it in terminal, can u check this. This is used to disable the version control of xcode 4 by modifying the file name extension.Can you disable version control integration in Xcode 4
So I'm horribly confused by this error, other threads on Stack Overflow mention I should set the SDK, but I see no option to do this. I'm trying to build:http://wafflesoftware.net/shortcut/
And I get no options, and I can only choose My Mac 64-bit, and I want it in 32-bit. Really beginning to hate Xcode 4.
Here is the screenshot when I try to edit my scheme: http://groovyape.com/scheme.png
Thoughts?
Firstly, I have observed that when Xcode 4 decides my Mac is 64 bit and all my other schemes have vanished, a restart of Xcode fixes that.
If you still have the issue after a restart, go to Manage Schemes... (under the Product Menu) and click on Autocreate Schemes now button. Try to delete the other schemes and see if you can run the project now.
However, if the issue is that you need to set the SDK, that's different:
Click on the top-level project icon in the left hand panel
In the right hand panel that appears, select Build Settings (near the top).
Select "All" option (instead of Combined)
Ensure Base SDK is set appropriately, like "OS X 10.7".
FWIW I'm seriously considering reverting to Xcode 3.2.5 at the moment, 4 seems horrendously buggy.
In xCode 4.4.1, use Validate Settings to solve the problem!
I can select either 32bit or 64bit now.
Ran into the same error message ("The selected run destination is not valid for this action") when attempting to use XCode 4 to build/run a tiny Objective-C "Hello, World" project I created in XCode 3.x. Fixed it by choosing to "Manage Schemes..." from the drop-down menu to the right of the Stop button, deleting the one scheme on the list (click checkbox beside the scheme, then click the "-" button at the bottom left), and then clicking "Autocreate Schemes Now".
I also needed to change the "Base SDK" from 10.5 to 10.6, by clicking on 'folder' icon (beneath the Run button), clicking the root/top of the tree view below it, clicking on the blue icon below "PROJECT" in the pane just to the right, and then finally, choosing "Latest Mac OS X (Mac OS X 10.6)" to the right of that.
I had this issue today. I found switching Base SDK from Latest iOS (4.3) to iOS 4.3 fixed everything.
This will happen if XCode believes your mac is a 64-bit machine, when really it's a 32-bit. If this is the case for you, simply click on your project icon from the far-left pane - it's the menu item that displays your project name next to a little blue icon. This should bring up a center pane that says "PROJECT" at the top. Highlight your project name, and the third pane should now show your build settings. The first item is "Architectures" which will allow you to specify if you are building a 32-bit or 64-bit application.
Kind of amazing that none of the answers here solved the issue for me, but I figured it out. Forget restarting Xcode, or using Autocreate Schemes, still only 64-bit will show up as a valid destination in the scheme.
The correct solution is to change the Architecture for your project. Go to Build Settings (in the root node of your project), and change Architecture to 32-bit Intel, it's right above the Base SDK setting. Destination will instantly switch to "My Mac 32-bit". HTH somebody.
It sounds as if you're trying to run (Cmd-R or run button) the framework (which you can't do - it's not an executable, just a library) rather than simply build it (Cmd-B).
I had this issue and maybe it was a coincidence but when I restarted XC4 but this time didn't choose to load my project from the popup window that appears on launch - instead choosing it explicitly from the File menu - the issue didn't occur and the build started ok.
On the 3 or 4 occasions I had this error, I had chosen to load the project from the popup window that appears when XC4 first loads.
As I say, I might have just got lucky, but I certainly didn't make any other changes to the projects to 'fix' the issue.
I found a good practice for moving from Xcode 3.2.X to Xcode 4 is, to remove any references to older SDKs (in the case of Mac OS to remove any Base SDK Ref, etc., for Mac OS <= 10.5, in the case of iOS I think you need to remove everything <= 4.3) PRIOR to upgrading to Xcode 4.
I never experienced any problems for new Projects, created in Xcode 4, only for such that where created with Xcode 3.X or 2.X
Xcode 4.5. I was trying to compile for 10.6. It seemed to be stuck on 64 bit just because it couldn't find the sdk. I didn't get any message about it not finding the sdk.
I first tried to put in the correct path to /Developer-3.2.6/SDKs/MacOSX10.6.sdk but xcode didn't want to find it there. Then I copied that folder into 4.5 next to the other OSX Platform sdk (new location I think just look in the bundle).
And magically my 32 bit came back.
So my conclusion is that the 32/64 bit option is really dependent on whether xcode can verify the sdk that you're trying to use. Being stuck at 64 while trying to compile for 32 gives the error without notifying you that its first issue is that the sdk can't be found.
I fixed this by deleting my xcuserdata in my Project file. Not sure how it got corrupt. But it worked for everyone else in the office, deleting the xcuserdata did the trick. I made sure Xcode was closed while doing so. Just for fun, make sure you delete your DerivedData folder for the app, and do a build clean for superstitious folks.
If this happened after you renamed your app, go to Schemes -> Edit Scheme -> Run <YourApp> -> Info
Select the right executable file (YourApp.app)
Another way is to select None as executable and then reselect the YourApp.app from your Debug-iPhoneOS folder.