Cannot Deploy Xamarin Forms iOS App on Real device for Debugging on Windows - xamarin.ios

I am not able to deploy Xamarin iOS app on Real Device.
Here is my Visual Studio Details
Getting the Following Log in Output window
I have gone through every possible solution but no luck.
Creating New Certificate and Provisioning profle
Using Automatic Provisioning profile
Clearing all Cache
Nothing seems working

To build for Xamarin.iOS, you need Xcode, and therefore you need macOS. From Xamarin.iOS Installation guide:
To build for Xamarin.iOS, the following are required:
the latest version of Visual Studio
the latest iOS SDK
the latest version of Xcode
the minimum version of macOS required by Xcode

You can use Automatic Provisioning、Manual Provisioning、Free
Provisioning to deploy to real devices
For more information, please refer to
https://learn.microsoft.com/en-us/xamarin/ios/get-started/installation/device-provisioning/

Related

Visual Studio Mac Won't Show iOS Simulators

I've got a Xamarin Forms solution with iOS and Android projects. The iOS side was working, I switched over and did a bunch of work on the Android side. Now I need to do some more iOS stuff (push notifications) and I can't get the iOS Simulator to kick in. Xcode is installed, VS says it can see the SDK. I can open the simulator from XC but inside VS no matter what Debug combination of the .iOS project I select all I get is "Generic Simulator". Any ideas?
Try Unload the IOS Project and Reload and Set as a Startup Project, it works for me
See the answer in the comment provided by #lowleetak:
Is the minimum supported version in Info.plist less than or equal to
the version of iOS Simulator that you have?
This was the issue. The project settings listed 10.2 as the target SDK but the info.plist file had 10.3 which wasn't installed on the machine via Xcode. The machine has Xcode 8.2.1 and iOS 10.2 installed.
Additionally there's now a bug opened about this behavior. If the two fields are going to allow different values there should at least be a warning next to them about the mismatch.
I also showed Generic Simulator only on my project after updating to XCode 14 early. At the release of XCode 14 the stable Visual Studio for Mac (Xamarin) release did not yet support this version of XCode. Even the preview channel was not yet ready. Guidance from Xamarin.iOS discussion group was that the special XCode14 channel could be used to evaluate. https://github.com/xamarin/xamarin-macios/issues/15954

iOS build fails in Xamarin Activation step after upgrading to Xcode 8.0 on the agent

I have a mac setup as a Xamarin build agent for Visual Studio and Visual Studio Team Services (VSTS). On Friday, Xcode updated itself to 8.0 with the iOS 10 SDK. This, of course broke everything. I managed to get Visual Studio to reconnect after upgrading both Xamarin iOS on the mac and Xamarin for Visual Studio.
Now, my only issue that is that the VSTS agent fails to build. This agent runs on the same machine as the Visual Studio agent that works (e.g. I can build in Visual Studio and it builds on the mac and gives me an ipa). I haven't changed any build settings since the upgrade.
Here is where it fails, in the Xamarin Activation build step:
Yes, I double and triple checked that the XamarinPassword variable is correct. In fact, if I enter the wrong password, it will fail with an invalid login error.
Here is the error:
******************************************************************************
Starting: Activate Xamarin license
******************************************************************************
warning MT0061: No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': /Applications/Xcode.app/Contents/Developer
error MT0052: No command specified.
/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mtouch --datafile
Xamarin.iOS 10.0.0 using framework: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator0.0.sdk
Failed to activate Xamarin license. {"code":1,"message":"An internal error occurred. Please email us at contact#xamarin.com and make sure to include the address associated with your Xamarin account ."}
Return code: 1
Is the VSTS agent ready for iOS 10? Should I downgrade everything back to before Friday and before the Xcode 8.0 update? Am I missing something new in the configuration?
The solution is that you can remove Xamarin license task, because it is no longer needed to build Xamarin app. (refer to this article)

using push notification using on visual studio on genymotion

I followed the link given below:
https://azure.microsoft.com/en-in/documentation/articles/app-service-mobile-cordova-get-started-push/#optional-configure-and-run-the-app-on-android
I also built the quick start azure project as said by your tutorial.
Now that I am trying to run the app on genymotion emulator (I have installed google play services in it) the build is giving me many errors
please click on the link of the image to see the errors
PS: The process is giving build errors so using genymotion is actually not a problem
Someone please help
The error indicates that you are missing a dependency from the Android SDK. Open up the Android SDK Manager and install google play services. If you installed the Android SDK as part of the Visual Studio install, you may need to run the SDK Manager as Administrator to do the install.

Xamarin set up IOS build host

I am using visual studio for Xamarin development and I have a business license for both Android and IOS. The Android version of my project is nearing completion and I want to begin development on the IOS version.
I am following the process listed in the requirements and installation section of the below link:
http://developer.xamarin.com/guides/ios/getting_started/installation/windows/introduction_to_xamarin_ios_for_visual_studio/
I have added my Apple Account ID to XCode however as far as I can tell you need to manually assign an IOS Certificate to the build hosts keychain to beable to build from visual studio
If you are using Visual Studio for Xamarin.iOS development, you also
have the option of provisioning manually using the Apple Developer
Portal.
Now as far as I can tell this has a $99 cost involved? Is this fee mandatory before I can build any IOS apps from visual studio ?
EDIT:
After pairing the build host and building my app it seems my suspicions are confirmed. A IOS Development Certificate
stored in the keychain is required
As far as i know you don't actually need the iOS Certificates for developing with Visual Studio and the build host, as long as you're running your app on the iOS simulator. However, as soon as you want to test your app on a real device you need the certificates. And just a reminder, you should test on real devices as soon as possible. I got some really bad surprises after developing exclusively on the simulator for more than 6 weeks ...

Is there a way to remotely build Xamarin.iOS with sdk 6.1 in VS2012?

I have an iOS project that was developed for iOS6.1 and I need to be able to build it for both iOS6.1 and iOS7. I updated all tools from Xamarin and upgraded to OSX Mavericks and iOS 7.0.3 on the iPhone. So at this time I have all latest versions.
When I start to debug the project from VS2012, the app that starts on the iPhone is always an iOS7 app. I added the iOS6.1.sdk to Xcode 5 so back on the Windows machine I can select this SDK in VS2012 for compilation.
But it seems that, whatever SDK I choose in the project settings, it always returns:
-debug -linksdkonly-sdk "7.0"-targetver "6.1" --abi=armv7 (arguments taken from the mtbserver.log on the building host)
If I build the project with Xamarin Studio on the Mac the behavior is as expecting when changing the version of the SDK.
Is there a way to get around this when building remotely with VS2012?
That's a bit uncommon and it sounds like a bug - you should file it on bugzilla so it will be confirmed (and fixed if it's the case).
Most people I know install several Xcode side-by-side, i.e. they do not copy an old .sdk directory into a newer Xcode release.
You might want to try this (the trick is to rename Xcode.app before installing the new one) and then set the VS addin to the older (e.g. Xcode46.app) directory when you need to build for iOS 6.1.

Resources