Thanks for the comment. "fileContents" must not have been String at that point because "\n" wouldn't have been found if it was, in fact, "\r\n" (since that is a single character and not a combination including \n).

I ended up begging the user to send Crash logs, which he did, and we've resolved the problems. (SIG_KILL also provides useful crash logs.)I still have only one log in Organizer. I've opened ticket FB7545163 about my missing logs. Barry

TomerN,thanks for your reply. This function would not be useful at all if it only finds unpaired devices. So it finds an unpaired device (which I first had to manually put into pairing mode), lists the device, I select it (which causes it to pair) and then it never shows up again? The doc does say "pairs the device" so you are probably right.So I tried it that way. Did "Forget This Device" on one of them, put it into pairing mode (which causes it to show up at the bottom of my Bluetooth Settings in "Other Devices"), ran the picker, and it still gives me a screen with no items.I've opened trouble ticket FB7545602.For your other suggestions, good ideas, but these devices don't do BLE and so no GATT.

Quinn to the rescue again!Here it is 2020 and the line-number of zero problem is still here. Per your years-old request, here is the bug report I just submitted: FB7545131 Barry

From this document:https://developer.apple.com/library/archive/documentation/General/Conceptual/DevPedia-CocoaCore/ExceptionHandling.html#//apple_ref/doc/uid/TP40008195-CH18I get the impression that it probably is possible to catch these exceptions... but using ObjC stuff in Swift is beyond me at this point.Yes, probably all exceptions are user errors. It would be nice to be able to catch it so some debug is possible.I finally tracked this one down (I think). My mainVC keeps track of what other ViewController is currently on the screen. All of those (I thought) have the necessary segue identifier. What I didn't take into account was when the mainVC was presenting a UIAlertController! Needless to say, this doesn't have the segue identifier (and I wouldn't want to segue from there if I could).Thanks for your replies. I really appreciate it!Any ideas on my showBluetoothAccessoryPicker post? Barry

A follow-up if I may.I gave my user a TestFlight version and we're narrowing down the problem. When I look in AppStoreConnect it shows that I have 4 Crashes on the beta version. (I was concerned that it was actually crashing, but the user tells me that when he kills the hung app, it is considered a Crash and lets him put in comments for the "crash".)That's all well and good, but when I go into XCode organizer, the Crashes page works on Downloading and then says "No Crashes" (yes, I've set the version/build number correctly). I know A-S-Connect says it may take 72 hours; does this mean that it may know about the crashes and XCode doesn't for that long, or they should be in both places now that they're in App Store Connect?Since the "crash" was generated by him killing the app, will it still give me something in XCode to look at?

Thanks very much Quinn! Good ideas. And I didn't know about sysdiagnose. Barry

It doesn't matter what MY locale is. I need the decimal keypad to function as if the USER's locale is en-US regardless of what her locale is...and I can't (shouldn't) change the user's locale. Basically I want to override their locale for one UITextField. How do I do that?

Thanks Claude; I am already doing something similar, but this doesn't solve the user experience problem.The field clearly shows that it should be dotted-decimal format and they know it should be dotted-decimal format, but the only thing they have on their Decimal pad is a comma. This leads them to confusion.I want the keypad to actually show a DOT.

Thanks for your reply Claude. I was using fullScreen already.I finally figured it out. The issue was that, in iOS12, the Unwinds are unwilling to return to the top SplitView Controller when the unwind-from VC was reached from the Primary page of the SplitView. All I had to do was create an unwind-action function in the VC for the Primary page (similar to the one I already had in the top SplitView Controller) and select that new action when I control+dragged the Done button to Exit.This works in both iOS13 and iOS12.(Yes, I probably shouldn't have navigation controllers because I'm not pushing and popping, but as it's turned out, now that I am unwinding to the VC that presented the page, I could be using the navigation controllers functions.) Barry

Here's some info:In iOS13, starting the Unwind segue causes a call to "allowedChildrenForUnwinding(from:)" when it is present in the top SplitView Controller. I call the Super of that in my override and the children array contains the ViewController of the Detail page (which is where I really want it to go).In iOS 12, starting the Unwind segue causes a call to that same routine BUT in the ViewController I'm trying to dismiss! The Super call returns an array with 0 elements. I tried returning the view controller I'm trying to get to and that doesn't make any difference. (The "allowedChildren..." in the top SplitView Controller is never called.

After stating exactly the scenarios and noting the two differences...I removed the Navigation controller from one of the cases, and it still doesn't work.It seems that the "problem" is caused by doing the "to" segue from the Detail page of the SplitView.