No devices attached in xamarin VisualStudio for ios - xamarin.ios

I'm having real trouble when I try to use the IOS emulator from the visual studio. So I created a hello world app in VS using xamarin (latest stable version), I set the project as main project, and When I refresh the connexion with the mac, I can't select the device that should be shown in the selectList. The message is "No device attached" :
And if I try to use xamarin studio on the host mac, all is okay, the sample app builds on the iphone emulator:
Thanks to help me !

I know this question has already been answered, but i found it when i had a problem, and it did not help... but i did find the solution:
Under the debugging menu in VS2012, click on Configuration Manager
make sure that iPhone Simulator (or iPad, if you want) is set...
Default seems to be looking for a physical device...
hope this helps.

Are you sure the device is connected to the Mac and not the Windows machine? Have you tried debugging from that same device from Xamarin Studio on the Mac?

Had the same problem. Issue was when i loaded my solution, visual studio 2012 decided to choose a library project as the 'Startup project'.
Rt Clicked the ios project, chose 'Set as StartUp Project' and the device list was populated.
P.S: Visual Studio you should be old enough to figure this out by now.

When I ran into this problem, I had another instance of visual studio running which was connected to the Mac.
Apparently you can only have on VS instance connected at a time.
Check your server log in Visual Studio output window for some more clues:
Closing the other instance of Visual Studio allowed me to connect in the instance I wanted to debug in

I discovered something missing. For me, in Visual Studio 2013, for some reason they have removed Solution Platforms from the toolbar. This makes it impossible to switch from iPhone to iPhoneSimulator without opening Configuration Manager. So, to fix this.
Click TOOLS/Customize then select the 'Commands' tab then select the 'Toolbar:' radio button and click the dropdown to the right of it and select 'Standard' as the toolbar you're working on.
Now, click 'Add Command' and select 'Build' from the catagories on the left and then scroll down commands until you find 'Solution Platforms'. Select that one and click OK. Then click the 'Close' button. You will now see an additional dropdown next to the Solution Configurations dropdown on your Standard Toolbar.
This will allow you to easily switch from iPhoneSimulator and iPhone. Use iPhone when you want to plug in an actual device, and use iPhoneSimulator when you want to pick a simulated device.
Hope this helps somebody out. I too have spent lots of time trying to figure this one out when I went from a device and was trying to use the simulator instead.

Restarting of Visual Studio 2010 worked for me.

Different things worked for me (Windows 8.1 & Visual Studio 2013):
Restart Visual Studio
Set 'iPhoneSimulator' as platform (only working one)
In Properties - iOS Application change 'Deployment Target' version to some lower number (6.0 worked for me).

As well as checking you have the right startup project selected as per #Chamkila's answer, check that you haven't accidentally broken your project's Info.plist file by attempting to open it through Visual Studio.

Related

Annoying "Create Desktop Entry" popup in Android Studio on Ubuntu 16.04

Recenty I installed Android Studio on my laptop running Ubuntu 16.04.
When I created a new project and used Android Studio, this annoying popup kept showing: (Because my low reputation, I cannot post images, please click the link below)
https://i.stack.imgur.com/zNMbk.png
I tried to check the checkbox but it still display everytime I click on anywhere in Android Studio.
Help me, thanks in advance.
Try to use this for creating a desktop entry: desktop-file-install THE_DESKTOP_FILENAME_HERE.desktop
It might be the solution (if error it's because it localized the fileB, if ok it will copy to the correct localization /usr/share/applications) Restart then
After trying many times, I decided to reinstall Android Studio and the error disappeared! I don't know the reason clearly but maybe using Create Desktop Entry in Android Studio and creating a .desktop file manually (after installing Android Studio, I wanted to add Android Studio icon to launcher) caused conflicts.
goto settings in android studio
keymap-> main menu-> tools-> create desk entry
right-click on "create desktop entry"
you will get an option to turn off it.

Android Studio won't run application from studio ide?

I've got an application I've been working on and am having an issue with android studio. When I click "build->run" and then select my device, the application never runs on my phone (and the log in android-studio that automatically comes up does not have anything, whereas in the past when I have used this feature it usually says something like, "waiting for phone..." and then the application pops up and automatically opens on the phone and you get some other pertinent information). I have the phone already in developer mode with the install from unknown sources set to on. When I manually move the application from its gradle build location to the phone and then install it manually in file explorer, all is well and the application performs as expected. As I need to debug, however, this is not a very viable solution. Anybody have any advice as to how to get it to run from the IDE? I have tried rebuilding and invalidating the cache/restarting android studio, to no avail.
When I click the run tab at the bottom I have an empty window. When I click the debug tab, I see:
Waiting for device.
Target device: samsung-samsung_sm_g920a-randomIntegerId
Uploading file
local path: /home/eric/Documents/class/OOSE/final_project/2015-group-17/project_code/android/Place2B/app/build/outputs/apk/app-debug.apk
remote path: /data/local/tmp/oose2017.myApp
Note: I am building the application on a LUbuntu 15.04 VM on a windows 8 host, and am using the latest version of android studio.
EDIT: gradle console indicates a successful build as well (obviously since moving the .apk manually to the device works properly).
Open 'Run->Edit Configurations...', and look for your app module in the column on the left-hand side.
Select it, then go to the 'General' tab.
Under the 'Activity' section, there are a couple of radio buttons. Make sure that 'Launch default activity' is selected.

Terminal on Android Studio not responding

I updated to Android Studio 1.3 and to Windows 10 before that.
Now the issue I am facing is that my local embedded terminal in android studio has some how stopped responding to any kind of user input.
I have tried:
Restarting the android studio
Restarting the PC
Searching through Google for a solution
My Terminal settings
Has anyone ever faced a similar issue?
Is it a Android Studio problem or a Windows problem?
How to solve it?
You may suggest me to use the external terminal as that too will work fine. But that's not the answer I am looking for as it ruins the whole Android Studio experience.
This is an issue with IntelliJ and Windows 10 console.
Here is a workaround from "IntelliJ Idea Terminal broken with Windows 10" thread:
https://stackoverflow.com/a/31716623/703562
Works for Android Studio too.
The workaround:
Open a command-prompt window.
Right click on the title bar.
Select Properties, then check Set legacy mode box, and confirm the dialog.

VMDebugger add-in crashes each time Visual Studio opens up

I'm experiencing the following error each time I open up an instance of VS 2012, for about a week
(so it's not due to the yesterday's Update 4).
Even if I click Yes, the error is shown again when I re-open Visual Studio.
Anyway, the VMWare debugger seems to be correctly loaded
(actually I don't use it, it came with VMWare workstation).
I can't isolate a single operation that caused the error to start appearing.
Anyone is experiencing the same error?
[Edit] See Attilas answer for a much easier solution producing the same result [/Edit]
For anyone who could not solve this problem by re-installing the VMWare plug-in but do not want to sacrifice all his VS settings, here is a solution that did work for me:
Export 'Menu and Command Bar Customizations' VS settings only using
Tools => Import and Export Settings... => Export selected environment settings
Deselect 'All Settings'
Select only 'All Settings/General Settings/Menu and Command Bar Customizations'
Open exported .vssettings file in a text editor, scroll to the end and remove the entry <add_toolbar Menu=... Name='VMware' .../> in the UserCustomizations section
Import edited .vssettings file using
Tools => Import and Export Settings... => Import selected environment settings
and restart Visual Studio to check if the error has gone.
I know this is an old thread, but I solved this problem with a rather simple step. Had the same scenario, clicking Yes in the popup window didn't change a thing.
What worked for me: you should start VS as an administrator, wait for the popup window and click Yes. After that the popup never came up again (even when VS was run as a non-administrator). So there was no need for me to uninstall the VMWare pluging (or the whole VMWare WS).
Run the VMware Workstation installer
Choose Modify/Change
Uncheck Visual Studio Plugin
Problem gone!
Run the VMware Workstation installer
Choose Modify/Change
Check Visual Studio Plugin
Problem back again!
Regards
Lemmy
one possible solution:
Tools => Import and Export Settings => Reset all settings
seems to work for me.
VS 2013
Tools > Customize.. > Toolbars
Here I selected VMware and clicked Delete button.
I really don't use this plugin, this was the easiest solution for me.
None of the solutions here worked for me since I have already uninstalled vmware a long time ago and I was not willing to re-install it again.
MSDN suggests that there should be a registry key under
Root\Software\Microsoft\Visual Studio\...\AddIns\...
for VMdebugger, just delete that entry (the whole folder) and it'll be gone.
This worked for me:
completely uninstall VMWare workstation, reinstall it (select or deselect the VS plugin as you wish)
old school
If the option to install for all users was requested these Registry entries must also be removed.
HKEY_USERS.DEFAULT\Software\Microsoft\VisualStudio\11.0_Config\Addins\VMDebugger.Connect
HKEY_USERS.DEFAULT\Software\Microsoft\VisualStudio\12.0_Config\AddIns\VMDebugger.Connect
They correspond to the following HKCU entries. Hunt and kill.
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config\Addins\VMDebugger.Connect
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\Addins\VMDebugger.Connect
From VS2012 menu bar select [Tools] [Add-in Manager]
Then check mark the radio box to install VMDebugger.
Worked on my system:
Microsoft Visual Studio Professional 2012
Version 11.0.61030.00 Update 4
Microsoft .NET Framework
Version 4.5.51209
Installed Version: Professional
Visual Studio Integrated Virtual Machine Debugger

there was an error attaching the debugger to the role instance

I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.

Resources