What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 134 Stack Exchange communities.

This question was closed as "too localized": Xcode expired certificate problem

Someone is asking for a workaround for a known bug in Xcode that still hasn't been fixed more than 12 months later and it is affecting thousands of people (as far as I can tell).

The bug makes it impossible to compile your code, and the only official fix is a complete hard drive erase/operating system re-install every 12 months or so.

The accepted answer is basically saying "yes, it's a bug. wait for it to be fixed". There is also a comment with a link to a third party site with an actual workaround for the bug.

I really want to post the full answer incase that third party blog goes offline, but I can't because it has been closed as "too localized".

Based on the workaround, I suspect this bug occurs for every single iOS developer who doesn't do a full system re-install once a year. It is anything but "too localized".

share|improve this question

closed as too localized by kiamlaluno, yhw42, Lorem Ipsum, Toon Krijthe, Martijn Pieters Sep 25 '12 at 9:32

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

3  
I've re-open this for you. –  The Anti-Santa Sep 25 '12 at 0:11

1 Answer 1

up vote 4 down vote accepted

Considering that the issue has been reported on March 2011, and the bug has not been yet fixed, I would not say the question is too localized. There is a workaround, and that makes the question perfectly acceptable. The fact the problem is present for any developer whose certificate is expired is another point to consider when considering the question too localized.

I guess that the fact the accepted (and only) answer essentially confirms it is a bug (and suggests to wait for the bug to be fixed) didn't help; add also that, in almost one year and a half, nobody has been able to write an answer with a workaround.

I can understand why the question has been closed: Knowing that the behavior I am noticing is a bug in the application I am using is not probably much helpful, if nobody can report a work-around for it. Now that the work-around is described in an answer, the question is more acceptable, IMO.

share|improve this answer
    
Understandable, but still wrong. –  Shogging through the snow Sep 25 '12 at 0:38
    
Yeah, I agree it could make sense to close it based on the details in the question. But as someone who has wasted about $5,000 in contract-billable time trying to find a workaround for this bug, and finding many other people who have the same issue and don't know the answer... I feel it is worth upgrading a one line comment to a full answer. –  Abhi Beckert Sep 25 '12 at 0:39
    
@AbhiBeckert I agree. I am sure there are many developers for which that information is very useful. –  kiamlaluno Sep 25 '12 at 0:45
    
Only problem is the workaround really isn't described in the answer. It's really just a link. If someone could edit and include the workaround in the actual answer, then I think there'd be a stronger case; however, at this time, I see a lot of link only answers, especially the two already deleted by the moderators. –  jmort253 Sep 25 '12 at 4:32
    
@jmort253 The answer written by Abhi Beckert is not merely a link. –  kiamlaluno Sep 25 '12 at 7:31
    
@kiamlaluno - Okay, one out of four. :) Takes a disciplined user to write a good answer on a NC, NARQ, Too Localized question. Not all are that disciplined, even some 10 and 20Kers. –  jmort253 Sep 25 '12 at 15:06

Not the answer you're looking for? Browse other questions tagged .