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
Related
I have checked the newly opened threads about the issue but none fixed the problem
I am using a mac and I don't understand what should I delete to make it work. Or should I just completely delete the IDE and freshly reinstall it?
I am using Android studio 4.1 on Linux Mint 19.3 after update had the same error.
Some of the plugins(Marketplace and Makrdown) are not compatible with the new version.
Some suggestions were to delete /.local/share/google(but there was no such folder on Linux Mint 19.3)
I solved it by renaming(or deleting) marketplace plugin folder in /home/user/.var/app/com.google.AndroidStudio/data/Google/AndroidStudio4.1
After that Andorid Studio starts normal and plugins can be udated.
I just deleted and reinstalled the IDE and it works fine.
Google should really check their releases before going out official - If I were to work on an important project this would waste many hours for nothing.
I have the adb.exe at "../AppData\Local\Android\Sdk\platform-tools\adb.exe" and even checked the virus chest of antivirus everything is fine.
But still get the dialogue box saying
"adb.exe is obsolete and has serious performance problems".
What worked out for me was after
Create Virtual Device
Choose a device
select Q API Level 29 image with target as Android 10.0 (Google APIs)
not just Android 10.0
and proceed as usual.
Hope its useful for you!
Maybe a bit late but the accepted solution didn't work for me. However the following did:
SDK Manager -> SDK Tools
Delete current Android SDK Build-Tools even if it is the latest version. In my case, I observed it also uninstalled a lot of previous versions
Restart Adroid Studio
Install the latest Android SDK Build-Tools
Restart Adroid Studio
I suspect the problem happened due to some sort of error in incremental updates of adb
First post--be gentle. Can't find any posts on Android Studio 4.0, so I hope this isn't a repeat. I updated Android Studio from 3.6.3 to 4.0 on Windows 10 (1909). Had created a couple of virtual devices in 3.6.3 (a Pixel 2 running API 28 and a Pixel 3 running API 29)--both worked great in AS-3.6.3 and I could develop apps, compile, load, and run them with no problem.
After the update to AS-4.0, the virtual devices no longer appear in the devices box at the top of the GUI--it just says "No Devices". When I open the AVD Manager, I can see them, and I can start them (although when I start them I get a pop-up saying "AVD Manager: Unable to locate adb"), but I can't get any code to download and execute on it. On the Pixel 3 emulator, I also get another pop-up saying "Detected ADB: Could not automatically detect an ADB binary.", and it gives instructions to resolve it, which don't make any difference (jump into extended controls and toggle "Use detected ADB location").
When I try to open a past project and run it, I get the same behavior--no devices found.
I've also tried making new emulators, hoping the new setup would recognize them, but to no avail. Tried starting and restarting AS, as well as the computer, also to no avail. I have Android SDK Build-Tools 30-rc4, the latest Android SDK Command-line Tools, Android Emulator 30.0.12 Android SDK Platform-Tools 30.0.1, and the Intel x86 Emulator Accelerator all installed.
I've Googled and spoken words of fierce power over this for several days now. Any suggestions for how to get AS-4.0 to recognize the emulators? I've resisted uninstalling everything and starting over--was hoping it was just a configuration thing.
Thanks in advance,
Uber
After some more Googling, I found the answer here (I think my constraint of wanting an answer for AS-4.0 specifically kept me from finding it):
Could not automatically detect an ADB binary - Android Studio
I had to redownload the SDK platform-tools zip file and reinstall it. I don't know why the old one got messed up with the migration from AS-3.6.3 to 4.0, but there you go--such is life with complicated software.
As soon as I replaced the old platform-tools directory with the new one, all my old emulators showed up and I was back in business.
Thanks anyway!
Uber
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
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.