The Robservatory

Robservations on everything…

 

bugs

The Calculator bug persists in iOS 11.2

It’s not as bad as it was before, but it’s definitely still there. You don’t even have to tap super fast; I can make it happen whether I’m using two fingers or one. As long as a couple of button taps are within a reasonably-quick amount of time, you’ll get the wrong answer.

Dec 14 Update: I’ve now visited an Apple Store, and can replicate the bug in iOS 11.2.1 on the X, 8/Plus, and 7/Plus. See below for a video of the iPhone X running iOS 11.2.1.
Dec 3 Update: Some users with the same phone models as those I’ve tested say they can’t replicate the bug. I’ve added a video of my phone in use, showing exactly how quickly I was tapping, and that the bug is definitely there. Click the “more…” bit to see the video.
Dec 2 Update: Users have reported the bug is fixed on the iPhone 7 Plus and the X. But it’s definitely present on the following phones: iPhone 6, iPhone 6S, and iPhone 8 Plus—I personally tested all three of those. If you have a different model and can test, please do so and let me know—I’ll update the list when I receive responses.

Below are three examples; one with 3+2+1 and two with 6-5-4. The slow-motion version shows exactly how Calculator comes up with the wrong answer, as you can see incorrect values being inserted. This was recorded on my just-upgraded iPhone 8 Plus running iOS 11.2:

I can even make this happen with a simple “3+2” test. You may argue that I’m tapping the keys too quickly, but I’m not really hitting them at super-human speed, just quickly. And more importantly, the taps should be recognized and cached in order, regardless of what onscreen animations are occurring.

Trying the same experiment with PCalc, for example, I cannot make it fail, even tapping buttons much more quickly than I do in Calculator.

Kill the fancy animations, Apple, and just make Calculator remember our key taps, please?

(more…)

Month 13 is out of bounds

And obviously, it would be, because there is no month 13. But if you’re unlucky enough to be a Mac user in the month of December, 2017, then you’ll probably be seeing a lot of “Month 13 is out of bounds” messages in your Console. And by ‘a lot,’ I mean an exceedingly excessive never-ending stream of spewage…

Thousands and thousands and thousands of them—I’m getting anywhere from two to 20 per second, continuously. Ugh.

This just started happening this morning, and it’s happening on all my Macs. I found one Apple developer forum thread that talks about the problem, and user Helge seems to point to a bug in mdworker

(more…)

Fix Messages’ broken bundled AppleScripts

While playing around with Messages this morning, I noticed that it ships with a feature that, if used, throws an error. Steps to reproduce:

  1. Open Messages’ preferences.

  2. Set the Applescript handler pop-up to any of the listed scripts:

  3. Close preferences, and try to send a message to anyone.

  4. Revel in the brokenness.

I especially like the execution error: No error message…it’s that rare non-error that tosses up an error dialog!

In any event, I think it’s shameful that Apple ships the app with a feature—plainly obvious in prefs—that breaks when used. Yes, I know AppleScript is probably dying, but that doesn’t excuse shipping the app with a clearly-broken feature; if it doesn’t work, just remove it. Apparently this has been an issue since Yosemite’s release in October of 2014!

With all that said, fixing this is incredibly easy—it took me about 30 seconds of “work” to find and fix the problem. If you’d like to use the bundled AppleScripts in Messages—either as is, or in some modified form—here’s what you need to do

(more…)

The Robservatory © 2018 • Privacy Policy Built from the Frontier theme