how did you install 10.7.3? with the method mentioned (cmd+r on boot) i can only install the 10.7.4 and also the apple support told me that there is no possibilty to install 10.7.3 ... *confused*
I understand your confusion Berny. The only thing I can think of right now is that the retina doesn't work with 10.7.3. I used the same install method and got 10.7.3 installed. The more reason for Apple and Adobe to find a solution (very) soon. Something is going terribly wrong here.
When I re-installed Lion using cmnd+r, it set me up with 10.7.3...I think when you install that software update 1.0 for macbook pro, it THEN updates to 10.7.4?...I am running new Macbook pro 15" mid 2012 (non retina). So not sure why Apple said its not possible, cuz here is screen shot of what IS possible
Thank you for your reply. There seems to be a difference between mb pro and mb pro Retina.
If you reinstall Lion on mb pro Retina (cmd+r) you can only Install osx 10.7.4
So my conclusion is: its Not the Mid Summer update(you also get the Update in 10.7.4 via recommended Updates). It is the osx 10.7.4 which cause the problems!!!
@adobe: pls fix this Bug. Our customer List is getting longer & longer with everyday!
And we cant work! We bought a Lot of New mb And they are useless...
Its only it garbage :@
I spent > 3 hours on Adobe phone support (on my dime) until they said they will need to escalate and call me back within an hour (asked for my number). 4 days later and nobody called. This is unacceptable. Adobe, I spent a fortune on InDesign and it is not working. What's going on?
Same issue here. New MacBook Air 13", a few weeks old with 10.7.4. Crashing immediately whenever I export to PDF. Very upsetting!
FYI - I have an outstanding case with Adobe regarding InDesign crashing anytime a warning message is presented by the application. I've had it happen numerous way (PDF export, Packing, Page Deletion). In all cases a blank warning message pops up very briefly and then the application crashes. The solution I've found is to find a work around in each instance that would not trigger the warning message. If I can avoid the warning messages I've had no crashes.
My case has been elevated to the 2nd level of engineers and I spoke to one directly about this. They acknolwedge and know about the issue and say that they believe it is specifically realted to OS 10.7.4 and it only occurs when it's being run on new hardware that was recently released (I'm a new 2012 MacBook Air).
Happening to me,too, trying to boot Indesign (CS5.5) for very first time on brand new retina pro. Can't get it to open or run it at all. Not good at all. What now, Adobe?????????????????????????? Should I return the retina MBP and just gp back to the unibody, where at least i was able to do some work??!
Not working here either. new 2012 macbook air. Tried the fix mentioned and the recovery partition (cmd + r) installed 10.7.4 it did say that is was downloading components so I guess its always going to download the most resent one and install that. which is kind of irritating. haven't installed any of the updates and it still crashes when I try to export a PDF.
Would be nice to have some info from adobe on this. how long is it going to take to fix. Do I have to go back to CS4 on a 7 year old macbook? Because this small bug renders indesign useless!
When I rebooted using cmd + r , it didnt install 10.7.4 for me and left me with 10.7.3. I still havent updated to the 10.7.4 macbook pro 1.0 software update...and am able to actually use this mac and software for what it's supposed to do and not be stuck with a $2000 paper weight! although, I feel like Im not getting best video performance without the video update...but have to outweigh the benefits I guess til something is fixed...
Weird that it doesnt work the same for you? Sorry!
Not your fualt. I have no idea how to install 10.7.3. I can't remember what version it came installed with.
I didnt install the update and I find my Macbook air is running a lot hotter. I dont think the 1.0 update is the issue as I am still getting the same problem. So it must be an issue with 10.7.4. Just imagine the fun when 10.8 is released.
I don't think 10.7.4. is the problem but the update for the new macbook pro's. My new Macbook Pro is running 10.7.3. right now and all works fine. My (very much) older Macbook is running 10.7.4 and all works fine there too. Suppose the problem really lies in the new MacBook Pro's and the 1.0 update which comes with 10.7.4. Just hope 10.8 is ok.
I have one of the new Mid 2012 MacBook Pros. I to am having this crashing issue, but only on my two new macbook pros. However my other older lion (pre update 1.0) and older are not having any issues. So when could we expect a patch to fix this issue.
Less than a week ago i bought a Macbook Air installed with Lion 10.7.4. InDesign CS5 crashes whenever a Warning box is activated - this can as other folks have described: when deleting a page with contents; when ungouping objects that have an effect applied; when updating a table of contents, or when relinking to an image that has been updated; (NOT, however, when exporting to a PDF, this seems to work fine, ironically).
I followed the instructions to reboot holding down the Command + R, and i was not given any options to NOT update to 10.7.4. So basically i have the same Lion version as before. I'm assuming that this is because my Air is so new? I really have no idea.
Are there any other suggestions about what to try to fix this, or is there any work from the engineers about a permanet fix?
Mine is also with the brand new Air with 10.7.4. I removed all errors in preflight and seem to be able to export to IDML, EPS, and print PDF but crashes immediately when exporting interactive PDF, so maybe there's a warning box specific to that export. But I do briefly see a warning box pop up before getting the Indesign crash notification.
I am using MBP with Retina display and I have same issues as well (fail on exporting, packaging, printing.) I do have them figure out about not crash while deleting spreads but that's a miner thing compare with those 3 big issues. I bought this computer for my final class but now I can't use and have to use my 5 years old computer for it. I can't believe they haven't have this figured out yet, grr!
Question for Adobe: Is there any way to temporarily disable all warning dialog boxes to prevent crashing?
I know this is not a good long-term solution, but i have to get some work done, and this issue is making it impossible.
What the heck is going on Adobe? I cannot use InDesign on my new MacBookAir, therefore I cannot on client stuff when on the way. I have the same issues as the others here! Please, how can I disable the warning dialogs?
This behavior caused by the update is being investigated by our engineers.
At this time it appears the update is removing an API we use to control our use of system icons. At present the solution appears to be to rollback the update for the software to continue to function as expected.
Other solutions are being explored to see if we can find a simpler answer.
Thank you for your response. Since my MacBook Air is less than a week old, I was unable to roll back the update, and that doesn't appear to be an available option for me. If you have ANY other suggestions about what i can try, i welcome them.
I cant rollback as well. It causes a lot of other problems, and because of this bug in the first place I am supremely behind at work. Having to work on this machine and then drag and drop to PDF on the old.
Adobe and Apple really must get this resolved and soon.
My MBP Retina is also only a week old and I have absolutely ZERO functionality. InDesign 5.5 crashes on start up each and every time and I am losing valuable work time every day. Scott,I appreciate your response (any response shows us that someone is listening, working on it), but like kevino2, I can't rollback the update. I am also a bit nonplussed that I stood in the Apple store and chatted with the business rep about buying the retina for my design business and NO ONE mentioned this issue!
Please keep the midnight oil buring on this, Scott.
Will this be a problem once Mountain Lion is released? Or will there be more issues?
At this time I cannot tell if it will persist in Mountain Lion. The APIs apparent removal really impacts the behavior in this situation.
We're taking this issue very seriously, I wish we had more to share at this time but I'll be sure to share what comes down the line from the engineers relating to solutions or any workarounds they can find.
I saw on a Mountain Lion developers thread that they were getting all the same crashes. That is how I learned about holding down the Option key to prevent some of the crashing. The option key does not prevent crashing when exporting to a PDF. So to answer your question, yes this is happening on current OS, and on the developer's testing Mountain Lion. This is an alarming problem that frankly I can not believe Adobe is not more concerned about.
FYI, there is no way someone at the Apple store would even know about this. They do not troubleshoot other company's software. Adobe and Apple hate each other, so when you bought your computer there was no way an Apple store employee could advise you about this problem. Honestly, Apple store employees are worthless. User forums is the best place to go to research issues with new hardware and software before purchasing.
This is Adobe's bug to fix. If that means sucking it up and talking to Apple developers so be it, but designers are both companies original tribe. You lose our respect and you have problems. Telling us to rollback is not a solution.
Release an update with a fix. End of story.
Do you ever test your apps against new OS updates? How can it have such an impact without being noticed?
TBH: I first thought that somethings wrong with my new machine, just to discover that it's a bug in your software. That's really annoying…
Keep the midnight oil burning!
I think the last tow posts are rather misinformed and quite unfair. I'd guess you've never been involved in programming or software development. API stands for Application Programming Interface (http://en.wikipedia.org/wiki/Application_programming_interface) and in this case the code is apparently provided by Apple -- they do that so developers can write software that will tun on their operating system -- and was removed by them without providing an alternative or a warning. It's not at all unreasonable for Adobe, or anyone else writing software to run on OS X to rely on Apple's published specifications at the time development is undertaken. If you want to be angry with someone pont your thoughts toward the gods in Cuptertino.
To imply that Adobe doesn't care is ludicrous. Waht do you think is prompting Scott to post here? A bug fix is not an instant process. First the problem needs to be reliably reproduced and the true cause(s) identified. That can take days or weeks, or may never happen. You're fortunate the cause seems to be known now, which says to me somebody has been working VERY HARD to identify it so fast. Once that casue is known, strategies for solving the problem must be formulated and TESTED before being released in an update. Would you be happy if this crash were fixed and something else got broken by the fix? I doubt it.
You make a point and maybe it is not fair to point fingers, but I am a design professional not a developer. I dont want to know what API stands for. I pay $700 for the software so I dont have to. I am thrilled to see your comment because finally after 66 comments I see a sense of concern by Adobe. We are all concerned because this probelm is costing us all a ton of time and money.
All I know is that these two companies have a long history of not getting along or communicating. Both would not be where they are today if it were not for the creative community using and influencing others to use their products and hardware. Both companies have plenty of money and resources to fix this problem. For a software package that cost over $700 and a laptop that cost more than $1500 this should not even have happened in the first place. What happens is the creative community who has stood by both companies (for two decades in my instance) do not deserve to have their business suffer due to lack of communication and testing before releasing. I really dont care who is to blame. It is ridiculous that it happened. This is not some small app in the App Store. It is a very expensive piece of software used around the world, and the world is not fair. Your name is on the product, so fix it.
You have to remember that each version of ID takes AT LEAST a year to develop and tesr before it sees public release (and that testing can only occur on systems that are actually in existence at that time) . It certainly looks to me, from what has been posted here, as if the problems did not appear until quite recently. I'm not sure what version of ID you have, but the thread started with a reference to CS5, which was released over two years ago. CS6 was released in May. How reasonable, whether you want to understand the underlying technical issues or not, is it to expect old software to run on a newly altered OS that was released after? That's like saying your gasoline powered automobile should run on solar power, and that the manufacturer should have had the foresight to have a conversion kit ready to give you, for free, the day the oil companies closed all the filling stations without warning.
I can not even address you analogy as it is absurd.
hi peter, i only want to let you know:
i tested id on a mac book pro retina with osx 10.7.4 with following versions:
the crash is infected by the described pop up...
please dont use "you are using an old version" as an excuse!!! because also cs6 crashes!!!!!!
i just checked the spec info from id: there is no warning that the software doesnt work with mac os x 10.7.4 . thats ridiculous!!!
and who is paying my loss of profit?
a new mb pro retina: $3.000 + cs6 master: $2.600
5 employes: $ 28.000 and you cant do the work for you customer.
im very very very upset!
And, I might add, it is not the way to win friends and influence people, Peter.
We are frustrated, we are making clients who pay us unhappy, and we have absolutely no recourse. None. And beyond that, we just look and sound dumb when we have to tell clients it's a computer or software issue. that is very 1995. Adobe is making us look bad, feel stupid, and lose money. They should be falling all over themselves with apologies to this important, core customer group (as well as fixing the issue).
I have to agree with the concerns above. Adobe needs to escalate this internally at the highest level.
I'm surprised this hasn't showed up in wider forums yet. Imagine this on Techcrunch: "Adobe suite crashes on latest Apple gear"
Adobe (and Apple) please do something.
I would agree with you 100% if it were Adobe's fault here, but it isn't. And I don't know waht you consider faling all over oneself, but Adobe seems to be doing everything they can to find a fix as fast as they can.
And I don't work for Adobe, I'm an independent designer with clients, just like the rest of you, so I have no stake in defending anyone. I know you are all frustrated, but it's the poeple at Apple who deserve your wrath.
If CS4 and earliier work, it would indicate to me that some new feature added in CS5 calls the API that was removed, and that particular piece of code was not used in the earlier versions. That does not make it a bug or design error.
@ izmalakof, I suppose you're right about the analogy. It would be closer to owning a car that runs on diesel, only to have the supply of deisel fuel pulled from the market.
Your assumption that I blame Apple less is wrong. I blame them just as much. A community we are hostage to both companies.
Perhaps this is a better analogy for designers to describe what's happened:
Your client asks you to design a full page ad for a large magazine, so you go the magazine website and download the specifications. You make the ad to those specs, and the client approves it. So far no problems, right.
The magzine, in an effort to cut costs, decided to change page size. Unfortunately, they neglected to put that information on the website or update the specs for the current issue, and because you are not a mind reader you continued to rely onthe published specification. Your ad turns out to be useless, your client blames you for not knowing. Is that fair? Now put Apple in the place of the Magazine, Adobe as the designer, and you as the client, and you'll understand where the anger should really be directed.
Would this happen with a real magazine? Probably not, but then real magazines depend on keeping their advertisers happy. Apple, on the other hand, is much more interested in selling iPads, phones, and apps than they are in the graphics market, and they have a reputation for pulling this kind of thing.
I know none of what I'm saying is likely to change anyone's mind, but I think you should try seeing the situation for what it really is.
Peter, do you have more information that what Adobe has shared? If not, perhaps you shouldn't be insulting us repeatedly (assuming we cannot "see the situation for what it really is").
Because the only thing I've seen from Adobe is the earlier statement:
"At this time it appears the update is removing an API we use to control our use of system icons."
That's not definitive. It could be something else, something entirely Adobe's fault. Or, it could be that Apple did announce removal of the API, but Adobe's programmers failed to appreciate the damage that would do.
rMacBook Pros just got into people's hands in the last week or so; this is an emerging situation. It seems to me that it's far too early to blame (or defend) Adobe or Apple. But the point remains, it is Adobe's software that is crippled, and it is up to Adobe to fix it. End of story.
I find it amusing (but sad) that the only "rollback" that will fix this problem for me is to go back to the CS4 version. (Will it be able to read CS5 files? Heck, will it even install?)
As I recall, no, CS4 will not be able to read CS5 unless they were saved as exchange files, and it will never be able to read CS 5.5 files. So, not much of a work-around.
I would not like to get involved with all the arguing.. but just as an FYI
to anyone thinking that CS4 might work...
Unfortunately for me... CS4 doesn't work with the new MacBook Pro 13" with
I am able to export PDFs "most" of the time, but I cannot change print/page
settings... making it impossible for me to do any print jobs at home (using
Hopeful that Adobe can fix it soon .
I'm sorry you feel insulted. That was not my intent. My intent was to point out that anger and ranting directed toward Adobe is misplaced. I know that doesn't get your work done.
As far as inside information, no, I don't know anything for sure beyond what Scott has posted, but I know the ID team, and they don't take this stuff lightly, at all, and if after three weeks of work they say "it appears" to be a problem with a removed api, I'd lay odds that they've ammased a good bit of evidence to point in that direction and there is near-zero probablilty that, except in some isolated special cases which might also be showing the same symptoms, there is any other cause. I would say from past experience that the time frame from finding the source of the problem to designing a fix, and then testing that so it can be released is a few weeks.
I mention the special cases because it is possible that some docments might have other issues that look like they are the same, but are in fact something else. This happened with PDF export problems in CS5. Most issues were fixed with the patch intended to correct the problems, but we still see a small number of reports of failure that look the same. It often turns out that there is some internal problem in these files -- bad link or font, for example, which can be corrected, but I would be lying if I said I didn't belive there are still possible bugs. Adobe is pretty up-front about admitting when they've screwed up the code themselves, and when a bug is as serious as this they put a lot of effort into fixing it. They care about their customers quite a bit, actually, and InDesign is a core product, not some sideline.
Most bug fixes don't get ported back to versions before the current release becasue the cost to test on non-current versions is too high and the risk of breaking something else on an older version is too great to warrant it if an upgrade will solve the problem (I know, that's money out of your pocket, but that's corporate reality). I don't know, but I wouldn't be surprised if an exception to that norm happens in this case and that if they can port a fix back to CS5 and 5.5 they will, but it's hardly guaranteed.
Adobe is always looking for beta testers. I would encourage anyone who thinks they can help to find bugs before a product goes public to apply to the prerelease program: https://www.adobe.com/cfusion/mmform/index.cfm?name=prerelease_interest