All of us who have updated to Xcode 4.6 are getting parse warnings. Not a big deal; things still flow as desired. But it is annoying. I've found it's actually not a big deal to fix the issue. "Parse Issue: 'the value' used as the name of the previous parameter not the selector" https://dl.dropbox.com/u/115208762/parsefix.png Just find an offending statement, correct it, and perform a search/replace for other instances. Sometimes it's one or two, sometimes it's twenty or more. Cheers! -- Smug

Thanks Smug.......Time to get to work!!! Dave AWESOME! AWESOME! AWESOME! Smug, cleared all 107 warnings in 15 minutes, great job smug!!!

Hey Smug Thanks again. Cleared up all of the warnings using your advice. Submitted the app that I was working on to apple for review with no issues!!! Dave

cool nice fix..although im waiting on upgrading both xcode and buzztouch 2.1.8. way too much work ahead. grateful for forum post like this. to help in those moments of upgrading!

you might want to download another copy of BT 2.1.8 I didn't realize they have been adding new upgrades to the package; I was still dealing with not being able to delete screens, and they've had that fixed for a few days now... I upgraded on 7 Feb... so all files with a mod date later I copied over to my server... Haven't ran through 'everything' just yet, but the delete screen works dandy now... Cheers! -- Smug

Many thanks for that Smug! Fixed All of my parse issues!

I just made a post that was in error. Nothing to see here... move along... Cheers! -- Smug

Hi, I am wondering if there would be any problem if we submit the app to apple for review without fixing the warnings. Mine were all parse issues too, but I wasn't sure if it was best to do the correcting edits.

It's pretty easy to fix. Appl has been pretty picky lately.

@Webnevees. I have just uploaded an app for review with 132 yellow warnings. Apple reviewed it and released it for sale without comments.