Brian Garcia Posted March 10, 2021 Report Share Posted March 10, 2021 I'm having the same issue for one of my end users with Nitro Pro 12. Your fix resolves the issue in version 13 but not version 12. Are people on version 12 out of luck? Do we need to pay to update our software to resolve this issue or is Nitro Pro still working to resolve the issue? I see more people reporting the issue and no responses from Nitro Pro in over a month. 1 Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now