iOS devices not shown after successfully connecting to MAC agent - visual-studio-2013

I am facing strange issue. The xamarin iOS project connects without any error to the MAC agent but the list of iphone is coming empty. Also in the iOS project properties under iOS Build tab shows Requested value 'key' was not found.

Related

Can not debug on simulator or device anymore

I was able to debug my Xamarin.iOS app on my physical device and simulators just fine until this morning. I think it has something to do with the recent iOS update. When I try to deploy to my physical device (iPad) I get this message now:
error HE0003: Could not load the framework 'IBFoundation' (path:
/Applications/Xcode.app/Contents/Frameworks/IBFoundation.framework/IBFoundation):
not found.
And I can't deploy on any simulator anymore, I get this message
Lower the deployment target to see older simulators or check you Apple
SDK path
I didn't have these problems yesterday and I've been working on my app for months without this problem. I updated Visual Studio, Xcode, and my Mac, but these problems still persist. Any idea how to fix?
It is a known issue that you can follow here: https://github.com/xamarin/xamarin-macios/issues/12778
Also there are few workarounds that work mentioned in the issue.

Cannot test Xamarin ios App on device

I have just created an xamarin ios app 'TestApp' for testing on iphone device. The same app created on xcode and deployed succuessfully on both iphone and simulator.
I have created an Apple Id using this .Below image shows the the provisioning profile and signing identity i have created.
Bundle identifier of both mac and windows project are same also. i have followed this link for free provisioning. Appie Id is added to the visualstudio project using fastlane. But when i run this app on visualstudio2017, it just builds successfully; neither deploying to the iphone nor simulator; just builds and run button enables again .no more. How can i deploy the app on device?
Now its working...Tools -> Extensions and Updates-> 'Mono Debugging For Visual Studio' was disabled. I Enabled it and program now deploys to the device ..

Xamarin Forms iOS application always runs on simulator even if I choose a device

I ported my Xamarin Forms project from windows to Mac and I am trying to run it on a connected device which is added in the provisioning profile (provisioning profile and identity is setup accordingly in IOS Bundle Signing settings).
Whenever I try to run the App using Debug|iPhone > my Iphone:
It starts simulator runs on that instead of the device :
After stopping the build if I go back to Bundle Signing settings its changed back to simulator automatically:
I am using following setup:
Visual Studio 2017 Community on Mac 7.2 preview build 540.
XCode 8.3.3
Can anyone please help me with proper configuration to run the app on IPhone?
Many Thanks in advance :)
After hours of messing around I finally found the problem and solution.
In solution settings, iOS project (Debug-iPhone) configuration was mapped to (Debug|Simulator).
Simply changed it to Debug|iPhone and Its working fine now.

Windows iOS simulator [Preview]: unable to install Xamarin iOS app

I need to debug my Xamarin iOS app in iOS Simulator (for Windows), but am getting an error of fail to install
I changed my Mac "Full name" as "Account", but am still getting same error.

XS community 6.1.1 auto close apps on iOS simulator 8.1 after deploy

When I debug and deploy Xamarin.iOS native app to iOS simulator 8.1 through XS(in Mac), it installs app to simulator but it closes automatically after installation. Though app deployment on iOS simulator 10 works fine. This problem is occurred after updating XS to latest version and iOS SDK update to latest version. My iOS app deployment target is 8.0. Also I made sure that Entitlements.plist is empty.
NOTE: Xcode 8 does successful installation on iOS simulator 8.1 and works fine.
Anyone knows why this problem occurs and how to resolve it ?
Clean the project, recompile it and run on simulator.
Additionally, open simulator logs using Cmd + / hotkey and see what exactly is being printed to the simulator logs when you launch your app.
I've seen similar problems which were related to the app crash on launch actually.

Resources