eskimo

… to check at runtime if app is running on simulator or device?This part of your question makes no sense. An app can't be built so that the same binary runs on the simulator and runs on the device, so it makes no sense to do a runtime check to see whether you're on the simulator or the device. Such a check would always be at compile time.However, to answer your question about the difference between TARGET_OS_SIMULATOR and TARGET_IPHONE_SIMULATOR, the former is the replacement for the latter, which is now deprecated. If you open <TargetConditionals.h> in the iOS 9.0 beta SDK, you'll see this comment: TARGET_IPHONE_SIMULATOR - DEPRECATED: Same as TARGET_OS_SIMULATORShare and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

It is possible to create an event with null title using Outlook calendar (simply create an event, do not change anything and save).Quite. If that's the case then either the EKCalendarEvent implementation needs to be fixed (so it doesn't return nil in this case) or its header needs to change (so it doesn't claim to not return nil).Please file a bug about this, then post your bug number here, just for the record.I am new to the forums, please feel free to correct me if there are any issues with my question.You're doing well so far (-:Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

How is your view controller getting into the responder chain? I tried two ways of doing this, one of which replicated your results:If I create a custom view, having accept first responder, and then make it the first responder, my view controller gets both key up and key down events.If I add a text field to my view and click in that, the view controller gets key down events but not key up events.At this point it's clear that this is definitely not related to Swift but rather something very specific to AppKit. I don't know AppKit (or any UI framework, for that matter) well enough to help you with anything beyond the basics. I've moved this thread to App Frameworks > Cocoa; hopefully someone more knowledgeable about this stuff will chime in over tehre.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I want to provide UI (like picture as follow link …) to let user to select the display language.The system does not support changing your app's localisation on the fly. If you look through the App Frameworks / Localization topic area (which is where I moved your question, btw) you'll find that a significant fraction of the threads are from people having problems when they try to do this. You may be able to work around some of the problems but there are others that have no workaround. Probably the most significant relates to system UI components.If the system puts up a UI component on your behalf (the document picker, or Game Center user interface parts, or whatever) it will do so in the localisation that it thinks that your app is running in. If your app is 'pretending' to run in some other language, you'll end up with a mixed localisation, where some parts of your app (the parts you control) are in one language and other parts of your app (the parts controlled by the OS) are in another. That's a very poor us

In my testing, it seems that if my server responds a 302 (temporary redirect), then NSURLSession cancelByProducingResumeData does not produce resume data.Does this happen in a background session, a standard session, or both?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

What about using [NSFileManager isReadableFileAtPath:]?It is essentially a wrapper around access. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Does this mean IP_BOUND_IF for socket? Yes. There are other options (like calling bind with the interfaces source address) but IP_BOUND_IF is the easiest. Is this legal API on iOS?Yes.There are two gotchas here:You have to work out the interface name you want to bind to (IP_BOUND_IF take an interface number, but you can get that from the name using if_nametoindex). These interface names are not considered API. You can call various APIs to try to infer the right interface name, but there's no direct API that answers the questions What's the Wi-Fi interface name? or What's the WWAN interface name?If the service you ultimately want to talk to is based on HTTP, it's definitely not fun implementing your own HTTP engine. Likewise for other high-level protocols.Finally, you're not the first developer to have problems with this sort of setup and it's clear that iOS could provide better support for it. If you'd like to see such support added in the future, I encourage you to file an enhancement request describing your

I meant the top level issue of local requests being blocked by default w/ ATS.Hence my request for clarification. I'd argue that the top level issue here, the one raised by the hhtouch when they opened the thread, relates to accessing nearby networks not to accessing localhost.Regardless, on the localhost front, it seems that bwalker filed a perfectly reasonable enhancement request for that (21519087) and there's a perfectly reasonable workaround (adding a ATS exception), so it's really just a question of waiting to see what iOS Engineering makes of the issue.I was just asking in case you'd be able to share any known changes coming in the next beta/release.You'll find that Apple folks really don't like discussing the future, even the relatively near future like the iOS 9 beta release cycle.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Is there any possibility that allows Mac App can listen on a privileged port (aka. < 1024) while the app was sandboxed?No.This low-numbered port restriction is really dumb IMO. We lifted the restriction on iOS many years ago, but there's no sign of us lifting that same restriction on OS X. Most annoying.Please file a bug report about this, then post your bug number here, just for the record.For the moment the only way around this is to distribute outside of the Mac App Store.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I don't have an answer for you here, alas. I'm not sure whether the built-in Apache is dynamically linked to the system OpenSSL or has its own statically linked OpenSSL (which is what we generally recommend). If it's the latter, it's obvious that upgrading OpenSSL on the system as a whole will have no effect.I can see three options for you here:continue to investigate the built-in Apache — If you want to do this I recommend you post your question to Apple Support Communities, run by AppleCare, where it'll reach a bigger audience whose more familiar with user-level issues.try OS X Server — Apache isn't really part of the OS X client product, in that it's not used by any user-facing feature. OTOH, Apache is part of OS X Server, and thus I'd be very disappointed if it didn't support TLS 1.2 out of the box.built your own ApacheShare and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

AFAIK you don't need any special entitlements to use NSMetadataQuery but it will only return results that are available based on your sandbox.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

adpward wrote:were you given a reason?I can't speak to Turbo3's specific case but, in general, the NEHotspotHelper mechanism is designed for folks doing captive network management apps. If you're not creating a captive network management app, it's not appropriate to use NEHotspotHelper.Turbo3 wrote:My already released app will crash when my users upgrade to iOS 9. This will make for hundreds of unhappy customers.Yeah, that's obviously not good, and we're taking this issue very seriously. Alas, I can't offer further insight into this issue at this time. I will, however, post updates to this thread as things develop.What is an alternative way to read the current WiFi SSID if I am not allowed to use the Network Extension framework?Just to satisfy my own curiosity, what are you using the current Wi-Fi SSID for?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

eskimo, thanks for your responses.We store important information regarding our users login status shared across a suite of apps in the keychain. We raise exceptions when we get unexpected statuses back from the keychain queries, as the user cannot be allowed to log in without checking the login status in the keychain. We have seen a few crashes with this status. However, it appears the user has been able to successfully get past it within the next 5-10 min after the app restarts. I'm not sure if there's anything the user has done to fix the issue in that time. So I'm curious if we should handle this status and retry the keychain query (as in it's a transitory error that can correct itself within the life of the app), or present the user with an alert advising them to restart the app or device (as in there's something wrong with the application/device state that needs to be restarted before it can be resolved).This has only happened in the field and we only receive our own custom crash reports, so I d

I'm not 100% sure what's going on here. I don't have experience with suspending tasks because… well, see below. If you have a reproducible case, please file a bug, including a small test project that demonstrates the issue. I'd appreciate you posting your bug number here, just for the record.My question for you is, why are you suspending these tasks? Tasks suspension is rarely used and, when it is, it's mostly used to temporarily disable callbacks as part of some sort of concurrency control system. That's because a suspended task can still be active on the wire; all that the suspend does is prevent it making progress internally, issuing callbacks, and so on.OTOH, if you're implementing a long-term pause (for example, the user wants to pause a download), you'd be better off calling -cancelByProducingResumeData:. Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com