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.
Related
I want to develop an app for an old tablet using API 7 Android Eclair 2.1, but I'm facing problems setting up all the tools needed.
I tried using Android Studio, but when creating a new app, the lowest API I can choose is 14, and when I change it via code, it complains about the libraries being not compatible.
I also tried importing some samples, but it tries to download some old version of gradle and apparently the link is down.
I recall that prior to Android Studio, one would use Eclipse, but it seems that it is no longer available.
Is it possible to set up a development environment, or am I better to code from scratch and compile it myself?
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
We have a 4 year old MonoTouch application, now a Xamarin.iOS application. It has a tag in each project
<MtouchSdkVersion>3.0</MtouchSdkVersion>
In the list of warnings with the current Xamarin.iOS and Xcode 6.1.1, I see
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets: Warning: The iOS SDK version '3.0' is not installed. Using newer version '8.1' instead'. ({myProjectName})
I could manually update this tag or remove it. I do not see in the Xamarin Studio where to configure this on each project. Thanks much.
That should map to the Project options, Build, iOS Build, General, SDK version combobox.
If not found it could show you Default (not sure about the logic) but, beside Default it will only let you select the SDK that the presently configured Xcode provides (e.g. for Xcode 6.1 would see 8.1 for device builds).
note: it's possible it was left over to that value during the project's conversion to unified (which implies switching to msbuild).
I'm using Xcode 6.1 and I get the error Security/SecAccessControl.h file not found
plus some other errors you can see in the image here. (this is a swift project). The same happens with Objective C projects (just add 10 errors)
These errors occur only when I target my real device, and not when I target the simulator. I have iOS 8.1 installed on the device.
Deployment is set to 8.1
This happens to all projects even new empty projects.
This seems to be a bug in Xcode 6.1 but I'm not sure.
Any fixes/workarounds or preferences I need to know about?
Reinstalling Xcode solved this issue
I have VS2012 Pro Update 3. I've downloaded and installed Windows Phone 8 SDK to create Windows Phone apps for the latest MS smartphone OS (WP8). However, I get the above-mentioned error when I try to create a new Windows Phone App project.
I deinstalled and reinstalled WP8 SDK as suggested on many forums and blogs, and even used the "repair installation" mode for VS2012 and WP8 SDK, but all this did not help.
How to get rid of this error?
P.S. My pc has Windows 8 Pro 64-bit and the CPU supports Hyper-V needed for this development (added this optional component to my Windows successfully). Other common Windows projects, such as WinForms and WPF apps, can be created and compiled without any problems in my dev env.
I solved my puzzle using the trial and errors method. Go to the TOOLS menu, then choose 'Extensions and Updates', then the Update section and install the latest NuGet update. Funny, yes?
My Solution: UNINSTALLED NuGet (as updates to it did not work)
I have installed visual studio 2012 update 3.
Go to the TOOLS menu, then choose 'Extensions and Updates', then the Update section and install visual studio update.