This bug exists for numeric fields as well. You can configure a min and max constraint in the model editor, but only the max limit will exist at run time. Numeric properties of course don't have a regex field, so that's no help. It might be possible to roll your own via userInfo properties, with some custom validation code.

It would be very helpful it this could be built into the default Xcode. We will be working around it for the time being.

Can you file a bug report at Apple as well? I just heard back from them that they categorize it as a duplicate of #10147878 (which unfortunetly isn't on openradar)

same issue replicating in all the ios versions only way to refreshing the document removing cache.

Status is now Duplicate/9111607.

This bug was just closed as a dup of rdar://10385163

This bug was just closed as a dup of rdar://9720925

This bug was just closed as a dup of rdar://9896209

This bug was just closed as a dup of rdar://8751876

I am having an issue similar to this on iOS 5.0.

I am recording audio and when the user presses a button, an alert view pops up asking them if they want to save the audio file. When they press the button to get the alert view, if I just pause the audio recorder, then stop it when they click OK on the UIAlertView, the file is corrupt. However, if I stop the audio recorder before I show the UIAlertView, then it is fine. I can't do that because if they cancel, I want them to continue recording.

This pretty much reflects my experience, and with the same version of Xcode.

I found this post after searching on Instruments not symbolicating the call tree, and pointing its stupid ass directly to the app and dsym file still doesn't work. Oh, and you failed to adequately criticize the piece-of-shit UI for pointing it to the dsym file. It presents a box in which to add paths, but you can't drag from Finder into it, and you can't even paste a path. You have to manually navigate to the build products directory, which of course is impossible by default because Apple has inexplicably decided to hide the ~/Library directory. So first you have to go to the command line and unhide that (which I swear I did before but 10.7.3 update re-hid it).

Oh, and the next time you come back to the dialog, guess what? The path you just put there isn't shown anymore. It's empty once again.

And yep, Xcode frequently hangs when it's doing nothing. You can literally be staring at the editor, and it starts pinwheeling. POS.

xcodebuild also has a -xcconfig parameter which allows settings to be set. These are documented to take precedence over everything, including command-line options.

As with command-line options this works correctly for the 'build' action but 'archive' action currently ignores them.

04-Feb-2012 12:25 AM Apple Developer Bug Reporting Team : This bug has been closed as Duplicate. We are aware of this issue and are tracking it under the Bug ID listed below in the Related Problem section of your bug report. To check the status of the original bug report, please visit the Related Problem section of the Problem Detail view of your closed duplicate bug.

1) link the CoreFoundation library into the application so it gets loaded (and initialized) at runtime in the main thread. The main application thread does not need to make any API calls into the CoreFoundation library....simply loading it is sufficient.

2) Use the DYLD_INSERT_LIBRARIES environment variable to specify the CoreFoundation library be pre-loaded when starting the application. (see DYLD(1) man page) ex: % DYLD_INSERT_LIBRARIES=/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation % export DYLD_INSERT_LIBRARIES % app

Engineering has determined that this issue behaves as intended based on the following information:

The video view needs to be in a window and the video needs to be prepared to play before calling setFullscreen:YES.

Apple confirmed that this is a known bug, but there's a workaround. Instead of using the model editor's min and max length fields, use the regular expression field. Validate against a regexp that matches the number of characters. For my example of requiring 3-10 characters, use "^.{3,10}$" to validate any string in that length. If you want to require non-whitespace characters, use "^\S{3,10}$". Adjust the 3 and the 10 in the regexp to match your requirements. (Thanks to Marcus Zarra for suggesting this).

playerLayer.bounds = playerLayer.bounds;

works around.