eskimo

This email address: - networkextension@apple.com as listed in the following document 717_whats_new_in_network_extension_and_vpn.pdf bounces back. Has the email address changed for these requests?No, the email address remains unchanged.By an amazing coincidence I happened to email that address yesterday and it worked for me.Finally, keep in mind that, as I mentioned in my post on 5 Aug, requesting access to NEHotspotHelper is only appropriate if you're actually developing an app to manage a captive network.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

dhoerl sent me the information I was looking for privately.For those reading along at home, the reason why I was seeing weird results is that if you fetch the server's root (https://s3.amazonaws.com) via HTTPS, the server redirects you to an HTTP page. Once I disabled this redirect, I got a lot less confused. I believe that the connection is failing the ATS check because the leaf certificate (not the TLS cypher suite, but the certificate itself) uses SHA-1 (sha1withRSAEncryption) whereas ATS requires SHA-2/256 or better (sha256WithRSAEncryption). This requirement is documented in the ATS Technote, although the discussion is not super clear.What is not documented is that NSExceptionRequiresForwardSecrecy relaxes this check. The docs say that NSExceptionRequiresForwardSecrecy simply enables extra cypher suites and says nothing about relaxing the SHA-2/256 requirement. I've filed a bug to get the docs updated. Anyway, the upshot of all of this is that dhoerl should set NSExceptionRequiresForwardSecrecy until suc

When working with NEVPNManager it's best, in my experience, to try and set things up first using a configuration profile. Once you have that working, you can then try to 'port' the settings to your code.To that end, you should read the VPN sections of Configuration Profile Key Reference. It has an extensive discussion of the on-demand rules.If you can't get things to work with a configuration profile, you should post over in one of the in Business and Education sections of the Apple Support Communities, run by AppleCare. The folks over there are more likely to have experience in VPN setup issues.OTOH, if you have a working configuration profile but you can't figure out how to replicate that in NEVPNManager, you should post your follow-up questions here.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

OK, that's much clearer, thanks.It seems that this restriction is a deliberate change (r. 18744994) made to enhance security. Right now the restriction applies to:LD_LIBRARY_PATHanything starting with DYLD_Disabling system integrity protection will also disable this check.What are you using this feature for? I'm curious about the context of your question because, well, it seems to me that this restriction might be overly broad.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Platform : MAC OSX 10.10.3Cool.We want to develop an application which should have Single Sign On support.What does your app want to do with SSO? Are you trying to issue HTTP requests to a server? Or Kerberise your own networking protocol? Or what?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

First up, I moved your question over to Media > AVFoundation (Video and Camera) because you're more likely to connect up with folks who have experience with this sort of thing over there.Second, I can't discuss other third-party developer's products specifically, but I will say that this is one of the advertised features of FairPlay Streaming. See WWDC 2015 Session 502 Content Protection for HTTP Live Streaming for details.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

However, I thought Apple had fixed this issue in iOS 7? I remember talking to Quinn at WWDC who advised me that we should be able to use the keychain after 200ms after launch of the app?I think you must be mixing me up with someone else. AFAICR I've never advised folks to delay accessing the keychain by 200 ms, for this or any other issue.Also, are you sure you're not confusing this error with the -34018 (errSecMissingEntitlement) issue? Folks have been suggesting that delaying their keychain access might work around -34018 issue, although personally I don't think that actually helps. This -34018 issue is covered in this DevForums thread.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I don't think there's a straightforward solution to this problem. The issue is that:Mac App Store requires that every piece of code within your app be code signed and sandboxed, including your helper tool.The App Sandbox is, as the name suggests, an app sandbox. So there's no affordance for sandboxing a tool independently of its parent app. Specifically, while you can sandbox a tool, there's no magic that gives the tool access to the paths that are passed to it via command line arguments.Sandbox inheritance (com.apple.security.inherit), which is the way I generally recommend that folks sandbox their tools, does not work for this because Terminal is not sandboxed so, when you run the tool from the command line, there's nothing to inherit from.You may be able to resolve the problem by converting your tool to some sort of script (a shell script, Python, whatever). That's almost certainly feasible from a technical perspective, I just don't know how it interacts with the Mac App Store rules. If no one else chimes

is there any code to write to send a push notification when an action is performed by a user?junkpile has effectively answered this already: the code you write depends on the back-end system that you choose to use.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I don't have any suggestions for how to solve your specific problem but I will recommend that you watch the following WWDC 2015 sessions, which are packed full of interesting info in this space:Session 509 Seamless Linking to Your AppSession 709 Introducing Search APIsShare and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

At first blush this looks like a straightforward server trust evaluation problem. Technote 2232 HTTPS Server Trust Evaluation covers this issue in detail.However, when I tried to test the specific server you mentioned, HTTPS worked fine. Specifically, this playground:import Cocoa let d = NSData(contentsOfURL: NSURL(string: https://api.themoviedb.org)!) println(d?.length)printed this result:Optional(22936)It could be that the server is doing different things for well-formed API queries, but it's hard for me to explore with the time I have available for helping out on DevForums.P.S. It would have been nice if this forum allows the uploading of screenshots.Quite. Rest assured that you're not the first person to ask for this (r. 22028729).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

This is definitely a problem with how your delegate method signature is set up. It's hard to say what the exact problem is because it's different in Xcode 6 and Xcode 7. I can, however, tell you a general recipe for avoiding problems like this:configure the class to conform to the right delegate protocolinside the class, type URLSession and hit Escape get code completionselect the right method from the listIf you do this then Xcode will always insert the delegate method with the correct signature.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I even tried converting everything to NSURLSessionStreamTask [...] may suffice for us short term for basic networking, but that class doesn't seem to be in a functional state yet either even on straight iOS 9.On the iOS side of things, it seems that you're seeing a bug in NSURLSession's stream task support. I tried this out for myself (or 9.0b5) and got similar results. I've filed this as 22213450.On the watchOS side of things, I think the problem you're having is that the watch does not have an active network interface, at least not most of the time. Most of the time the paired iPhone is available and the watch pushes networking requests off to that. If the paired iPhone is not available then the watch can join Wi-Fi networks, but that only happens under specific circumstances and opening a TCP connection is not one of them.I'm not sure that NSURLSession stream task will help with this, even once it starts working in general.For the moment I think your best option is either talk to your target device via HTT

Hey eskimo: Amazing idea to use autocomplete. ;-) Thanks a lot. Now it works. Correct method signature when working with NSURLSessionTaskDelegate is:func URLSession(session: NSURLSession, task: NSURLSessionTask, didReceiveChallenge challenge: NSURLAuthenticationChallenge, completionHandler: (NSURLSessionAuthChallengeDisposition, NSURLCredential!) -> Void) { println(didReceiveAuthenticationChallenge) }

whatever happened to getting Apple to release API(s) to allow access to the ARP table?There's nothing concrete announced about that.In fact, this issue is getting trickier due to MAC address privacy issues. Starting with iOS 7, iOS apps no longer have access to the device's MAC address because that address represents a persistent identifier for the device. See WWDC 2013 Session 714 Protecting your Users' Privacy for details.The ARP table represents a similar concern; while the local device's MAC address isn't in the ARP table, the presence of MAC addresses is still troubling (r. 22246722).Regardless, at this point if you have specific requirements in this space, I encourage you to file an enhancement request describing those requirements. Please 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