eskimo

Alas, I don't know what CryptSignMessage does; you will have to ask your question in terms of the behaviour you want. Is it a low-level signing operation? Or a high-level CMS operation? ps I moved the thread over to Core OS > Security, which is a great home for questions like this.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Hi eskimo,My App is in English and Portuguese, the primary language is English, I can change the language of my App without problem, everything is good and proper. What I want is to know what is the language that is configured the iPhone system (setting), after I know that I change my App to English or Portuguese. My App works well to detect the language and changes automatically, the problem I detected was that I am seeking localization and this leads into error when it comes to location in Portugal but the iPhone is set to English. There has to be a way to know the settings that are on the iPhone without being compared to the languages of my app have, I think that's what makes [[NSBundle mainBundle] preferredLocalizations]. The link that you sent me is more about the internationalization of the App, that I have correct.Sorry my bad English (I not who write the English part of my App, lol).Thanks,JFontes

I'm sorry, I'm still really confused as to your goals. I suspect that there's some subtlety here that, ironically, is not making it across the language barrier.If we walk through some specific cases, perhaps you can tell me what you're looking for:Your app is localised into English and Portugese. One of these, it doesn't matter which, is your development language.If the user's preferred language is Portugese, you launch in Portugese. That's good.If the user's preferred language is English, you launch in English. That's also good.If the user's preferred language is neither Portugese nor English, you launch in your development language. That's less than ideal, but the best you can do.What other case are you trying to solve?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I have downloaded the TLSTool from your link and I have built it, but it doesn't display the TLSVersion as in your example, see the output result below.Yeah, that's my bad. I'm using an updated version of the tool that contains features beyond that found in the public version. My apologies.Where can I get the TLSTool displaying the TLSversion?If you drop me a line at my individual email address (see my signature), I can send you a copy.I also need to work on getting my latest code on the public web site. Hmmm, how to find the time...Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

I'm going to assume that this is the same issue as your other post, so I'll respond over there.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

You seem to be using a self-signed certificate. Is that your final plan? Or is that just for initial bring up?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Saying that 'String?' is not convertible to NSStringThe immediate cause of this error is that textField.text is optional (it's of type NSString?) and thus can't be converted directly to NSString. I'll note that UITextField's text property is often nil when the text field is empty, so you do have to deal with this. Probably the easiest solution is to treat nil as the empty string here. For example: let text = textField.text ?? let prospectiveText = (text as NSString).stringByReplacingCharactersInRange(range, withString: String())Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Hi eskimo,Once again I apologize for my English, I try to be simple and direct.iPhone with iOS 7.1.2With:- Setting - General - International-> Language = English-> Voice Control = English-> Keyboards -> 3-> Region Format = Portugal-> Calendar = GregorianI have:[[NSLocale currentLocale] localeIdentifier] -> pt_PT[[NSBundle mainBundle] preferredLocalizations] -> one object with pt-PTWith:- Setting - General - International-> Language = Português (Portugal)-> Voice Control = Português-> Keyboards -> 3-> Region Format = Portugal-> Calendar = GregorianI have:[[NSLocale currentLocale] localeIdentifier] -> pt_PT[[NSBundle mainBundle] preferredLocalizations] -> one object with pt-PTiPhone with iOS 8.4With:- Setting - General - Language & Region-> iPhone Language = English-> Preferred Language Order = English, Português (Portugal)-> Keyboards -> 3-> Region = Portugal-> Calendar = Gregorian-> Advanced = Automatic - OnI have:[[NSLocale cur

Thanks very much eskimo, this was a very useful link. Went through the code and it makes sense, so I'll play around with it. I know I'm pushing my luck (can also submit a different thread if you prefer?) but do you happen to know of a feature-by-feature and limitations comparison article between Multipeer Connectivity and NSNetworkService. After going through the code it seems that NSNetworkService is better suited for a server-client type of applications but then again I read this Apple article which suggests that Multipeer Connectivity is built on top of NSNetworkService and simply adds convinience.https://developer.apple.com/library/mac/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/Discovering,Browsing,AndAdvertisingNetworkServices/Discovering,Browsing,AndAdvertisingNetworkServices.htmlMany thanks,Stefan

Reply to 300BaudNice user name (-:Multipeer Connectivity does not support operating in the background; it's really that simply. You may be able to get some things to work, but I recommend that you not go down that path because, when you do unsupported things, you run the risk of future changes breaking your code.The networking stack does, in general, support operating in the background. Where things start to go wrong is if your app gets suspended in the background. Technote 2277 Networking and Multitasking has the details. So, if your already have a way to prevent your app from suspended—for example, it's an audio app that's playing music—you can use other networking APIs in the background quite successfully.OTOH, if you can't avoid suspending in the background, you will have to look at APIs that let you make progress while you're suspended; that typically means using NSURLSession background session support, possibly in conjunction with UIApplication's background fetch support.Share and Enjoy — Quinn The Eskimo

Once again I apologize for my English [...]No worries; it's better than my Portugese, or any other language for that matter )-:My theory here is that the system has not picked up that your app is meant to be available in English. Specifically, in cases 1 and 3 -preferredLocalizations is coming back as Portugese because the system doesn't think your app can do English.Have you looked at QA1828 How iOS Determines the Language For Your App? That explains, in some detail, how iOS decides what langage to run your app in.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

Same problem exists with tes app also. Zh-Hant.lproj works fine for Chinese Traditional and Chinese Traditionl(Hongkong) but doesnot work for Chinese Traditionl(Taiwan).Indeed. There seems to be some confusion about whether 'Chinese as used in Taiwan' should be zh-TW or zh-Hant-TW. Specifically, the Preferred Languages list in the Languages & Region preferences panel uses the former and Xcode assumes the latter (both in the main body of its 'add localisation' popup menu and in the extra languages hung off the Other submenu). If I rename Zh-Hant.lproj to Zh_TW.lproj, everything works fine. But Xcode doesnot provide any option to add Zh_TW.lproj.Indeed. It's OK to do this—historically it was necessary when dealing with localisations that Xcode didn't specifically understand—but it's clearly less than ideal.You should file a bug about this. Honestly, I don't know enough about the history of Chinese localisations to tell you whether this is a bug in Xcode or a bug in OS X but, either way, something needs to b

iOS 7? That's really old and, more pertinently, immediately after we added iCloud Keychain, which is what all of this 'synchronizable' stuff relates to. Can you retry on something more modern?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com

So as a work around to get it to collect all my data (without being rate limited) I throttle down the rate of the requests that will rate limit me with a 2 second sleep for each of those calls, and run all my requests synchronously, in serial.Wow, so you're deliberately trying to make your networking slow (-: As you might imagine, that puts you somewhat outside of the target market for mainstream networking APIs.If you just want a drop-in replacement for +sendSynchronousRequest:xxx, that's pretty easy to implement within NSURLSession. We don't provide it as an API because we think it's a really bad idea—for all the reasons we've been discussing in this thread—but given your rather unique constraints it probably make sense. Earlier you wrote:Use a dispatch_semaphore with NSURLSession. I think this is a very bad option. In my opinion this is unacceptable because it's going to create a lot of extra code on my end (the customer) and be difficult to maintain, and more prone to bugs.I think you're radically overest

Yes your're right, I'm using a self signed certificate. Is there an issue due with this?Yes. ATS is pretty much fundamentally incompatible with self-signed certificates.In itself, that's no big loss IMO. Self-signed certificates are a bad idea and you're much better off avoiding them and instead using a custom CA instead (Technotes 2232 and 2326 have the details of this). However, that approach is also incompatible with ATS as things currently stand.In short, to work with ATS you will have to get a certificate issued by a trusted CA. The alternative is to disable ATS (only for the domain you care about, of course) and then, if necessary, do your own custom trust evaluation.ps borgiscool and Lucky7, please start a new thread for the b4 regression; I'd like to use this thread to help sebastien78 with the more fundamental problem.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com