Skip to content
← Share your feedback on Acrobat DC

Settings and activity

1 result found

  1. Adobe Licensing Application hangs after login on Mac OS 10.15.2 (Catalina)

    28 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    45 comments  ·  Acrobat for Windows and Mac » Installation and Licensing  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Jeff in GA commented  · 

    Ansh, what triggered the problem (the loss of privileges) was doing a migration from one Mac to another. All the other programs made it except Pro Acrobat. I even tried deleting every trace of Acrobat, but nothing worked except a Root authorization. So the Adobe install glitch may only relate to migrations.

    An error occurred while saving the comment
    Jeff in GA commented  · 

    Ansh, thank you for the reply. I tried all of that, and it didn't work. The solution: I had to create a "root user" account, then log out, log back in as "root" and finish the installation (i.e., license application) from there. I think that's the only way around the glitch in Adobe's install.

    An error occurred while saving the comment
    Jeff in GA commented  · 

    ****UPDATE****
    In order to get around Adobe's installation glitch, I had to create a "root user" account, then log out, log back in as "root" and finish the installation (i.e., license application) from there. Then you can log out and return to your normal user account. Instructions: https://support.apple.com/en-us/HT204012

    ORIGINAL POST...
    After migrating from one Mac to another Mac, Acrobat "pro" 2017 doesn't work (but all of my other apps do work). I have uninstalled and reinstalled it multiple times and always get the blank "Acrobat Licensing Application" screen. I tried the instructions from Ansh below (cut & pasted the command line into Terminal) but that didn't do anything either other than spawn another blank screen. IS ADOBE GOING TO FIX THIS PROBLEM?

    BTW, the response to Ansh's command line is: "Class oobelibclass_CS7_7 is implemented in both /Library/Application Support/Adobe/Acrobat 2017 Helper Frameworks/OOBE/adobe_prtk_lib.dylib (0x1110a7728) and /Library/Application Support/Adobe/Acrobat 2017 Helper Frameworks/adobe_oobelib/acrolic/adobe_oobelib.dylib (0x1113fcab8). One of the two will be used. Which one is undefined."

    Jeff in GA supported this idea  ·