There was a RAISE without a handler // CFURLCopyResourcePropertyForKey // MACOS 10.15.2

Forum|Forum|6 years ago
November 13, 2019
2 replies
1160 views

I was asking about this --

+ Acrobat Pro DC comes up with this error message and then crashes:

++ There was a RAISE without a handler

+ It is perhaps likely, that

++ MACOS expects “something” before “//“

++ for instance : “file://”

++ so that the line would look more like this : “var filePath = "file://(fileURLpath)"”

I have NOT found the MACOS file to correct -- I am not that driven an expert

Mich

This topic has been closed for replies.

Correct answer AnandSri

Hi MichaelMix,

We're sorry for the trouble you had, as correctly suggested by @ls_rbls, Adobe Acrobat and Reader official update 19.021.20056 Optional update, November 13, 2019 containing the fix for this issue is now available.

This update will be automatically pushed to all existing installations of Acrobat and Reader. If you want, you may also manually trigger the update by opening the application and going to the help menu > select check for updates.

Reboot the machine after updating Acrobat.

More information about this release is here: Release notes

Please let us know if you experience any issues.

Thanks,

Anand Sri.

AnandSri

Correct answer

Community Manager

Hi MichaelMix,

We're sorry for the trouble you had, as correctly suggested by @ls_rbls, Adobe Acrobat and Reader official update 19.021.20056 Optional update, November 13, 2019 containing the fix for this issue is now available.

This update will be automatically pushed to all existing installations of Acrobat and Reader. If you want, you may also manually trigger the update by opening the application and going to the help menu > select check for updates.

Reboot the machine after updating Acrobat.

More information about this release is here: Release notes

Please let us know if you experience any issues.

Thanks,

Anand Sri.

MimaginableAuthor

Participating Frequently

Hi Anand Sri,

Thanks for your post -- it was fortunate that the update was here -- the issue is solved -- I-m sure others will have benefitted -- thank you for this forum -- it is a really strong strong and uniqe forum -- because not only users -- however skilled -- but also reps from Adobe are here --

Mich