Cihat Gündüz<p>In <a href="https://iosdev.space/tags/Swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Swift</span></a>, it's easy to get error messages wrong. It's due to a design flaw in the "Error" protocol itself, introduced for <a href="https://iosdev.space/tags/ObjectiveC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ObjectiveC</span></a> compatibility. I've seen people write below code all the time. I fixed this flaw in <a href="https://iosdev.space/tags/ErrorKit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ErrorKit</span></a>: Just conform your errors to "Throwable" instead! 💯</p><p>Learn more: 👇 <a href="https://iosdev.space/tags/iOSDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>iOSDev</span></a> <a href="https://iosdev.space/tags/ErrorHandling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ErrorHandling</span></a> <a href="https://iosdev.space/tags/DevTips" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevTips</span></a><br><a href="https://www.fline.dev/swift-error-handling-done-right-overcoming-the-objective-c-error-legacy/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">fline.dev/swift-error-handling</span><span class="invisible">-done-right-overcoming-the-objective-c-error-legacy/</span></a></p>