eskimo

But what is bothering me is iOS 8 behaviour.I'm still confused by your actual issue. I suspect you're talking about this case:you build an app using NSURLSessionyou deploy a server that supports HTTP/2on iOS 9, this will talk to your server via HTTP/2on iOS 8, this will talk to your server via HTTP/1.1 or SPDYon iOS 7, this will talk to your server via HTTP/1.1Whether this works really depends on your server. Ignoring iOS 8 and SPDY for the moment, consider the iOS 7 case. Here iOS is simply going to open the connection and send an HTTP command. What does your server do in that case? It should handle it correctly, but iOS can't guarantee that.OTOH, if I read your original question literally, you seem to be asking about this case:you build an app using NSURLSessionyou deploy a server that supports HTTP/2on iOS 9, this will talk to your server via HTTP/2on iOS 8, will it send HTTP/2 requests?The answer here is no: the HTTP/2 support is part of iOS 9, and thus won't be available on earlier OS releases.OTOH, iOS

iOS does not have a shell.For those following along at home, this question is fallout from an earlier thread.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Hello eskimo,I have the same problem. The iOS framework has memory leaks when we open a video stream through http.I already try many workaround to try to avoid this memory leak without success. Please see my code:[[NSURLCache sharedURLCache] setMemoryCapacity:0]; [[NSURLCache sharedURLCache] setDiskCapacity:0]; _connection = [[NSURLConnection alloc] initWithRequest:[NSURLRequest requestWithURL:_url cachePolicy:NSURLRequestReloadIgnoringLocalCacheData timeoutInterval:20.0] delegate:self];We can just leave the didReceiveData without code,- (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data { }and still verify the memory leak in XCode, because the allocated memory don't stop to increase, and in Instruments, because Leaks reports many Leaked Objects at libsystem_c.dylib reallocf Also, it seams that the number of leaked bytes per second increase with time. For the first frames, the instruments detect 200 KB of leaks per second (remember we are receiving MJPEG video)...and after 3

Calling -close on both the input and output streams should be sufficient to close the streams. I just tested this with a small test app here in my office and it works as expected. Some things to watch out for in your code: make sure that -disconnect is actually called — It's easy to confirm this in the debugger.make sure that -disconnect is called on the correct thread — In general it's best to confine your access to a input/output stream pair to one thread. I suspect that you call both -connect and -disconnect from the main thread, so that's not a problem here.make sure that inputStream is not nil at the time you call -close — Because you're using the ? operator, if inputStream was nil your entire -disconnect method would be a no-op.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Does this problem occur with NSURLSession? If so, you should file a bug about it. Ideally your bug report should include:a small test project that demonstrates the issuethe URL of a camera available on the public InternetApropos the second point, if you have a publicly accessible camera that reproduces the problem please post its URL (or email it to me if you don't want to share it with everyone; my address is in my signature). I'd like to take a quick look at this, just to verify my own expectations.Finally, 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

My assumption here is that when the user opens my app and it runs for some time in the foreground, then the rate limiter is reset or similar -- so now things will flow nicely again. Is this assumption correct?Yes.Also, starting with iOS 8, if the user brings your app to the front then iOS will automatically give tasks a 'kick'. I've forgotten the exact mechanics of this but I'm pretty sure it's covered in WWDC 2014 Session 707 What's New in Foundation Networking.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Have you tried creating more than one background session, each with only a few hundred items in it?Please don't do this. Having multiple sessions make sense if the items are logically distinct, but having multiple sessions just to bypass some restriction in the OS is just starting an arms race that you're not going to win.And remember that all sessions on the system are handled by a single instance of nsurlsessiond, so splitting the work between multiple sessions won't help in that regard. You can always handle the background completion event by scheduling another batch of downloads …Indeed, but there are limits to how far you can take this because nsurlsessiond limits how frequently it will resume your app. I posted a link to my old DevForums post about this earlier, but you seem to have missed the reference. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Now I've migrated it to Xcode7/Swift2 and when deployed either to iOS8 or iOS9 I keep hitting the -34018 Keychain error.You hit it every time, or occasionally? If it's every time then there's almost certainly something wrong with your code signing. If it works the vast bulk of the time but fails under specific circumstances, that's the bug that discussing on this thread.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What context are you trying to do this from? /.vol is weird but /.Trashes is simply a directory with restricted permissions. If you elevate your privileges you can access it the same way as you access any other volume. $ ls -lha /.Trashes ls: .Trashes: Permission denied $ sudo ls -lha /.Trashes total 0 d-wx-wx-wt@ 2 root wheel 68B 1 Dec 2014 . drwxr-xr-x 36 root wheel 1.3K 5 Jun 23:09 ..However, in 99% of cases you should avoid monkeying with these special directories because their presence and semantics are not considered API. So, what are you really trying to do here?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

This is working for me in Xcode 6.4. Perhaps it's a platform-specific issue. I was testing an iOS app in the iPhone 6 simulator. What are you testing?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

hi anybody can help me for find the source row?You need to symbolicate your crash log. For background on this, see TN2151 Understanding and Analyzing iOS Application Crash Reports. IMPORTANT The advice in the current version of that technote (dated 2012-12-13) for how to symbolicate a log is incorrect (we're in the process of updating the technote right now). I recently posted up-to-date instructions in a different thread.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Please see my response to your other post.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I am new to the xcode and also in MAC envronment. I want to know what are the API or methods used for Digital Signing in objective-c using xcode 3.2.5.Xcode 3.2.5? Really?That version of Xcode is very old. What version of OS X are you running it on?With regards signing, there's a specific issue at play. IIRC Xcode 3.2 is for Mac OS X 10.6, and the API you want to use (SecSignTransformCreate) was introduced in OS X 10.7. If you really are stuck on 10.6 then you'll have to use the much older CDSA APIs. These are long-since deprecated, so there's not a lot of information about how to use them. Specifically, I can't help you with them because I never got around to learning them myself. Moreover, I can't recommend that you write new code that targets these APIs because, well, they're deprecated. If there's any chance you can upgrade to OS X 10.7 and Xcode 4.x, the situation will be a lot clearer. Here you'll be able to use SecSignTransformCreate, which yields two benefits: you can crib code from the CryptoCompatib

Perhaps it should just be an APIWell, it is already an API (SCNetworkReachability) but I suspect you meant Perhaps there should be a better API (-:If you'd like to get this suggestion in front of folks who have the power to act on it, please file an enhancement request. If you do that, post your bug number, just for the record.When writing your bug report, please be specific about what you're using reachability for. In my experience this API is often used for all the wrong reasons, so if we introduce a better reachability API I'd like it to encourage folks to use reachability in the right way.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I've moved your thread over to Xcode > Getting Started because that's a better match for questions like this.What platform (or platforms) are you developing for?I am trying to create an app where you can submit something and it appears on a list that every one using the app can see.I'm not entirely sure I understand your question. I suspect you're goal is to ship an app that anyone can download. These users can then add information to some sort of network-based database, and that information is seen by all the other users. Is that right?If so, there are lots of options available to you and it really depends on how you want to manage the server side of this. However, before I send you down that path I want to raise one key question: how are you going to manage security? Once you have a world writable database, you have to worry about things like spam, phishing, abuse, and so on. How do you plan to handle that?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support