eskimo

I would strongly recommend that you not go down this path. Honestly, I don’t know if this technique still works but I can say two things:The technique is not supported because the format of the resulting data is not documented (it is document on OS X, but it’s not safe to assume that iOS and OS X are aligned here).iOS is getting increasingly restrictive when it comes to identifiers that can be used to track the user. I would not be surprised if this technique runs into sandbox restrictions in the future (r. 22246722).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Is there any difference in behavior between an app submitting batches of 300 sessions, each containing 1 task, and the same app submitting batches of 1 session, each containing 300 tasks?The resume rate limiter applies to your app as a whole, not to any specific session within your app.My app's currently using the 300 sessions of 1 task each approach.Yowsers! That’s a really bad idea, regardless of its effect on the resume rate limiter. I talked a little about this in another recent thread but the situation is worse with background sessions because they have a footprint in both the app and nsurlsessiond. It's an embarasingly large chage to refactor my code to support 1 session of 300 tasks.Oh, and you thought I’d let you get away with that one, eh? (-:In my experience the majority of folks who are using a session per request do so because of NSURLSession’s single delegate (as opposed to the NSURLConnection model, where there is one delegate per request). However, it’s relatively easy to demultiplex the NSURLS

Mac OS 10.9 and up.OK. That’s important because, while there’s some overlap in the Security framework between iOS and OS X, they are largely different beasts.You can import a DER-encoded public key using SecItemImport. For details, see this post on the old DevForums. Note The code in that post imports the key into a keychain. At the time I thought that was a requirement for SecItemImport. My understanding now is that this is not a requirement, and you can get a SecKey object without actually putting the key into the keychain. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Why the public key can generate in iOS 8 SDK?It’s not uncommon for different releases of the OS to have varying behaviour when it comes to parsing malformed data.Given that iOS does not have an API for converting an exponent and modulus into a key, you have three choices here:Continue using your own code for this, fixing it to generate the ASN.1 data structure correctly (A).Adopt some third-party ASN.1 library (B).Change the code that sent you the exponent and modulus to instead send you a certificate (iOS has nice APIs for dealing with certificates) (C).In general I recommend C. Given that the server is likely to have a full-feature security toolbox, it should be easy to do this on the server side.If you stick with approach A and get completely stuck, please open a DTS tech support incident and we can take a look at your code in more detail.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Folks, please read my posts on this thread and use the advice therein to check that your public key is well formed.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

See this post for my thoughts on this.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Your best option is to view the device’s system log (via Xcode’s Devices window) which will show the log entries from both you app and your extension regardless of whether Xcode is attached or not.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Getting lots of crashes due to Fatal signal EXC_BREAKPOINT / EXC_ARM_BREAKPOINT at _dispatch_queue_wakeup_with_qos_slow. I’ve no idea what’s going here but I’d love to see a full crash log. Can you post one?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

During DarkWake via daemon process make the OS wait until its done.Have you looked at the IOPMAssertion API?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

[Administrivia: I had to edit your post to remove the URL so that I could reply promptly.]What’s your high-level goal here? You started this thread with a very theoretical treatment of the issue but this most recent post seems to be very specific (worrying about App Review rejects of your app and so on). If you can post a summary of what your app does, should be able to provide more concrete advice.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Given that you started with WiTap, and WiTap sets includesPeerToPeer, please test with an unmodified version of WiTap in your environment to see whether it works or not. That’ll tell us whether the problem is with your code (WiTap works but your code doesn’t) or in your environment (WiTap doesn’t work). Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Just wanted to verify what I want to do is not currently supported before filing a radar.You should definitely file an enhancement request describing your use case. Please post your bug number, just for the record.As part of the login process, the server will send back the domain of another server to use for further https communication. The possible domains returned to us are not (and cannot be) known to the client app at build-time.And yet you’re sure that this other server complies with ATS’s other requirements. Interesting.Given the current state of ATS, it seems like solving this on the server side might make more sense. For example, if you put all of these redirected-to servers ‘inside’ your domain, this problem would go away. The DNS side of doing that is easy, although the digital identity provisioning is likely to be less so.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

NSAllowsArbitraryLoads is not disabling the App Transport Security for the Watch …I think you need to start a new thread for this new topic. It took me a while to find your post in this long and complex thread, even though I knew it was there.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

We have this requirement to show mac addresses connected so wanted to know if we have any other way of doing this.As per the second point in my previous post, the main concern here isn’t a technical one, so alternative technical approaches are unlikely to help.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The problem here is that NSUserDefaults is ultimately backed by a file in your app’s container and your app’s container is subject to data protection. If you do nothing special then, on iOS 7 and later, your container uses NSFileProtectionCompleteUntilFirstUserAuthentication, a value that’s inherited by the NSUserDefaults backing store, and so you can’t access it prior to first unlock. IMO the best way around this is to avoid NSUserDefaults for stuff that you rely on in code paths that can execute in the background. Instead store those settings in your own preferences file, one whose data protection you can explicitly manage (in this case that means ‘set to NSFileProtectionNone’). There are two problems with NSUserDefaults in a data protection context:Its a fully abstract API: the presence and location of its backing store is not considered part of that API, so you can’t explicitly manage its data protection.Note On recent versions of OS X NSUserDefaults is managed by a daemon and folks who try to manipulate