• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
-performSelector: exception... in one build configuration
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

-performSelector: exception... in one build configuration


  • Subject: -performSelector: exception... in one build configuration
  • From: Steve Christensen <email@hidden>
  • Date: Tue, 01 Nov 2011 22:23:09 -0700

No, I don't think this is a Cocoa issue.

I recently moved an app project from Xcode 3.2.6/iOS 4.3 to Xcode 4.2/iOS 5.0. The project is set up to build debug (no optimizations, debug-only status and error messages in the code), release (full optimization, code stripping, etc. for local testing), and distribution (same as release except for an app store distribution profile) configurations.

Today I ran into something weird. My app includes a category on NSUserDefaults that adds some app-specific getter/setter methods. In most cases I'm just calling, e.g., [[NSUserDefaults standardUserDefaults] foo], but for one case I'm using [[NSUserDefaults standardUserDefaults] performSelector:@selector(foo)].

This worked just fine for previous builds (all configurations) with Xcode 3.2.6, and works fine for simulator builds (debug/release) and device builds (debug), but crashes with an unknown selector exception for a release device build. While trying to track down what's going on, I added a NSLog call that prints the result of -respondsToSelector: for that message selector and it says that the selector exists for all the cases that don't crash, and that it doesn't exist for the case where it crashes.

Note that there are several methods in the NSUserDefaults category that are also called in both ways, and except for one getter/setter pair, all of the direct method calls and -performSelector: calls work fine for all configurations.

Does anyone have some ideas on what might be going on here? I haven't seen something like this happen before unless the selector really doesn't exist.

steve

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: -performSelector: exception... in one build configuration
      • From: Michael Babin <email@hidden>
  • Prev by Date: Re: Symbol Navigator
  • Next by Date: Re: Static Analyzer Problems
  • Previous by thread: Re: xcode4 and Lion causes freezes when saving
  • Next by thread: Re: -performSelector: exception... in one build configuration
  • Index(es):
    • Date
    • Thread