So i just updated to iOS 6.1 and Xcode 4.6. I run my app and get 107 Parse errors. Anyone know if this is a BT thing waiting for an update? Push still works. All of the plugins seem to be working. Thanks Dave

Hi @Calypso_Kd - Same issue here. I posted in this thread: http://www.buzztouch.com/forum/thread.php?fid=B322B373DC8427F49853C78&tid=B322B373DC8427F49853C78 I'm guessing Buzztouch has something in their code to update. If I have to I'll revert to a backup of my system, but right now I'm lucky enough to be between major projects (planned as I was waiting for Push to be fully released too...). I would have to recommend that anyone with critical work to do wait for an "All clear" from Buzztouch to use Xcode 4.6. Best of luck! -William

It seems that the higher your target the more warnings. When I set the target to 4.3, I get 107 errors, 5.0 gets 112 warnings, 6.1 gets 164 warnings. No errors though. The app launches and runs Dave

Same results here, though my numbers on my particular project are a little different.

Hi guys...I'll add a bit to this. Happens every time Apple releases an update to Xcode (4.6 in this case) or iOS (6.1 in this case). I most cases existing projects compile fine but may show tons of warnings. In some cases they don't compile at all and show actual compiler errors that prevent them from compiling. It's looking like projects are compiling OK but we have some work to do. When this happens, and it happens every single time, we end up updating / fixing / altering the core files related to all of your projects to account for the newly released changes. We've already begun doing this. It's usually a few days, and sometimes a week or so until we get all the gotchas ironed out. At that point, project downloads will stop showing warnings or erros. Hope this helps. Don't fear too much. All will be well. d.

Thanks David! Cheers! -- Smug

As usual David, you guys are the best. No worries at all. Figured it was related to the new updates. Thanks for all your hard work. Darn those Apple engineers who keep doing this to us!!!! ;-)

David, will this also sort issues for 1.5 compiles ? I have a 1.5 APP that needs updating and cannot because of the iOS 6.1 SDK and XCode upgrade. Please let me know. Thanks again for all your efforts appreciate it !

Thanks Apple. Just what we needed. David/BT have been working like mad to get the Self Hosted pkg released- and now he's gotta go thru his code and fix a bunch of depreciations just because he has nothing better to do.... Sorry David..... I'd suggest thinking about NOT being an early adopter of updates if you are a developer. customers will wait of NEW features - they HATE when old/working features break.

Thanks for the update @David

@thegibcoyote - 1.5 is no longer supported in updates. I imagine it's possible to make 1.5 apps work with 6.1, but you are pretty much on your own. Would this be of any help to you? -https://www.buzztouch.com/files/howtos/V15appToiOS6.pdf

@Absentia I am aware about 1.5 thanks for that. I am running a Self Hosted 2.0 environment but my 1.5 app is still not converted as it will take me a long while to mirror what I have in it. In meantime need to keep it updated and running reason for asking about the possibility of 1.5 working on 6.1 Thanks

I just download new source code, and I think all of the iOS 6.1 errors are gone.

Hello Everyone, I'm brand new to BT...I'm hoping that i'm just a victim of bad timing. I downloaded Xcode for the first time and got 4.6 just as it appears that BT was working to reconcile everything. So the apps that i've been playing around with are loaded up with the "parse issue" issues that i've been reading about in this thread. My question: should i still be getting these messages at this point? Is it just a matter of needing to be a little more patient and these parse messages will go away? or do i need to dive in and figure out what's going on with these parse issues? For example, for this line: +(void)showIt:(id)theCallingObject:(NSString *)theMessage; i get this message: "`the calling object' used as the name for the previous parameter rather than as part of the selector"

Same here....hoping that it's just a temporary thing, but not sure if it should still be happening at this point.

From what I've read here in the forums, due to the recent release of iOS 6.1 and the new Xcode, they're working on updates to the deliverable. Certainly is bad timing, but these are really good people here and I trust a resolution to the problems quickly. Hang in there and they'll prove it to you too. -William

Could this be related to the blank screen I am getting in the simulator? I'm using xCode 4.6 iOS 6.1 This thread didn't seem to help: http://www.buzztouch.com/forum/thread.php?tid=D7F0A9721B54E14D28E746C&fid=06DB0BCB08E2222&sortColumn=FT.id&sortUpDown=DESC&currentPage=1

Awesome :D

@David "It's usually a few days, and sometimes a week or so until we get all the gotchas ironed out. At that point, project downloads will stop showing warnings or erros." Hi David. Any news regarding all the errors I get after upgrading Xcode ???

Hi guys, I'll just chuck in a suggestion for the moment. If you're wanting to test out any apps on the simulator, go to a previous version of Xcode. The previous 4.5.2 works as it should do, but you won't be able to test your app on iOS 6.1. Here's a tip if you want to test on a real device running iOS 6.1. Go into Xcode 4.6, and register your device there and get the profiles you need. Now quit that and go to the previous version and try testing there. Always works for me. Here's a download link to the previous versions if you already have the latest 4.6: https://developer.apple.com/downloads/ You'll find the download somewhere in there.

Thanks. I have downloaded 4.5.2. Now I Can test my apps without receiving 130 errors.

Thank you smugwimp!! Awesome find https://www.buzztouch.com/forum/thread.php?fid=BCD244553C34C5A4AD6CEC3&tid=BCD244553C34C5A4AD6CEC3

Two things to comment on: 1) Yes, we've been working out LOTS of differences in how the compiler helps devs like you and I find and improve our code. It's turning out that some "once OK" shortcuts are no longer OK as far as Xcode is concerned. There are lots of ways to organize method declarations and other programming structures and it's turning out that Xcode's latest version is FORCING us (all devs) to stop using some older, once allowed shortcuts in our syntax. I've been fixing these for two week! LOL. 2) Developer Profiles: You'll see a new section in your Developer info screen (Account > Developer Profile) titled "Development Environment" This is our first step towards tailoring downloads to your device / platform / version. For new folks, this may not make much sense. For folks that have been with us awhile, and have experienced the famous "new xcode version" issue, this should make lots of sense. The idea: If we know what type of computer you're using when working with the iOS and Android SDK's, we may be able to prevent some headaches for you. Example: Not everyone has the ability to use the latest greatest Xcode version (depending on their machine) so it makes sense that we would not deliver them a project that won't compile in older versions of Xcode! Get your Developer Environment stuff updates so it's complete when we start customizing downloads. I'll continue on the syntax hunt until the latest Xcode stops yelling.....

Thanks David!!

Thanks David. Looking forward to getting this sorted.

Thanks David, all those warnings made a little nervous, but I must confirm that the project compiles and runs without crashes. Wish you a lot of strength to fight with all the stuff (you do it for us too). Frogman

Having the same problem with Xcode 4.5.2 and 4.6 versions...Hope you fix it soon!!!

Georgios, it's a simple fix. Check out this link https://www.buzztouch.com/forum/thread.php?fid=BCD244553C34C5A4AD6CEC3&tid=BCD244553C34C5A4AD6CEC3

thank you very much, I've seen this post but in my case there are 100 errors and I was wondering if there is another easiest way...

I had 107 warnings and it only took 15 minutes to go through and clear each one in Xcode. It's just a matter of putting the curser to the left of every : (except the first one) in the line of code with the warning and hitting the space bar one time. As you go along the warnings just disappear. To find the line with the warning just click on a warning on the left after you run the app. I'm assuming that you meant 100 warnings ( yellow) and not 100 errors (red)

yes exactly...100 yellow errors...ok I'll try this out and I'll write the results

Same problem guys, 107 warnings and into simulator the phrase: "the configuration data for this application is invalid" with black screen. I tryed also with simulator 5.0 and 5.1 but the same results...but i'm sure BT will fix these bugs!

Hello, Im new in town. I have this bad experiences just from my first app, so i dont 
have the clear conscience about the BT plataform works. I have changed my membership from free to member, but now i have no the opportunity to take advantage of this. For the administrators: Do you have any idea of an estimated time to fix the system? I will appreciate very much your response about this matter. Thanks

@ferga you can rest assured that @David and the team will not rest till they fix every bug related to this issue. This is probably the reason other cookie cutter app making websites don't supply the source code but I can honestly say that no one backs their product more than @David and the buzz touch team so I don't think it will take too much longer for all harmony to be restored and I am sure coffee sales in CA will have jumped up 25% in last couple of weeks Lol.

Nice speech Mr Stuck!

@Mr stuck, Thanks for your response, makes me feel better, feel that i have not taken a bad decision. Seems like the most of developers posting at this thread are full convinced of the sensitivity and professionalism of the buzztouch developers. Good day!

Hi @ferga, we are aware of you concerns and truly appreciate your support. Lots of updating when Apple decides to change things up on us. that is also why we are now asking in your "Developer Profile" that you also fill in the "Developement Environment". Lots of folks using different versions of Xcode and all versions require different attention. We are working as we speak to clear up the issues:) Thanks again for your Member support, and 3 stars too, nice! Ian

There you go @ferga. This truly is the best place with best support to build apps ;)

Update: We have found and isolated ALL of the warnings / messages generated by Xcode 4.6 when compiling projects. 100% of them are syntax differences that were "allowed before" but "not now." The idea revolves around how method signatures are written. If you're unsure what this means, think of how each method in each class is "described" to the compiler. There are several ways to write a method signature. The method used for several years now is considered a "short cut" and not a "verbose" signature. The Xcode 4.6 compiler is requiring verbose signatures these days. This is actually a good thing (I think). It's a bit inconvenient (for us) to have to re-write hundreds and hundreds of method signatures but it will be better in the long wrong to write them using the verbose syntax. This is what I've been doing for weeks now. Think of things like the code-hints and other compiler features that only work with verbose signatures - it makes sense that Xcode would push everyone (like us and you) into using standard method signatures, and not short-cut signatures like we've been doing. State of affairs: At this point we could update the core files on the download server to prevent these messages BUT doing that would cause all sorts of other issues with literally every plugin. Today, the plugins are also using short-cut signatures, and not verbose signatures. We moved towards updating each .m and .h file in every single plugin. When these updates are completed you'll see the newly available plugins included in the newly updated core project. It never ends...

Only thing I can say is dude you rock! Thanks for everything Dave

@David your coffee machine will get a little more rest now Lol. Good work!

Nice! Appreciate all of the hard work! @David

Much appreciated work David. You're a real legend. You deserve the right to sail away on the shores of California (until Xcode 4.7 is released).

I still get the parse error warnings though...

@Georgious: Did you re-download the source code? Jake

Georgios @david said that the fix has not been released yet until he can go through and fix every plugin. This way when he does release the fix, everything will be fixed togeather. I suspect that it won't be too much longer. Dave

thank you guys...I didn't read well david's post and I thought that everything was ok now... Ok then...We'll just wait. No problem!!! Keep up the good work!