<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Tewha.net</title>
    <link>https://tewha.net/tags/support/</link>
    <description>Recent content on Tewha.net</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Sep 2012 14:00:00 +0000</lastBuildDate>
    <atom:link href="https://tewha.net/tags/support/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ADC incidents</title>
      <link>https://tewha.net/2012/09/adc-incidents/</link>
      <pubDate>Mon, 10 Sep 2012 14:00:00 +0000</pubDate>
      <guid>https://tewha.net/2012/09/adc-incidents/</guid>
      <description>&lt;p&gt;In the past, I’ve tried to avoid using ADC incidents. You get two a year per program, and most years I’ve avoided using any. This year, I decided to use them both the iOS ones up before renewing.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>In the past, I’ve tried to avoid using ADC incidents. You get two a year per program, and most years I’ve avoided using any. This year, I decided to use them both the iOS ones up before renewing.</p>
<p>The first one was clarification on how to fix a bug demonstrated by some Apple sample code. I got a response, but it wasn’t especially satisfying. But that’s okay, because in the end I found a way to do a different UI and avoid the bug entirely. Let’s call it a draw.</p>
<p>The second one, however, was a mistake in how I was using UIKit that I didn’t realize was a mistake. I boiled it down to a <a href="https://github.com/tewha/ExtraGridLines">test case</a> and submitted the project to Apple. As part of solving the incident, Apple not only explained what I was doing wrong, but provided snippets of code that would work.</p>
<p>This would be gold, but they also fully corrected my code the code I’d sent.</p>
<p>Of course, when I tried to integrate the solution back into my real application, I ran into other problems. However, the explanation Apple had offered me was enough that I was able to solve those other problems, too.</p>
<p>Basically, I got a fantastic code review out of that DTS incident by someone who clearly knows iOS and UIKit better than I ever will. Total win.</p>
<p>I don’t plan on wasting these in the future, but neither will I horde them in case of emergency. They’re worth using for the really nasty problems, and they’re not incredibly expensive to replace — $99 buys another two incidents.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
