My ipad2 has beed upgraded to ios6.1.3, and then the Xcode can't recognize this device .
When updating the xcode to 4.5.2,this problem still exists.
So how can I resolve this issue,Please help me.
That's because Xcode 4.5.2 is also outdated. Try this link to Xcode 4.6.2
Related
I recently updated my Visual studio for windows and mac. I also updated the Xcode to 10.2. The visual studio 2017 for windows version is 15.9.11 and the xamarin ios sdk version is 12.4.0.64. My visual studio version of mac 2019 community is 8.0.2 and xamarin ios version is 12.8.0. Why I did these updates is I got a mono version mismatch issue when compiling ios app. After these updates the mono version conflict resolved but now it shows xamarin ios version mismatch error. How can I solve this? I am trying to solve these for some days. Any help is appreciated.
We're using Azure DevOps to build our Xamarin Forms mobile app. This has been working without any problems for weeks now. For some reason I am now getting the following error when we build the iOS project:
MT2002: Failed to resolve "AuthenticationServices.ASWebAuthenticationSession" reference from "Xamarin.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065"
The Android and shared project are working perfectly. This is only a problem with the iOS project.
I haven't changed or updated Xamarin.iOS in any way whatsoever, so cannot understand why I am now getting this error.
I am using Visual Studio 2017 15.8.1 if that makes any difference.
I suspect the error first occurred after adding a reference to Microsoft.Identity.Client preview in the shared project. Is there an issue with this reference and Xamarin.iOS on Azure DevOps?
I had the same issues, and had to downgrade to version 2.1.0-preview.
2.2.0, 2.2.1 and 2.3.0 give the same error.
I had the same issue on Azure DevOps. I have updated mono version from 5.10 to 5.18.1 and build was succeeded.
I had the exact same issue. I downgraded my "Microsoft.Identity.Client" package from 2.3.1 to 2.1.0. My Xamarin.forms project version had to be 3.0.0 for this to work.
Hope this helps.
I have the same error with microsoft.identitymodel.clients.activedirectory 4.3.0 as well.
That package is also able to save tokens in MSAL-format so perhaps it is also using AuthenticationServices.ASWebAuthenticationSession.
AppCenter won't build at all since it's outdated and Azure DevOps fails with this.
You need to have Visual Studio 2017, at least 15.8.7, which has support for XCode10, and XCode10 installed on the Mac to get the classes needed to run ASWebAuthenticationSession (ex. AuthenticationServices). If you still have issues, please open an issue on the MSAL repo.
I have both Xcode 4.5.2 & Xcode 4.6 and also an iPod with iOS 6.1.3.
Now when I connect the device and use Xcode 4.6 - device is detected.
But the device is not detected with Xcode 4.5.2 .
Please note both versions of Xcode have exactly the same SDKs.
Any idea ???
Thanks!
The above process regarding copying the SDKs work perfectly. I just restarted my machine.
My old installation of Xcode was working full, but i try to upgrade the Xcode to use iOS 6, so i downloaded the new version in Mac App Store, but my iOS Simulator stop working now, he said me that he could not find the SDK and that the sdk may need to be reinstalled.
I remove Xcode and reinstalled, but the problem still with my iOS simulator, and all the possible solutions that i found in the web don't work for me
Try going to the downloads section in settings.
It's in: Xcode>Preferences> click Downloads tab. The supported simulators are in there.
Can I run the Android SDK emulators for Android website testing in Aptana Studio 3?
Do I need to install the Eclipse plugin?
I have installed Android SDK, and use Aptana Studio 3, but I am not sure if they will work together.
Thanks in advance
Ant
I don't see a major conflict by installing both plugins into Eclipse.
Aptana Studio's 'younger brother', Titanium Studio, can run both, so no real reason why the studio wouldn't run both as well.
In any case, if you stumble into issues like that, you can open a ticket at http://jira.appcelerator.org/secure/CreateIssue!default.jspa