eskimo

If its still not possible, I would like to know when the Swift ABI is planned for enough satbility and sytem level availabilty ?There’s still no official timeline for a stable Swift ABI.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

in my test code something internal to the dispatch library code seems to be deadlocking when large numbers of tasks are dispatchedIf you haven’t already watched WWDC 2015 Session 718 Building Responsive and Efficient Apps with GCD. It explains one common cause for GCD deadlocks (namely, thread explosion).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The value you’re seeing is U+00A0 NO-BREAK SPACE. NSNumberFormatter uses this deliberately because word wrapping at a thousands separator would be very confusing.To achieve your goal you should look at +[NSCharacterSet whitespaceCharacterSet]. There are various ways you can use this to search and replace for whitespace but here’s a one-line drop-in replacement. let trimmed = value.componentsSeparatedByCharactersInSet(NSCharacterSet.whitespaceCharacterSet()).joinWithSeparator()Finally, concerning your goal you wrote:I'm trying to remove all the whitespaces from the NSNumberFormatter string.This is worrying from a localisation standpoint. I don’t have any concrete examples but, given the wide world of locale-specific behaviour, my guess is that there will be at least one place where removing whitespace from a formatted number causes semantic differences.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple

Have you tried to actually load the KEXT using (using kextload)? The fact that kextutil complains that the KEXT is not signed is expected; you have kext-dev-mode so the system will ignore the broken signature. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Are there any other router settings I can try to speed up this discovery process?I’m not able to provide insight into non-Apple kit. On Apple APs there is no UI to configure multicast support; it works out of the box and continues to work as long as the AP is functioning.or there is any other workaround solution for this issue?As I mentioned earlier, restarting the AP often helps.Is this issue is router specific?I’m not sure why you’re asking me that. You started this thread by saying that the problems you’re seeing only occur on some APs, implying that, yes, this is AP-specific.If yes, why the issue happens only with these types of routers?I’m going to quote myself here: I’ve seen lots of problems where buggy Wi-Fi access points (APs) cause Bonjour to misbehave.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

It sounds like your agent has connected to the window server but isn’t responding to window server events.Are you expecting it to have connected to the window server? Typically this happens when you use UI frameworks in your agent.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

How are you validating localised numbers? The only reasonable way to do that is to call NSDateFormatter itself, but that’ll happily ignore the whitespace for you. Validating numbers any other way is challenging (you have to deal with Eastern Arabic numerals, amongst other things).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

There’s a long explanation here but the short answer is that NSHost is not the droid you’re looking for (NSHost is not really the droid anyone is looking for, which is why it’s not part of the iOS SDK). Rather:If you want to a simple interface to the DNS, use CFHost.If you want more control, use DNS-SD (<dns_sd.h>).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

You should definitely file a bug about this. Even if there is some rationale behind it (which is eluding me as well you), it’s obviously getting in the way of your adoption of Swift 2 and thus should be improved.Please post your bug number, just for the record.You can work around this using unsafe goo. Here’s something I cooked up (although I’m hardly an expert in Swift unsafe goo so, folks, please chime in if I’m doing something dumb).func makeScheduledAudioFileRegion() -> ScheduledAudioFileRegion { let tmp = UnsafeMutablePointer<ScheduledAudioFileRegion>.alloc(1) memset(tmp, 0, sizeof(ScheduledAudioFileRegion)) return tmp.move() }Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Thank you Eskimo! But I think I found the bug, and it seems to be in iOS and the way it handles the (now rare case) where the exponent of the RSA key is small. I get my code to work if I change the DER-encoding of the one-byte exponent of the public key from02 01 <exponent>to02 03 00 00 <exponent>dumpasn1 doesn't like this format that the iOS 9 libraries now require, it says Error: Integer has non-DER encoding

Hi Eskimo,Any updates on this? Here's another use case you can use.We connect with WiFi cameras and one of them, that lets you go professional, requires a Wake-on-Lan packet to work. We don't keep the MAC address or use it for identification - we only need it so we can send a Wake-on-Lan magic packet, which as you know requires the MAC address. We already know the fixed IP address of the camera, which is connected via ad hoc wifi to the iPhone.Any help or alternatives would be greatly appreciated.

The advice I give to all NEVPNManager developers is that they first try to configure the VPN using a configuration profile (typically created with Apple Configurator, possibly with custom modifications based on the info in the Configuration Profile Reference). That lets you determine whether the problem you’re seeing relates to your code or to your VPN configuration: if you can’t get things working with a configuration profile, there’s no point investigating your code.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

First of all, you realise this isn’t actually a crash right? Hence the NON-FATAL CONDITION (this is NOT a crash) text in the log.150/sec seems really low for such network provider which potentially need to handle all traffic in the IOS device.Indeed. However, I doubt this report is caused by network traffic because you really should only be waking up once per packet and 41438 packet a second for 300 seconds is a lot of networking for iOS. Was your provider really handling that much traffic?In my experience EXC_RESOURCE reports like this are more commonly the result of a bug the causes the process to continually wake up for an event that’s never serviced (which is why we implemented the EXC_RESOURCE mechanism in the first place). Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

… it seems to be in iOS and the way it handles the (now rare case) where the exponent of the RSA key is small.Weird. Please file a bug and then post your bug number, just for the record.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I was wondering if changing this to until first unlock would have any affect on existing installs of the app as far as NSUserDefaults is concerned once the user updates to the newer version of the app, or will the existing backing store remain at Complete for ever?AFAIK changing the default file protection setting for the app does not change the settings of existing containers that are updated to the new version.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com