Find the WTD in iPhone Xcode builds!

-
I'm an avid iPhone developer and I've been developing with Xcode for Mac OS X a while (about 4 years) now. In all my days I have never seen an error from Xcode (even the crazy ones from objc) so sick and twisted that it takes almost an hour to fix.
Luckily this fellow ran into the same issue (and posted it). I wasn't using a button, but a "search bar"; and when I removed it everything built just fine. I don't think IB files like multiple "bars". Oh well, back to hard coding GUIs.
[error-message]
*** -[UIImage encodeWithCoder:]: unrecognized selector sent to instance 0x44d470
[/error-message]

I also learned that Xcode or IB doesn't like "lonely" outlets. Meaning, if you assign an instance to an outlet in IB, you better make sure the instance variable is in the corresponding class file. It will build and launch, but crash with some error like: __TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION__

Fun with WTDs (what the deuce).

Comments

Anonymous said…
I'm using a UISearchBar as well and am running into the same error when compiling, but still can fix after reading both your and the other post. I am using beta 5 and cannot find the "Show Pressed Feedback..." (or anything like it) attribute checkbox the other post mentioned in IB. Any other suggestions? Thanks.
May 11, 2008 at 10:52 PM
C. Bess said…
Honestly, I don't have any "real" suggestions; other than adding the "conflicting" UI control dynamically (via hard coded fun). Sorry, but until the final release is deployed I think we will be at the mercy of Apple's iPhone Dev teams.
May 11, 2008 at 11:19 PM
casa sims said…
having the same sort of problem with UIPageControl. I can't find any mention of this anywhere so either it is just me or no one is trying to use this control in IB. The only example I can find for this component is in UIShowcase and Apple could not possible have produced a more worthless example.
May 20, 2008 at 8:15 PM
Anonymous said…
Interface Builder can help with Outlet issues - open the XIB file and click on the info (i) button in the NIB document window (the one that shows the view components in a list).

If there are issues, they often show up here.

Hope that helps ....
Another iPhone n00b :)
November 10, 2008 at 4:11 PM
Post a Comment

Popular posts from this blog

Python SUDS with Windows Authentication (SOAP)

-
While intergrating Plone with CRM4, I stumbled upon Suds. However, it didn't support NTLM. Then I found python-ntlm, and merged the two libs. Below is the result. You can add it at the bottom of suds/transport.py class WindowsHttpAuthenticated(HttpAuthenticated): """ Provides Windows (NTLM) http authentication. @ivar pm: The password manager. @ivar handler: The authentication handler. @author: Christopher Bess """ def __init__(self, options): # try to import ntlm support try: from ntlm import HTTPNtlmAuthHandler except ImportError: raise Exception("Cannot import python-ntlm module") return HttpTransport.__init__(self, options) self.pm = u2.HTTPPasswordMgrWithDefaultRealm() self.handler = HTTPNtlmAuthHandler.HTTPNtlmAuthHandler(self.pm) self.urlopener = u2.build_opener(self.handler) u2.install_opener(self.urlopener)
Read more

Text Sherlock the OpenGrok alternative (Source Code Search Engine)

-
Image
OpenGrok has taken much to long to setup in the past, so in my dissatisfaction, I wrote Text Sherlock . Text Sherlock strives to be an easy to setup version of OpenGrok , written in Python. Think of Text Sherlock as a personal source code search engine. But, it can be run from a dedicated server. Features: It has built-in support for whoosh and xapian backends. It provides a web search interface similar to GitHub. It quickly installs. Set the configuration options in the local_settings.yml script. Then run an installation script in your install directory. Once done, everything is a simple command. Web search interface. Matched document interface. Well documented and it works as expected. Check it out and drop a comment or submit an issue via GitHub. https://github.com/cbess/text-sherlock
Read more

How to remove, update, or replace the WKWebView inputAccessoryView

-
Many others, including myself, have been trying to safely modify the WKWebView.inputAccessoryView. Now in iOS 13+, you can do it! TL;DR; The WebKit team update the code, Apple updated their dependency in iOS 13. Swift code sample: import WebKit class RichEditorWebView: WKWebView { var accessoryView: UIView? override var inputAccessoryView: UIView? { // remove/replace the default accessory view return accessoryView } } In another class somewhere: // set accessory view to replace it, if left untouched, then it will be removed let webView = RichEditorWebView() webView.accessoryView = SomeAwesomeInputAccessoryView() Because WebKit is a library that iOS uses (like SQLite), I assumed that Apple would update that dependency as well for iOS 13, since the change was resolved around June 2019. References: https://trac.webkit.org/changeset/246229/webkit#file1 https://bugs.webkit.org/show_bug.cgi?id=198631 It was too difficult to find the answer, s
Read more