eskimo

Our app uses WiFi to communicate with VoIP server (in both fore- and background), periodically connecting to a dedicated server asking for data updates.I have two big picture questions here:I presume you're using the original VoIP architecture, as opposed to the PushKit architecture we introduced in iOS 8?When you say uses WiFi to communicate with VoIP server, does that mean the VoIP server is only available on Wi-Fi? That is, is the VoIP server available on WWAN at all?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What are the criteria for iOS to consider WiFi connection functional?That is complex and undocumented, and it evolves over time.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What are you using reachability for? I'm finding it hard to imagine a situation where you'd want to run a reachability probe on a IPv6 address specifically (as opposed to a DNS address, which the Reachability sample code already shows how to do).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

TLS cypher suite negotiation works (roughly) as follows:The client sends a list of cypher suites that it supports to the server (via the Client Hello message).From that list, the server tells the client which cypher suite that it likes the most (via the Server Hello message).Given that design, your question doesn't make logical sense: iOS 9 will not include the insecure cypher suites in its Client Hello and so server's support for other cypher suites is irrelevant.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The following assumes you're building with a modern SDK and you don't have UIApplicationExitsOnSuspend set in you information property list. There's one easy way to trigger -applicationWillTerminate:, to wit, with your app in the foreground, bring up the multitasking UI and swipe up on your app. Beyond that it's really up to the OS. Are the devices exhibiting this behaviour primarily older devices? I suspect that memory pressure is the most likely cause of the symptoms you describe.Can you reproduce this in house? If so, do you see anything interesting in the system log?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

It would be nice to see asymmetric crypto included in the common crypto library for applications that just want the algorithms not keychain integration.The best way to get that feedback in front of folks who have the power to effect change is to file an enhancement request for it. Please post your bug number, just for the record.Also, I had wanted to generate keys with exponent=3, to push more of the work load from encrypt to decrypt side, but it looks like SecKeyGeneratePair() always uses 65537.Ditto.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I'm not sure what else is going on with your project, but this line is wrong:messageVC.recipients = [077669789805]The recipients property is meant to be an array of strings, so you'd have to write this: messageVC.recipients = [ 077669789805 ]If you need further help with this, please let us know what version of Xcode you're using. There are big differences between Xcode 6.4 and Xcode 7 beta, and it's hard to give specific answers without knowing which one you're targeting.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

You don't understand. No one here wants to turn their app into a Hotspot helper just so they qualify to use the NEHotspotHelper APIs. We just want to be able to read the current WiFi SSID and use that information within our current app.A phone call is not going to help. It is very unlikely the person handling the phone would even understand the question.Since eskimo understands our needs and has passed them along to the programming staff at Apple handling iOS that is the best way to get this resolved. We need an approved (and supported in all future iOS versions) way to read the current WiFi SSID.

Yes, VoIP server is only available over WiFi being a part of LAN within a Company infrastructure, it's not exposed externally, so not accessible via WWANAlas, that is not a model that's well supported by iOS's VoIP architecture (either old or new). The VoIP architecture assumes that, if a device has a working WWAN, the VoIP app will be able to contact the VoIP server via WWAN.IMPORTANT: There are good reasons for this. Specifically, this assumption allows iOS on WWAN-capable devices to disassociate from the Wi-Fi while sleeping, which saves significant amounts of power.Having said that, the new VoIP architecture might help here. The normal flow for the new architecture is:server sends app a push notificationapp wakes up in the backgroundapp contacts server to decide what to doif necessary, app alerts the user about a phone calluser brings app to front and answers callIf you remove step 3 then this approach will work for a server that's only available on Wi-Fi (because step 5 requires an unlock and that will r

The issue is resolved in iOS 9 Beta 5.Cool. Thanks for following up about this.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Still not working in 7b5.Are you still seeing that NSExceptionRequiresForwardSecrecy works around the problem? I was playing around with this myself and that didn't work, so I'm curious about your experience. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

The sample code fr CoreTelephony has been removed from the Apple dev sample code???I'm not sure what sample you were looking for but CoreTelephonyDemo is still available on the developer web site.The data I need is in the built-in testmode app in iOS. If you dial *3001#12345#* in your phone dialer you will see it.How do I get to this data in iOS?There's no public API to get this information.I think the new CoreTelephony Framework might help alot.Alas, that's not the case. The public CT API is only useful for monitoring call state while your app is in the foreground. It exists so that a VoIP app can put its VoIP call on hold when a cellular call comes in. It doesn't support any cellular diagnostic capabilities.I am a cellular network engineer by day and curently all the tools are on Android platforms and I would like to move this to iOS.This is simply not possible within the boundaries of the iOS SDK. If you're working on behalf of a specific carrier, you should talk to that carrier about this issue.Share and

c. I simply ignore this and go straight to the stage where the peers exchange public keys in order to proceed with encrypted communicaiton.You don't need to do that yourself; you can pass NULL as your identity and MCEncryptionRequired as your encryption preference and you'll get encryption without identity checking (for whatever that's worth). Getting back to your overall question, there's a fundamental issue here: in a decentralised peer-to-peer network, how do you determine identity? This isn't a problem specific to networking; you get exactly the same issue in the real world (if someone comes up to you and says Hi, I'm Boris., how do you know that they are really Boris).I've thought about this issue a lot and I can see two basic strategies:centralised server -- You don't have to use this for communication; it's solely for setting up the identity on the device. I posted about this on the old DevForums.ask on meet, then remember -- This is the approach used by SSH: the first time you interact with a peer, yo

The main application is scriptable.Temporarily ignoring your command line tool for the moment, what happens when you open the document via AppleScript? Does that work?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Mr. Eskimo,I can confirm that your Jul 23, 2015 1:37 AM solution works!I really appreciate your help.Thanks.