eskimo

While the constants you’ve referenced are all C macros, and thus the values are right there in the C header, there are a lot of constants exported by the system where that’s not the case. For example, UIApplicationDidEnterBackgroundNotification. The Swift import style makes perfect sense for those constants. ps I’m not on the Swift team, so can’t give you an authoritative answer to ‘why’ questions.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Do we need to ensure the above suggested certificate compliance on all of the certificates involved from the Leaf, all the intermediary, and the Root CA certificates?No. These requirements apply just to the leaf certificate.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

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 (r. 22227634) to get the docs updated.It turns out that the fact that NSExceptionRequiresForwardSecrecy relaxes the SHA-2/256 requirement is a bug; the intended behaviour of NSExceptionRequiresForwardSecrecy is the behaviour documented in the App Transport Security Technote, namely that it should just enable specific cypher suites. Our plan is to fix this bug at some point in the future. We expect to fix this in some compatible fashion, so folks who’ve mistakenly used NSExceptionRequiresForwardSecrecy to disable the SHA-2/256 requirement won’t break. However, predicting the future is always a challenge. Which brings us to what you should do right now. [A previous version of this post gave less concrete advice. The following is an update that tightens things up.] Aft

The only folks who can give you a definitive answer about this is App Review; you can contact them directly but, in my experience, they prefer to deal with concrete problems (Is this specific app allowed?) rather than offer general opinions.My general advice about background modes is to evaluate your use based on the spirit of the guidelines. The audio background mode is their so that users can enjoy audio playback while they do other things on the device (or the device is screen locked). The user understands that doing this sort of work in the background can reduce their battery life, and are reminded that it’s happening by the ongoing sound coming out of the devices speakers.Does your proposed usage match that?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What happen if my app state moves from foreground to background before the request ends?Unless you have other work that prevents your app from being suspended (for example, audio playback), it will be suspended shortly after moving to the background.Does the request will continue running for a limited time in background?No.You can, however, arrange to do this by using a UIApplication background task. This is exactly what UIApplication background tasks were designed for.Presumably your upload is small (after all, it fits in memory), so there’s a reasonable chance of it finishing in the few minutes that the UIApplication background task gives you. If it’s large enough that that’s not the case, you should use an NSURLSession background session. However, NSURLSession background sessions bring in all sorts of complexities, so if you can get away with using a foreground session in concert with a UIApplication background task, you should do so.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, D

I suspect you have a race condition here, that is, your reader thread is reading the data before your writer thread has finished. The NSData calls you reference do not buffer the data in user space, and the kernel’s file system cache is coherent.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

After resolving I'm trying to setup input and output streams…Resolving the NSNetService? You don’t need to do that; you can call -getInputStream:outputStream: and it will resolve as part of the opening the streams. Beyond that, I can’t see anything specifically wrong with your code. Try removing the resolve to see if that improves things. I’ve seen cases where your operations on the NSNetService can confuse the streams’s operations on the NSNetService and cause weird problems like this (the streams should make a copy of the NSNetService and use that internally but that’s not how things currently work (r. 9821932)).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

A large chunk of the CoreWLAN API was replaced with new API in 10.7. At that time the old API was deprecated. I’m not super-familiar with CW8021XProfile but I suspect the replacement you’re looking for is CWNetworkProfile.ps I also moved this thread over to Core OS > Networking.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 this thread to Core OS > Security.Second, this is a complex problem and I very much doubt you’ll find an answer here on DevForums. I recommend that you open a DTS tech support incident so I, or one of my colleagues, can investigate the issue in detail.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Thanks Eskimo. That at least confirms I'm not missing an api. The reason is there is a mix of requests going from UIWebview with default CFNetwork derived headerand custom requests with an explicitly set header. Ideally the values would be the same.

Your method is already passing a completion block as a parameter so it seems you are handling the response asynchronously...Yeah, that’s the bit I don’t understand.Can you post your old NSURLConnection code so we can see what it did?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Where are you getting this predicate format string from?NSPredicate kinda assumes that you’re using format strings that are hard-wired into your app, and thus throwing an NSException when it gets a bad one is reasonable behaviour (in the same way that NSDictionary throws an NSException when you try to insert nil, it’s considered to be a programming error).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

So how do I push the Dev Team at Apple to understand appropriate API access; So we can read the current connectivity of the device and not damage anything in said device.The standard answer here is to file an enhancement request.Beyond that, this is a business question, not a technical question, and I’m not in a position to offer advice on business issues.If you do file an enhancement request, please post your bug number, just for the record.Finally, off list someone asked How can I tell whether an API is public or private? A good first step is to check whether the API is in the iOS SDK. If it’s not, it’s definitely private.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Right now the only option is Xcode. I used to point folks at iPhone Configuration Utility but, alas, that’s not longer supported. [I’m hoping that the new Apple Configurator 2 will support this but, alas, I haven’t had a chance to try it out yet.]Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Can you get detail of WiFi network on iOS ?No. There’s now supported way to get low-level Wi-Fi information, like the nearby channels and their signal strength, on iOS.ps I moved your thread to Core OS > Networking, where this is a bit of a FAQ (-:Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com