Re: Every project reverts to "iOS Device" destination on every open
Re: Every project reverts to "iOS Device" destination on every open
- Subject: Re: Every project reverts to "iOS Device" destination on every open
- From: Alex Zavatone <email@hidden>
- Date: Fri, 02 Nov 2012 15:12:55 -0400
Not trying to evade at all and don't want this to become a he said/she said diatribe.
The main issue that I remembered which resulted in data loss was mentioned with incompatibility between storyboard formats within dot release versions of Xcode.
I'm sorry Joar, but Xcode regularly crashes out from underneath me simply while using the product - on multiple computers - that I have no time to categorize, document, reproduce and report each and every bug.
Each time something like this happens, it pushes us further from our current deliverable and it makes using the product an experience where you must be leery of which actions you take lest you spend yet another night trying to figure out why Xcode lets you apply a distribution certificate to a debug profile yet prevents you from launching the project using that configuration.
Losing support for 10.6.8 is also an unpleasant experience as it forces me into versions of the OS that are less productive for me than 10.6.8.
I wish I had the spare time to jot down each and every issue for reference that has impacted our team related to the Xcode 4.x point releases but I don't.
OH, yes. Upgrading of iOS on a device to 5.1 from 5.0.1 while we were still on Xcode 4.2 resulted in two of our team members in different offices being dead in the water while preparing products for our CIO.
Why? Since we were on 10.6.8 in Xcode 4.2, the updating of the iOS devices from 5.0.1 to 5.1 meant that we simply could no longer build to the devices and there was no way to revert the devices to 5.0.1.
Why was Xcode 4.2 prevented from downloading and using the iOS 5.1 SDK if updating the devices meant we could no longer deploy to them?
We wasted days trying to remedy the situation, upgraded to Lion, used Lion for a while, exported our classes, reinstalled 10.6.8, replaced our devices and rebuilt the project in 4.2 again.
There are two short answers. There are more, but we don't have time. The time wasted with problems related to issues related to updates, point releases and the like is angering considering how much money, time and 24 hour stretches we have pulled as a result of them.
You can only leave the office so many times at 5 AM before starting to hate just how Xcode loves to crash when you perform expected tasks like trying to undo a change.
After a while you get a look of disbelief of "what else is going to happen" and "what do I need to expect will go wrong this time".
If we released our IDE product in this state back when I was doing it, we would simply be fired. This is why I am in disbelief.
So, to answer your question I have 4.5.2 updating on another Mac and I'm spending my time in trying to reproduce the Matt/Tom issue as well as Fons' issue with the command tools not updating.
Then I'm staying late to get the work done that I'm actually being paid to do.
But really, we should not have to be playing the role of QA for Apple with issues like these on released products, especially one as important as Xcode.
- Alex Zavatone
On Nov 2, 2012, at 2:11 PM, Joar Wingfors wrote:
> Alex,
>
> You're evading my question.
>
> You may want to consider what it means to add value to the community represented by this mailing list. Matt provided something very useful, he reported a regression and filed a bug report. What is your contribution in this message thread?
>
> Joar
>
>
> On 2 nov 2012, at 10:54, Alex Zavatone <email@hidden> wrote:
>
>> Well, let's see if my memory serves.
>>
>> Just off the top of my head,
>>
>> Going from 4.2 to either 4.3.x or 4.4.1, simply opening a project in the newer version changed the document formatting version for every storyboard without posting a confirmation dialog so that when reopened under 4.2, each storyboard could not be opened. The only error message was "Storyboard can not be read".
>>
>> I work in a distributed team and when one guy decides to update Xcode on his own and that makes the rest of us unable to open his projects, then we need to take time to jump back in SVN, possibly reinstall an older copy of Xcode and waste time merging to get the project able to opened by the team again.
>>
>> The dropping of support of 10.6.8 as a supported platform after 4.2.
>>
>> And continued reports from people on this list of "I upgraded and this broke".
>>
>> It just seems that while the upgrades offer required functionality and improvements in many areas, there is always something broken that will bite the users that is only discovered after people in the community start complaining about it.
>>
>> Basically, I've spent too many hours over the past few months early in the morning, losing count of how many times Xcode crashed out underneath me that I'm leery of coordinating a team upgrade to the current release, then finding out that something new is broken that will impact our schedule.
>>
>> Yes, I've had to manage release of a large product in the past that people made their living off of and have a slim idea of the complexity of releasing a product as complex as Xcode. However the exact conditions that Matt reported are the issues that are easily caught if someone actually uses the product to produce the simplest of products.
>>
>> If this issue as common as Matt's and Tom's reports indicate then this is a blocking bug.
>>
>> We shouldn't have to be this leery about updating Xcode and Xcode should work more nicely in conditions where team members may be running different versions of Xcode.
>>
>> For all the random crashes and issues like the above in Storyboards, we spent the time to learn storyboards and now are taking the time to throw that all away and move back to doing everything in code where the editor is much more stable.
>>
>> Or maybe it's time to spend the time to learn Jetbrain's AppCode.
>>
>>
>>
>>
>>
>> On Nov 2, 2012, at 12:44 PM, Joar Wingfors wrote:
>>
>>> Alex,
>>>
>>> What concrete issues in Xcode 4.5.2 over 4.5 or 4.5.1 have you run into to warrant this outburst?
>>>
>>> Curious,
>>>
>>> Joar
>>>
>>>
>>> On 2 nov 2012, at 07:32, Alex Zavatone <email@hidden> wrote:
>>>
>>>> I'm sorry, but who is QAing this thing?
>>>>
>>>> Why are we getting releases like this where every time we have another release, there are more new more problems?
>>>>
>>>> Is the Release Engineering team just out of college? Do they exist at all?
>>>>
>>>> Are the managers getting rewarded on every product release, instead of only when a good product with a low bug count is released?
>>>>
>>>> Matt, what are your other serious issues so I know just what will bite our team when we install 4.5.2.1.
>>>>
>>>>
>>>> On Nov 2, 2012, at 10:18 AM, Matt Neuburg wrote:
>>>>
>>>>> Xcode 4.5.2, in addition to not fixing some of the issues I was most concerned with, has introduced a new problem: every time I open a project, it reverts the destination to "iOS Device", even though no device is plugged in and no device has ever been associated with this project. If I switch it to the Simulator and use it, then close it, then open it again, we're back again at "iOS Device". It's maddening.
>>>>>
>>>>> Is there perhaps some hidden default I can tweak to prevent this?
>>>>>
>>>>> m.
>>>>> --
>>>>> matt neuburg, phd = email@hidden, http://www.apeth.net/matt/
>>>>> pantes anthropoi tou eidenai oregontai phusei
>>>>> Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do
>>>>> RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
>>>>> TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Xcode-users mailing list (email@hidden)
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>
>>>>> This email sent to email@hidden
>>>>
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Xcode-users mailing list (email@hidden)
>>>> Help/Unsubscribe/Update your Subscription:
>>>>
>>>> This email sent to email@hidden
>>>
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden