Unfortunately Runtastic crashes on iOS 9. So I switched to tracking my nordic walks with Apple Watch. This works fine for the most part. But I experienced two issue lately. One of those is quite funny, so I chose to publish the bug reports here as well.
Apple is introducing a new contacts framework in iOS 9. The do so very aggressively to even replace view controllers from AddressBookUI.framework with their new implementations. Unfortunately not without problems.
Normally I am prefer to keep quiet about bugs in iOS beta versions, but this one affects apps public on the app store which are using this view controller and therefore I felt it necessary to warn my iOS developer colleagues about it. This is the crash I was alluding to on iOS Today.
Working on an issue that has been reported for Notepad Classic 2007 (currently free on App Store) I found that UITextView has problems keeping the scroll position when showing or hiding the keyboard.
This issue didn’t occur on iOS 7 and I wasted more than 5 hours trying to come up with a workaround. The problem is that showing and hiding the keyboard is causing superflous calls to layoutSubviews on the text view which causes it to change the contentSize and contentOffset. This gets further complicated by UITextView dynamically changing the contentSize as you scroll down through text that is longer than a few pages.
It is rare that I am so confounded by a bug, so I even opened a DTS call for it, hoping that there is a workaround for this problem.
Filed as rdar://20743459 and on Open Radar.
Fun fact! Sometimes Apple engineers confuse dupes of Radars with the original ones:
And that even though my radar has the zip file with the sample app attached and the alleged original only a reference to my GitHub RadarSamples repo. Oh well… as long as Apple fixes the issue, I am happy to give the win to Peter Steinberger. Fatality!
But, I have one more bug report up my sleeve! A similar issue occurs server-side when using CLGeoCoder, so I filed this as rdar://20665320 and on OpenRadar.
Again, this bug report comes with a beautiful sample app. This is the first bug report sample app I made in Swift. Only took me 4 times as long than if I made it in Objective-C, but a developer’s gotta do what a developer’s gotta do. 🙂
This has been bugging me for quite some time, since some of my address book contacts are affected. NSDataDetector does not properly handle addresses which have more than 2 numbers with one slash.
Previously, this issue was compounded by another issue in the geocoder which would take the apartment number (instead of the street number) for determining the geographic position. To workaround this I had to add another address to some of my contacts that didn’t have the apartment number. This seems to have been fixed in iOS 8.3, but NSDataDetector is still broken.
I wanted to add a custom modal transition for the prod.ly app when you tap on a thumbnail image. I wanted to make a tutorial about that as soon as understood interactive transitions, but stumbled over a couple of bugs.
Of these one I would consider quite severe and new as of iOS 8.3, which made it a show-stopper. As long as this bug is present I cannot add an interactive percent-driven dismissal transition to my app.
I filed this Radar already back in December, without a sample. Now an Apple engineer requested that I provided one. So I did.
The problem is that a scrollview misaligns a content image if you pinch-to-zoom causing white lines to appear along the right and bottom edges.
Filed as rdar://19323748 and on OpenRadar.
Working on the prod.ly app (see screen shot below) I found this problem when adding actions to table view cells via the new editActionsForRowAtIndexPath: API. If you have a UIButton in the cell then the swipe does not cancel the tap on the button and you can end up accidentally executing the button action when you only wanted to edit.
Filed as rdar://19411256 and on Open Radar.
For the ProductLayer SDK I have built a text field that keeps track of the last used input language. When implementing this I noticed that several of the methods that UITextField claims to be implementing are not being called. Apparently this is a new bug in iOS 8.
Filed as rdar://19263531 and on Open Radar.