Re: 2 itunesconnect questions
Re: 2 itunesconnect questions
- Subject: Re: 2 itunesconnect questions
- From: April <email@hidden>
- Date: Fri, 11 Nov 2011 22:50:26 -0700
On Nov 11, 2011, at 7:14 PM, Conrad Shultz wrote:
> On 11/11/11 4:59 PM, April wrote:
>> Years ago I used my real name. I was very new to cocoa (this is like
>> 2002) and asked some dumb questions. I got flamed to death.
>
> Greetings, April. I regret that you were mistreated in the past; I am
> confident that will not occur now.
>
> Anyhow, did you get a chance to try the couple suggestions I tossed out
> in previous messages?
>
> I remain a little hazy on how your project got into this state. I
> understand that you manually set build architectures, but vis-a-vis
> creating a universal app, did you:
>
Actually I had a long existing project that I start working on in 4.1 before the release and then 4.2 when I started icloud support up until now. I've hit multiple delays and setbacks due to adding features out of fear of 1 star ratings due to "It's useless cause I cant..." Even though many of the features are simply moronic on a touch platform. For instance the ability to draw freehand on an iphone in an app for serious use.
Anyway.... all I did when I started working in xcode 4.2 was set the base sdk to 5.0. I never changed the deployment target away from actually, 3.2. Later I implemented ARC but only changed the deployment target to 4.2. And this project was originally poorly implemented in that there were 2 separate projects, 1 for iPad, 1 for iPhone/iPod. So I brought all of the code under one roof and used a simple ISIPAD definition (a macro for the interfaceidiom check) to figure out what should do what. not that that matters.
Anyway. In xcode 4.1 the arch had been armv6/armv7 and I never really bothered to look at it again after installing the final xcode 4.2. I built and ran.. according to the bundle version script's last incrementation at release 2673 times over a 5 month period. Installed at least a dozen or more adhoc builds via itunes to check some built for release things. never got an actual error... though I was ignoring warnings in the build window. Won't do that again. so last night I was surprised. Like I said stack overflow had an answer, but since starting this thread I now understand the problem, thanks both to you and others. Had I changed the build target to 4.3 I'd have never seen the error. But because I was trying to maintain some degree of backward compatibility I got the error. I did manage to get it submitted with armv6/armv7 compatibility. version 3.1 may not support armv6. I'm still contemplating that. mostly I hate the "What about us" support emails. The ones I got a few hundred of when I updated a mac app to intel only, app store only.
So I guess, technically if you can consider it converting rather than uh... Conforming it to xcode 4.2's available settings until it built, I manually converted it. This is embarrassing to admit, but at the time I was so wrapped up in getting this app working, chasing bugs and trying to have it submittable by the GM seed (which I missed by a damn site.. thanks useless assembly language class I will never use in life.) that I didn't really give much thought to reading the "switching to" docs.
> a) Start a new Xcode project, configured to be universal; or
> b) Convert an existing project using the universal conversion feature; or
> c) Convert an existing project by hand?
>
> I ask because I remember something in the docs about how the
> migration/conversion feature does more than just change the target
> platform and add a couple nibs, and that we shouldn't try to convert
> projects manually. If this is what you attempted then it seems possible
> that there are other magic flags that need configuration.
>
> Also, since this topic now seems to be well within the tools domain, you
> might get good feedback on the xcode-users list as well.
>
Well with the app submitted and my motivation to learn cocos2d low... Thats a long story that for the first time in 10 years has me seriously considering trying to sell a project rather than complete it. Anyway, I suppose it's time to catch up on the 4.2 docs and "switching to" notes etc. I have 4 apps, two on the store, two in development, that need updating/completion. Plus the app this thread relates too already has a full plan for 3.1 laid out as well as around 500 lines of commented code. (Things I skipped in order to get it out the door.) It would be nice to not have to ask another dumb question each time I start work on one of these.
Besides, even with months of 8+ hour days deep in the code, I just know that the complete failure of iBetatest.com to produce anything useful, means I've missed something somewhere in my testing and that of the 1 person that ever ran the app when I asked them to, and I am going to have to fix a crash that never happened in all that time. After all, those apple people could find a bug in 'hello world.'
> --
> Conrad Shultz
>
> Synthetiq Solutions
> www.synthetiqsolutions.com
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden