Recent Comments

Open Radar 30104132: Communication between iPhone and Apple Watch breaks down occasionally

Additional note:

We also saw some occasions where the phone is clearly not reachable (flight mode enabled and wifi and bluetooth off) and the reachable property of the WCSession reported true.

Seems to me like this flag is just totally broken and should be ignored by app developers...

By florian.goessler at Feb. 17, 2017, 10:57 p.m.

Open Radar 27994304: Data corruption using Swift 3 enum with associated values

Appears to be fixed in Xcode 8.3 beta 2.

By at Feb. 17, 2017, 3:54 p.m.

Open Radar 30577177: Setting UIAppearanceProxy on UINavigatonBar screws up MFMailCompose/MFMessageComposeViewController's nav bar

Sample code available here:

By designatednerd at Feb. 17, 2017, 3:51 p.m.

Open Radar 30574703: UITextView spell checking dots should be drawn according to the content scale when inside a scroll view

Sample Code

By michaelhochs at Feb. 17, 2017, 9:02 a.m.

Open Radar 30574627: UITextView spell checking is huge and overlaps next line's text when dealing with small font sizes

Sample Code

By michaelhochs at Feb. 17, 2017, 9:02 a.m.

Open Radar 28844763: Bug in OpenGL ES 2.0 emulation via Metal?

It seems the bug is gone on iOS 10.3 beta 2

By r.kuznetsow at Feb. 17, 2017, 7:24 a.m.

Open Radar 30114548: Volume controls behave incorrectly when connected to LG UltraFine USB-C monitors

Same issue. Really hope this gets fixed as it does go super loud going from headphones to the speakers and not realising the levels.

Open Radar 29799091: Specifying a currency in a SiriKit payment is not displayed correctly

I had the same problem. But you can solve this by confirming the currency like this:

func confirm(sendPayment intent: INSendPaymentIntent, completion: @escaping (INSendPaymentIntentResponse) -> Void) {
    let response = INSendPaymentIntentResponse(code: .ready, userActivity: nil)
    response.paymentRecord = INPaymentRecord(payee: intent.payee, payer: nil, currencyAmount: intent.currencyAmount, paymentMethod: nil, note: intent.note, status: .pending)


Then it shows the correct currency.

By don.pironet at Feb. 16, 2017, 9:06 a.m.

Open Radar 30156799: The SSH config option "UseKeychain yes" does not seem to actually use the keychain?

FYI, they're now stored in the "Local Items" keychain (which can't be locked), and the passphrase item is inexplicably not visible through Keychain Access.


Open Radar 29758498: NSTextField with tabs in text displays incorrectly in 10.12.2

Closed as duplicate; original also closed; bug still present in 10.12.3

On January 9, 2017, my bug report was closed as a duplicate of another bug.

On January 10 the original bug was also closed. Unfortunately I do not know why (e.g. was it fixed, was it marked "won't fix", or what).

The problem is still present in 10.12.3; the workaround (adding wantsLayer to the window's content view) continues to work.

Open Radar 23869832: Support 32GB of RAM in the Mac mini (Late 2012) and Mac mini Server (Late 2012)

Let's do this. My Mac Mini is a VM hosting machine, going strong! Only thing holding it back is the 16 gig RAM limit.

By cchichester at Feb. 14, 2017, 6:26 p.m.

Open Radar 30143243: otool fails to disassemble whole binary

14-Feb-2017: Me

Changed the Rank to Medium as even though the output of llvm-objdump is not as "nice" as the one from otool (personal preference I guess), it works as a work-around when otool fails.

By m.hanauska at Feb. 14, 2017, 10:36 a.m.

Open Radar 30143243: otool fails to disassemble whole binary

26-Jan-2017: Me

Okay, the "community" basically says you are a liar. Sorry, not trying to insult you here but that's what I've been told.

First of all, llvm-objdump -disassemble does not start disassembling where otool does, it starts disassembling at the start of the text section, just like otool-classic does. So already that was a untrue. It is not the truth that
llvm-objdump only starts disassembling at the first known symbol.

xcrun llvm-objdump -disassemble binary:

Disassembly of section __TEXT,text: text: 100002100: 55 pushq %rbp :

100002100 is the start of the text section and there is no symbol anywhere near it!

Second there is a llvm-objdump -disassemble-all, that really disassembles the whole text section, from the first to the last byte and that is even more than otool-classic or any other otool version has ever disassembled. So all you would have to do is to just that option if you want all the disassembly.

To summarize above: No behavior of llvm-objdump explains the odd behavior of otool. otool is just behaving wrong and that is definitely not the fault of llvm-objdump. Please re-open that bug and fix otool. So far all you did was making false accusation to the llvm community but if otool misbehaves, than this is your mistake as you are in control how otool shall behave.

By m.hanauska at Feb. 14, 2017, 10:36 a.m.