xfa.host.response - XFA forms problem after update of Reader DC from 13.8.2019

[Michal_Hraba]

We have problem with our xfa forms after update of Adobe Acrobat Reader DC from 13.8.2019.

Now, javaScript method xfa.host.response returns always null.

Example:

var lAns=xfa.host.response("Number?","","1");

app.alert(lAns);  // Always shows null

Can we expect solving of this bug soon?

[AnandSri]

Hello MichalHraba,

We're sorry for the trouble you had after the latest release, would you mind sharing more details so that we can investigate further?

What is the current version of Adobe Reader DC installed? To identify, please take help from the article Identify the product and its version for Acrobat and Reader DC

What is the OS version?

What happens when you turn off the enhanced security in Adobe Reader's preferences? Edit>Preferences>Security(Enhanced)>tunr off Protected Mode at startup and Enhanced Security>Click OK>restart the application and check.

Note: Disabling the Protected mode and Enhanced security is only for testing purpose, please enable it back.

Toggle the JavaScript settings in Edit>Preferences>JavaScript and check.

Let us know how it goes and share your observation.

Thanks,

Anand Sri.

[Michal_Hraba]

Hi Anand Sri,

OS is Windows 7 SP1 Profi Czech. I can test in other versions of Windows later.

Versions of Adobe Acrobat Reader with this bug: 19.012.20036, 15.006.30499, 17.011.30144.

Tested versions of Adobe Acrobat Reader without this bug: 17.011.30127, 15.006.30482

Turn off the enhanced security doesn't solve the problem.

[Michal_Hraba]

Hi Anand Sri,

I did more tests. I tested on Windows 7 Pro SP1 Czech, Windows 10 Pro 1809 Czech, Windows 10 Pro 1903  English. Result is: Version of Windows have no influence.

Tested versions of Reader:

  19.012.20036 – bug

  15.006.30499 – bug

  17.011.30144 – bug

  19.012.20035 – ok

  15.006.30482 – ok

  17.011.30127 – ok

  17.011.30143 – ok

Adobe Acrobat Pro 2017, 2017.011.30144 – bug

Turn off the enhanced security doesn't solve the problem.

Workaround: Call of method xfa.host.response replace with call of method app.response.

Thanks,

Michal

[gauravs43202023]

Hello Michal,

Thanks for reporting the issue.

Issue is reproducible at our end.

Has forwarded it to our engineering team.

Sorry for the inconvenience.

[EdGioja]

Has this been corrected yet? It is going to be a big problem for us.

[gauravs43202023]

Yes this issue has been resolved with our release on Aug22, 2019.

Please update to latest build(if not done yet).

Please let us know if you still experience any issues.

Regards,

Gaurav