I have 10 instances of this error showing up in xCode, as yellow warnings. Precisely: 'MKReverseGeocoder' is deprecated first deprecated in iOS 5.0 It seems to have something to do the the Plugin BT_ screen.map. This is what appears in the .map.h file: //geocoder delegate methods -(void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFailWithError:(NSError *)error; -(void)reverseGeocoder:(MKReverseGeocoder *)geocoder didFindPlacemark:(MKPlacemark *)placemark; and this in the map.h file: //fire geocoder MKReverseGeocoder *geoCoder = [[MKReverseGeocoder alloc] initWithCoordinate:self.mapView.userLocation.coordinate]; geoCoder.delegate = self; [geoCoder start]; //let map place default blue pin return nil; I have not set up any geo locators in Buzztouch, no maps, no location. According to Apple Developer, this error has something to do with apps using Google Maps, which is no longer supported. Any suggestions how I get rid of the errors? Is it ok just to delete these sections? Or should I delete the Plugin BT_screen.map?

You should be fine to just delete the plugin. But if you do add a Geo screen, then note that it'll show a black screen.

Thanks so much. I've removed the plugin, refreshed xCode, no more errors! Cheers Flloyd

"I have 10 instances of this error showing up in xCode, as yellow warnings." We don't see any errors when compiling projects with this plugin. What iOS version are you targeting? What version of Xcode are you using? For sure Apple is moving away from Google Maps but warnings and errors are something we're always tracking down and isolating / fixing. Thnx in advance.

HI David, I'm using xCode Version 4.5.2, and targeting iOS version 5.1 Cheers Flloyd

Cool... got it. If you target ios3.0 it will work on far more devices... and you won't see this warning -:) Thx for the heads up.

thanks so much for the advice, David. I just looked in xCode, it only allows as far back as 4.3, so I'll go there for the moment.

--Click your project name on the left in Xcode --Single click your "target" to bring up the summary window. --Make sure Summary tab is selected along top (not info, build settings, build phases, etc) --TYPE 3.0 in the Deployment Target box. You can enter anything you want in this box, regardless of what the drop down makes available. Next, to confirm you entry...use the Build Settings tab and scroll down to the iOS Deployment Section. Your entry should remain :-)

Just did that, then ran simulator. 3 Dependency errors now showing: warning: iOS deployment targets lower than 4.3 are not supported (current IPHONEOS_DEPLOYMENT_TARGET = "3", ARCHS = "armv7"). (null): The CodeResources file is missing and it must be a symbolic link to _CodeSignature/CodeResources. Make certain that the bundle is on a locally-mounted volume (not a remote SMB volume), and be certain to use the Mac OS X Finder to compress it (-19062) (null): iPhone/iPod Touch: application executable is missing a required architecture. At least one of the following architecture(s) must be present: armv6 (-19033) What do you think?

Yikes....LOL. Your project download should have had all this stuff already set too, make it even stranger. In build settings tab, in the Valid Architectures setting. It should show two values. armv6 armv7s This is because different devices have different processors. And, when you say "hey iOS, when you compile this software, make sure it will run on both of these architectures." So, iOS 3.0 Deployment Target Both architectures. Clean > Build. See what happens.

armv6 is missing. Only two errors now, though! Here is one (null): iPhone/iPod Touch: application executable is missing a required architecture. At least one of the following architecture(s) must be present: armv6 (-19033) full validation log entry: Validate /Users/flloyd2010/Library/Developer/Xcode/DerivedData/beingingoodvoicesunday-dzjkmjaogcgizkdacglsrglvfbsl/Build/Products/Debug-iphoneos/beingingoodvoicesunday.app cd /Users/flloyd2010/beingingoodvoice/abeingingoodvoicesunday_v20_iOS setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" setenv PRODUCT_TYPE com.apple.product-type.application /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation /Users/flloyd2010/Library/Developer/Xcode/DerivedData/beingingoodvoicesunday-dzjkmjaogcgizkdacglsrglvfbsl/Build/Products/Debug-iphoneos/beingingoodvoicesunday.app Unable to validate your application. - (null)

@ Flloyd Not sure if this will work but just went through this hell too......this is what I did and it fixed it and now is waiting in the itunes to be reviewed.....hope you figure it out http://cl.ly/image/0Y1J1M3S2P2f

Hi Sheri, thanks for that. I agree, nice simple solution! You can't have everything, and I'm also happy to settle for 4.3 customers and up for now. Nice way of sharing too, very cool. Good luck with iTunes! Cheers Flloyd

Go Northwest to the rescue...here is another string on the armv6 that explains how to change your settings. http://www.buzztouch.com/forum/thread.php?tid=B7AB21E0FE04A1B0CFB644B&command=isSearching&currentPage=1&topicTitle=armv6&createdBy=&repliedBy=&minViews=-1&maxViews=-1&minReplies=-1&maxReplies=-1&forumCategory=

Thanks Susan, I checked out that string, realised there would be a whole load of xCode adjustments to make and decided to leave it for the moment. If it becomes apparent that I need to have that facility when I'm closer to submitting, I'll deal with it then. Thanks so much for the link, lots of suggestions there. Cheers Flloyd

Good discussion here but none of this explain who MY machine shows no errors and compiles with iOS 3.0 target (the way the download is setup). Could it be related to how "old" the "oldest" SDK on my machine is? I'll bet it is. In fact...that makes perfect sense now that I'm thinking about it. If you dont' have the 3.0 SDK on your machine it won't be capable of compiling for that older architecture. Duh. It's easy for me to assume everyone has the same Xcode setup but we are reminded time and time again that things are slightly different on each machine. This means we should probably update the download so it doesn't reference the iOS 3.0 target (older devices) anymore. I say this because new folks that are just getting started couldn't possibly have this older 3.0 SDK on their machine...they just downloaded Xcode and the latest download doesn't come with it. I'll look into it. In the meantime, @Flloyd will for sure have to settle for the newer 4.3 target without going through a bunch of tweaks.

Gotta love that I'm logged in as Bigfoot - my test account. Hee hee. Bigfoot lives in Maine in spirit only, Monterey in reality :-) David.

Thanks for clarifying that, @Bigfoot, otherwise David @Buzztouch, otherwise henceforth to be known as Big Heart to go with the Big Mountains! Cheers Flloyd

is there a ready code to replace the problem one?

???