iOS8/Simulator - error in SFHFKeychainUtils, SFHFKeychainUtilsErrorDomain error -34018 - ios

I have just downloaded XCode 6 and adjusted my application to run under it.
It seems to work just fine, however I use SFHFKeychainUtils, and when I run the application in the simulator I get the error:
error getting UUID: The operation couldn’t be completed. (SFHFKeychainUtilsErrorDomain error -34018.)
Looking at the code, I'm not quite sure why I would get that error. I also do not get that error running my application on an iOS7 device running from XCode6, just the simulator, so I think it's an iOS 8 error.
Any thoughts on resolving this?

Error code 34018. It happens when client has neither application-identifier nor keychain-access-groups entitlements.
iOS 8 is BETA version and doesn’t support Keychain Access developer APIs on the simulator at the moment.
iOS 8 beta Release Notes

Related

iOS extension "Failed to find a valid app with bundleID" & "Error was encountered trying to find service extension"

We have an extension in our iOS project (Broadcast Upload Extension). The extension works well when doing local builds, however whenever we do a TestFlight build a distribute it we encounter following exception (found in device logs):
Error getting proxy for beta app with bundleID
com.foo.bar.screenshareextension: Error
Domain=ASDTestFlightFeedbackErrorDomain Code=5 "Failed to find a valid
app with bundleID com.foo.bar.screenshareextension"
UserInfo={NSDebugDescription=Failed to find a valid app with bundleID
com.foo.bar.screenshareextension}
one more error lists:
[com.foo.bar] Error was encountered trying to find service extension:
error=Error Domain=UNErrorDomain Code=1904 "Unknown application"
UserInfo={NSLocalizedDescription=Unknown application}
the bundle IDs are set correctly (meaning the container app has "com.foo.bar" bundle id while the extension has com.foo.bar.extensionname".
The extension is referenced through
var bundleUrl = NSBundle.MainBundle.GetUrlForResource("Foo.iOS.ScreenShareExtension", "appex", "PlugIns");
I can confirm actually that the extension appex file is physically in the archived file for distribution.
The only difference is that the min OS version is set differently in the container app & in the app extension. However when doing local builds this doesn't seem to matter.
What could be the reason for not being able to target the extension? (seems like it's missing?)
ps: we are using Xamarin.Forms
Not sure if this helps: I encountered a similar error today, the reason is that the default build target of the notification extension is 13.6(the latest OS), while my testing device is in 13.5. After I changed the build target, everything works fine.
I've got same error with native Swift code on iPhone 6 (12.4.8).
I'm still not sure what causes this bug, but for me it fixes only by changing device. On iPhone 8 (13.6) the absolutely same code works just fine, rebuilding for iPhone 6 and it's not even trying.

The operation couldn’t be completed. (OSStatus error -54.)

I get the above error when trying to run a project from Xcode on a simulator. When I click details it says:
The operation couldn’t be completed. (OSStatus error -54.)
Domain: NSOSStatusErrorDomain
Code: -54
User Info: {
NSDebugDescription = installForLaunchServices;
"_LSFunction" = "-[_LSInstaller installApplication:atURL:withOptions:installType:reply:]";
"_LSLine" = 717;
}
System Information : macOS Version 10.15.4 (Build 19E287)
Xcode 11.4 (16134)
It was working last night. It worked once this morning. Then it stopped working when I try to run a simulator from not just one project but others as well. What is this error saying and how do I fix it?
Restarting the simulator solved it in my case.
I needed to update my Xcode to 11.4.1. Not sure what happened that made this error occur in the first place when Xcode 11.4 was working fine for weeks, but that solved my problem.
For me, Device/Erase All Content and Settings solved it.
This may happen when no app has registered such a scheme.

Error when uploading nativescript/angular 2 iOS application

Please, someone can help. Since the update of XCODE to 8.1, I get the following error when trying to upload the application to the store : ERROR ITMS-90685: "CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value 'org.nativescript.TNSWidgets' under the iOS application 'careeat.app'."
#Nikolay Tsonev, not exactly the same error. The one you are taking about can be resolved only on rebooting your mac.

Error while running my first IOS app on Xcode

I just created my new iOS project as a single view app and tried running it with no codes added, but there appears just a blank black window in the iOS simulator, and it generates the below error:
"The operation couldn't be completed. (Mach error -308 -(ipc/mig)server died)"
Have a look at this question:
Swift Playground and Simulator Error (ipc/mig) server died, Unable to boot the iOS Simulator
Hopefully that will help you too.

Custom Keyboard: Hub connection error

recently I was playing around with the custom keyboard extension in iOS 8 Beta with Swift (Xcode beta 6), but I keep getting this error when I run it on a simulator, it seems to be quite random and I've no idea what causes it:
plugin com.name.app.extensionName interrupted
Hub connection error Error Domain=NSCocoaErrorDomain Code=4097 "The operation couldn’t be completed. (Cocoa error 4097.)" (connection to service named com.name.app.extensionName) UserInfo=0x7b087720 {NSDebugDescription=connection to service named com.name.app.extensionName}
I have no idea what to do. I can't test the app on a real device at the moment, therefore I'm stuck here. It happens on all types of simulators, I already reset them and restarted Xcode and my computer.
I hope you can give me any advice or maybe even know a fix!
I had this problem in Today Extension written in Objective-C. After updating to XCode 6.0.1 and building my project it started saying about missing ARM64 Architecture. When added arm64 it started working well. Try to play with it
I tried a variety of things to resolve this and ultimately what fixed it was "cleaning" my application (on the "Product" menu). I don't know what that really does, but I "cleaned" it, then restarted the simulator and suddenly everything is working again.

Resources