Skip to main content
Participant
May 10, 2022
Question

ACROBAT per iPad non funziona l'interattività dei pulsanti - button interactivity not working

  • May 10, 2022
  • 3 replies
  • 1113 views

Ho creato un PDF interattivo con pulsanti che puntano a segnalibri e URL ma nella versione 22.04.00 per iPad non funzionano. Al tap del pulsante appare un bordo azzurro ma l'azione associata al pulsante non funziona. Il PDF funziona correttamente su Acrobat Pro DC per Desktop.

 

I have created an interactive PDF with buttons pointing to bookmarks and URLs, but in version 22.04.00 for iPad they do not work. A blue border appears when the button is touched but the action associated with the button does not work. The PDF works fine in Acrobat Pro DC for Desktop.

This topic has been closed for replies.

3 replies

Adobe Employee
June 15, 2022

hi Edoardo243875201viq,

Thank you for reporting this issue to us and we're sorry for any inconvenience.

The new release Acrobat Reader 22.05.01 is available now in App Store. Would you please give it a try and let us know if it works for you?

Thank you for your patience.

Participant
June 15, 2022

Derek, I just tried, and it still doesn't work.  I use the Rich Media tool to create buttons at the top of a document whose action navigates to page two of the document (a table of contents).  The button ONLY works in Acrobat DC.  It doesn't work in Acrobat Reader on my iPad, or Apple Preview on either my Mac or my iPad.

Adobe Employee
June 15, 2022

hi Daniel24880799m4yl,

Would you be willing to share with us a file which you experienced the problem for our investigation?

Thank you for your patience.

Participant
May 10, 2022

Will the limitations in the Acrobat Reader mobile application for
interactive PDFs be resolved?


Thanks

--

*Edoardo Pistolato*
Graphic Designer

Studioverde Srl - www.studioverde.it <>


/Ai sensi e per gli effetti dell’art.13 del Regolamento (UE) 2016/679,
tutte le informazioni contenute in questo messaggio, sono destinate
unicamente alle persone/enti in indirizzo, e le informazioni in essa
contenute, incluso ogni allegato, sono di carattere confidenziale e
possono essere legalmente riservate. Sono destinate ad uso esclusivo del
ricevente ed ogni divulgazione, copia, distribuzione o riferimento è
proibito e può essere considerato illegale. Se tale messaggio è stato
ricevuto per errore, il mittente deve esserne prontamente avvisato ed il
messaggio deve essere distrutto, compreso ogni allegato presente.
Per non ricevere più comunicazioni via e-mail o fax da parte di
Studioverde Srl è sufficiente inviare una mail a info@studioverde.it
o un fax al numero specificando
nell'oggetto "Eliminare da liste di distribuzione"./

[Personal info removed by mod]

Harsh Vardhan Pareek
Community Manager
Community Manager
May 10, 2022

Currently, we cannot confirm it but I’m going to pass along your thoughts and needs to our product development team. Thanks again for writing in.

 

Also, we have Adobe wish to form for feature request/bug report: https://www.adobe.com/products/wishform.html

 

Thanks,

Harsh

Harsh Vardhan Pareek
Community Manager
Community Manager
May 10, 2022

Hi @Edoardo243875201viq 

 

Unfortunately, there are certain limitations in the Acrobat Reader mobile app for interactive PDFs. We recommend you to open it in the desktop Acrobat DC application.

 

Thanks,

Harsh

vincentp60706512
Participant
May 11, 2022

Hi @Harsh Vardhan Pareek 

 

Unfortunatly, if it is a limitation in the Acrobat Reader mobile app, it is a new one, because buttons pointing to bookmarks has been working fine with previous versions of the app.

Therefore, it rather looks like a bug or a regression.

 

We already have several clients complaining that their interactive PDFs are not working anymore!

 

Can you please pass the information and escalate so that this critical issue is fixed as quickly as possible?
Thanks.

Participant
June 15, 2022

My pdf button actions worked fine just last month using the same process I've always used, but are not working now on newly created documents.  So it is indeed something on Adobe's end.