eskimo

Well, there's good news and bad news here. Let's deal with the bad news first: on currently shipping OSes there's really no good way to create a hotspot helper app. There are some facilities but they are either fundamentally broken or not broadly available.The good news is that we plan to fix this in iOS 9. WWDC 2015 Session 717 What's New in Network Extension and VPN for details.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I believe these errors are AVErrorUnknown and AVErrorMediaServicesWereReset, respectively. I don't know much about AV Foundation so I moved your thread to Media > AV Foundation (Video and Camera) where you're more like to connect with folks who know stuff about this stuff (-: Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

eskimo - Thank you for your share. Actually, I had tried to follow MVC model. I just wonder that the NSURLSession in tab1 and tab2 controller are using same session to connection server or not. Thank you.// tab 1class tab1controller: UIViewController{ override func viewDidAppear(animated: Bool) { var page1: readPost() = readPost(L) }}// tab 2class tab2controller: UIViewController{ override func viewDidAppear(animated: Bool) { var page2: readPost() = readPost(F) }}class webConnect(){// use NSURLSession}class readPost(){ init(postType: String) { // postType - L = Lastest; F = favorite } func readPost() { var webConn : webConnect() }}

NSString's substringWithRange: should work fine.That depends on what you mean by fine. Yes, it'll work fine if the string only contains characters encodable as ASCII. For anything more complex than that, even for something as simple as Latin-1, -substringWithRange: makes it easy to fall into some common pitfalls. The most common of these are: you might erroneously split a surrogate pairyou might accidentally split a character from its combining accentsyou might erroneously assume that, for two strings to be equal, they must have the same lengthThe Swift string API is designed to deal with the complexities of non-ASCII string processing. The cost of that design is that you lose the ability to treat strings like ASCII if you know they really are ASCII (for example, if you're dealing with strings in a network protocol).Which brings us back to the original question. The example only makes sense if you can guarantee that s is an ASCII string. So, @Shuhao, are you asking about how to deal nicely with ASCII strings?

eskimo - After I keep working on my project, I need to re-parse my question. I found that NSURLSession.sharedsession() is shared to connect server. When I use it in Tab 1 and Tab 2, the taskIdentifier of each task is 1 and 2 respectively.However, I want to config sharedsession as code below (setting). So that I can fire the during downloading and download is completed by setting up delegate: self. Thank you.setting var configuration = NSURLSessionConfiguration.defaultSessionConfiguration() var mainSession = NSURLSession(configuration: configuration, delegate: self, delegateQueue:NSOperationQueue.mainQueue()) func URLSession(session: NSURLSession, downloadTask: NSURLSessionDownloadTask, didWriteData bytesWritten: Int64, totalBytesWritten: Int64, totalBytesExpectedToWrite: Int64) func URLSession(session: NSURLSession, downloadTask: NSURLSessionDownloadTask, didFinishDownloadingToURL location: NSURL)

Well, there's nothing of interest in the system log, so I tried running your code. I got the same error but, after poking around a bit, I managed to get things working. Here's what I ended up with.import Foundation import CoreWLAN var error: NSError? let iface = CWWiFiClient.sharedWiFiClient().interface() println(iface.interfaceName) let success = iface.startIBSSModeWithSSID( Test.dataUsingEncoding(NSUTF8StringEncoding), security: CWIBSSModeSecurity.WEP104, channel: 11, password: HelloCruelWorld, error: &error ) if !success { println(error?.localizedDescription) } else { NSRunLoop.currentRunLoop().run() }With reference to your line numbers:You have a lot of unnecessary semicolons (-:Line 3 is a bit weird and definitely unnecessary.Line 5 is unneeded because you never reference ssid.Likewise for security on line 6.Likewise for channel on line 7.Line 8 is definitely a problem; you can't create a .WEP104 network without supplying a password.In lines 11 and 14, you should use let not var because you don't cha

I was inquiring when we will get some detailed documents to iterate over the new Packet Tunnel Provider?We do hope to get proper documentation but I don't have any information to share about schedules.Also do you know what sandbox exceptions we might expect?The extensions are quite heavily sandboxed. Do you have any specific concerns here?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

In situations like this I generally recommend that you have a model-level controller that owns the NSURLSession and hence receives all of its delegate callbacks. You can either implement that as a singleton or inject a reference to it into each of your view controllers.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

My question is fairly straight forward - can iOS create a Wi-Fi Direct group that can be joined by non-iOS devices?No. The peer-to-peer Wi-Fi implemented by iOS (and recent versions of OS X) is not compatible with Wi-Fi Direct.Note Just as an aside, you can access peer-to-peer Wi-Fi without using Multipeer Connectivity. The underlying technology is Bonjour + TCP/IP, and you can access that directly from your app. The WiTap sample code shows how.Based on this I would say no, but technically speaking, there should be no limitation for Wi-Fi Direct as [...] apps like AirDrop already use it.AirDrop does not use Wi-Fi Direct, but rather the Bonjour + TCP based peer-to-peer Wi-Fi discussed above.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What junkpile said plus…If you use NSURLSession for your networking, you can avoid the need for accumulating data manually by using one of its convenience APIs. This simplifies your code and gets you off the now-deprecated NSURLConnection API.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Then isn't there any way to develope sources to connect iPhone to other devices through as well?I'm sorry, I don't understand your question.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Swapping out the view like that is usually a last resort though. Can you set it in your storyboard?Alas, WKWebView can't be put in a nib (and hence can't be put in a storyboard). This is a known bug that's bitten me more than once )-:Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

First of all, thanks for all your feedback about this issue (both formal, via Radar, and informal, via DevForums, email, and so on).Second, be aware that this is not a accidental change (r. 15225882): rather, Apple has serious concerns about the privacy implications of CNCopySupportedInterfaces and now that its expected use case, dealing with captive networks, has been formally replaced via NEHotspotHelper, it seemed like a good time to make this change. However, it's now clear that lots of developers are using CNCopySupportedInterfaces for things other than dealing with captive networks. That feedback is being considered by the relevant parties here at Apple and there may be future changes based on it. I can't offer any further insight into that process. Regardless of how this issue is resolved, I've made it clear that this issue needs to be covered in the release notes (r. 22068424).Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEm

I'm not sure about accessing the accelerometer is the background per se, but there are at least two problems with your overall strategy:You wrote: then bring app to frontthen bring app to front and complete some processes such as email and communicate with server.It is not possible for an app to bring itself to the front.It sounds like you need the ability to process the accelerometer data in real time, which means you need to avoid your app being suspended in the background. It's not possible to do that in the general case. If you have some other reason to remain running in the background, you could look at how the accelerometer APIs behave in that case, but if you don't have such a reason then the question about how the accelerometer APIs behave is irrelevant.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

You haven't asked a question here, making me suspect that you'd be better off filing a bug report rather than posting here on DevForums.If you do file a bug, 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