Has anyone out there found a solution to their Acrobat Pro crashing when using it running on the new public beta of MacOS Big Sur?
Has anyone out there found a solution to their Acrobat Pro crashing when using it running on the new public beta of MacOS Big Sur?
As macOS 11 is in Beta, it is not fully supported by Acrobat DC and Acrobat Reader DC. Some workflows for the current version of Adobe Acrobat and Acrobat Reader software may not work as expected on macOS 11.
Adobe engineering team is working with Apple to ensure full support of macOS 11 Big Sur as soon as it is released.
The application doesn't work even in the slightest - as soon as you click anything it crashes. Can you at least share a pre-release build or beta for BigSur users to test -- a partially buggy app is much better than one that doesn't work at all.
Agree. disappointing. I thought I'd try DC Pro as I had some forms to do. I can run on windows, and of course
understand I'm running as a beta, but as a software engineer that's often the way.. so I look to use companies and software where they are more supportive and responsive to change.
That's actually influenced other lifestyle choices, like which bank I use - it will be in part down to how quickly they support betas - really. And that means £££. My own persective is many companies are now realising that they need to adopt more quickly.. this is good.
Sad we don't get any explanation, a workaround, or at least something other than 'no'.
Unlike Apple, Adobe has a controlled and curated beta-testing program. You can apply to it if you wish (https://www.adobeprerelease.com/), but releasing half-baked software "into the wild" for public testing is honestly irresponsible, and I'm glad they're not doing it just because someone else does.
I understand that users based on Big Sur beta version may not expect to have a fully debugged Adobe suite, nevertheless you may seriously reflect on the fact that first Big Sur beta was released two months ago and since then Acrobat DC have permanently stopped working.
In the meanwhile users are regularly paying a monthly fee despite a discontinued service.
There are many other APPS and services that migrated to Big Sur in the meanwhile without major issues.
The fact that Acrobat DC is still crashing a few seconds after it has been launched is totally unacceptable from my standpoint!
Don't forget that the macOS is the Beta software here.
The problem may be with Apple and not Adobe.
You should report the problem via Apple's Beta programme as that is the whole point to them releasing the beta publicly.
You are ranting at the wrong company.
We KNOW "macOS 11 is in Beta" - stating that is not helpful. what would be helpful is WHAT we can do, What YOU are doing - keeping your customers informed should be foremost in your responses, not CYA.
Love the anger.
You are wrong of course.
Beta software clearly states that it should not be used on a production machine.
You only have yourself to blame.
Adobe has no obligation to support the beta version of the macOS.
Don't forget that the problem may be with something in the Apple software — and it may have nothing to do with Adobe.
Next time don't load a BETA on a production machine. It's there for testing — many unexpected things can happen — and that's the whole point. Finding bugs is part of the process and why the BETA software is released ahead of time. Problems. and bugs will be encountered.
The big question is : Why did you install Big Sur?
"This discussion is totally irrelevant, the question was if there is a way around to this crash. The answer is no" Actually, since the discussion started the answer has changed, and for some people the answer seems to be yes. See discussion.
No problem with that.
IMHO, this is a public forum, people come here mainly to find solutions, not to see all kind of appreciations or debates. So, i think every topic should be short and succinct. Of course you might think differently.
I think, some day if you'll be in this situation, looking for a solution to an urgent issue, you'll then understand what i mean.
"I think, some day if you'll be in this situation, looking for a solution to an urgent issue, you'll then understand what i mean." The thing is, looking for Acrobat for a beta system can't be an urgent issue, it's impossible for it to be urgent UNLESS SOMEONE HAS MADE A CATASTROPHICALLY BAD CHOICE. When helping people, it's as well to point out if, behind their question, there is a disastrous choice.
Example: "I tried to clean my car with a sander and it lost the colour. This make of car sucks! What can I do!"
Quick reply: you can get cheap paint for your car from [name of store].
Better reply: you can get cheap paint for your car from [name of store]. You should note that no cars are made to be cleaned with a sander, so this is not a fault with your make of car. If you keep doing this you will keep damaging cars.
You're totally right. However in this case, people using macos beta version, Apple warns all along that users shouldn't use betas for important work. So, i'm not sure your warning is better than Apple's.
Besides, people might have a totally different story. It might not always be due to a CATASTROPHICALLY BAD CHOICE, as you claims. Life isn't that simple. So, i'd strongly suggest you wouln't judge anyone.
The main purpose of the forum is to help people, not to educate them!
This isn't CYA; it's trying to deal with the mass lunacy of people installing betas then complaining that other things don't work, and trying to beat us down by saying they have important work to do. Just lunacy. I hear, by the way, that Apple fixed whatever was wrong, and Acrobat might work again in the latest beta.
Gaining access to a beta version of any application, especially an OS, used to be a complicated and exclusive process, reserved mostly for people in the know, often with extensive programming or UI-design experience. I still remember getting a beta version of Windows (2000?) in the (snail) mail and what a big deal it was... It seems that now beta-testing is considered just another "early-adopters" trend that any layman can gain access to it. This is not good, of course, as it leads to such issues we've been seeing reported here during the last couple of weeks, where people complain that their production machines are not working properly (often failing to mention they're running an unstable OS version). I wish Apple will knock it off, but I guess I'm being optimistic...
try67 — That's it exactly.
I have no idea what benefit Apple get out of releasing a public Beta.
All they get is a bunch of people complaining (in most cases quite angrily - guess that the way of the social media world - no civility) — I wonder if any of them bother to report a bug.
The only thing I see is misdirected anger at the wrong company (in this case Adobe).
I've never bothered trying to Beta test a macOS — in fact (as I'm sure we are all aware) installing a release version is dodgy for the first few months. Maybe Apple should put up a bigger and bolder message asking for constructive feedback with a massive disclaimer about installing it on a production machine — something that requires a signature that the person understands the risks. Clearly the small print doesn't get through.
I think you are totally missing the point.
I am a professional as many of the other Acrobat users logged at this community, not a jerk or a hacker or so. I am fully aware of the consequences of installing a beta version.
Nevertheless you have to take in account that beta versions are not an exclusive of developers or specialist since long time. They are available to early adopters, hence normal users with a attitude to experiment new user experiences.
The vast majority of the software developers have clearly understood the potential of this user segment to debug early releases of their software. These companies align their release plan with the OS. They play the same game as Apple does to provide a mature official release.
these applications are not 100% functional, but they ensure users will still preserve their experience within latest OS release.
In this case it seems like Adobe is coming from the other side of the universe, ignoring all this trends and pretending not to give a minimum explanation about their software not matching latest OS. There is no beta version available for Acrobat users and official version is regularly crashing a few seconds after the launch.
Nevertheless it's either to say that Adobe monthly fee is coming on a regular basis despite this software is not compliant with the latest OS.
Ignoring this scenario is the worst decision this respectful company could do.
I do not agree with your point of considering this space only for short technical comments.
I use Acrobat many times a day and this is crashing since months without having a minimum support or explanation from Adobe side. Is it a fault of Apple? I don't know. How do you know? They keep their line "don't use beta versions" while the reality is a totally different one.
I am really concerned. Big money, no support.
PTLM — unfortunately (and I'll say this as nicely as possible) you are missing the point.
A macOS in beta releases is not for early adopters. It's for testing and finding problems.
The Acrobat problem was an Apple problem (as far as I can tell and it is seemingly now resolved).
I can't speak for Adobe, but I would think they are busy on many aspects of their software - new features, etc.
As well as supporting macOS and Windows. I'm sure they do run their software on both platforms and test it thoroughly, while at the same time solving possible problems (while chatting to Apple and MS).
Installing a beta release of any software by any company is for non-production machines only (this is clearly stated over-and-over). And the reason is not to give you the chance to be an early adopter — it's so they can get feedback on bugs. They are using you to do their testing and to make comments. Big Sur has not been released (and that's an important fact - no matter how you spin it).
You seem to be giving Adobe time limits to fix bugs that don't feature in a stable OS — how do you know they aren't working on things and just haven't managed to find the problem yet?
The latest release of macOS is Catalina. Acrobat works with that.
When Big Sur is publicly released you would do well to check the software notes that Adobe publish as there may be problems.
In my mind, if you are working in a production environment, you should wait a month or two before installing any major OS update. To do it any earlier is not being an early adopter — it's just being silly — you are looking for trouble. I love having new features — but not at the expense of my working ability. Catalina was so buggy it took me more than 6 months before I installed (I kept checking back to see if those that were critical to my workflow had been fixed).
Why did you install OS 11?
Was there a specific reason — I'm curious?
Why compromise your work for a new look and feel (unless there was some actual software feature you couldn't do without of course)?
On behalf of Adobe Acrobat Engineering …
No one is calling you “a jerk or a hacker.” On the other hand, neither MacOS nor Windows beta / developer releases are meant for “early adopters.” That is certainly not a message even hinted at by either Apple or Microsoft.
Regrettably, the landscape for computer operating system development has dramatically changed over the years. Many years ago, when I personally managed an operating system development group, the most important cardinal rule was that anything we changed or augmented in the operating system could not do anything to prevent existing applications from properly running as they did under previous operating system versions. That rule was very strictly enforced. And operating system vendors worked closely with application developers to ascertain that such compatibility was maintained before any so-called beta or preview releases were provided to anyone in the general public. That is obviously not the case today. Specifically in the case of MacOS 11, Apple should not be releasing “public beta” OS versions for which there are quite a few major compatibilty bugs in the operating system itself.
To be very clear, Adobe in general and the Acrobat engineering group in particular has been thoroughly and continuously testing our products with builds of MacOS 10.16 since the first private developer releases were made available to us.
Even this far along in the process, there are a good number of MacOS bugs affecting Acrobat and other Adobe applications that remain to be fixed by Apple. (I've seen the list with Apple bug numbers on same … and it is sizable!) We are in continuous communication with Apple over these issues and progress being made to address them. There is nothing that Adobe can do to fix these operating system / application incompatibility issues ourselves beyond reporting the issues to Apple, discussing same with Apple, and testing fixes from Apple in the next MacOS build (most such builds are not sent to the public). And as has been reported by others in this thread, some of the problems have been resolved in subsequent MacOS 11 beta releases.
The bottom line is that it is your personal choice to use operating system beta / developer releases in a production environment. But since these OS versions are not blessed for compatibility by the operating system developer much as less the application developer, you are in uncharted waters and should not expect and certainly not demand support from the application software developer (whether Adobe, Microsoft, or other application developers).