Repeated error in console in relation to registering callbacks for GET_FEATURE_FLAG

[Patrick25290128fzhl]

There appears to be an error in the source code for the pdf embed API.

Even on the view sdk demo you can see in the console lots of errors:  https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf

Uncaught (in promise) Error: No callback registered by viewer for GET_FEATURE_FLAG:

It then logs errors for the different options.

[Benjamin281283092hgu]

Same issue. And my customizations (comments pane open on load, for instance) have stopped working. This from a "bugfix" patch update. If Adobe PDF Embed API won't allow us to load specific API versions, then I can't keep using it, nor can I recommend it to any of my clients. It's inherently unstable.

[shashank25305410mnu1]

Thank you for reaching out, and we’re sorry to hear about the issues you’re experiencing.

In the mean time,  we will prioritize trouble shooting this, could you please share more details:

• The specific customization code or settings/API you're using

• The behavior you're seeing now vs. before the update
  
  We appreciate your feedback and support.

[Benjamin281283092hgu]

As OP said- it's in every implementation- on your demo even: https://acrobatservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf

As a result of the errors,  simple options like showCommentsPanel: true no longer work on load.

[Jason29694845yh7b]

I'm getting the same issue and my code has not changed in years and has worked with no issues. 

[Benjamin281283092hgu]

Is there any update on this? My app is functionally broken because I can no longer programatically open the comments/annotations pane due to these errors.

[Peter27541665p8gf]

Hey, Adobe. Anything on this? The console is littered with these errors. If I try to actually register a GET_FEATURE_FLAG callback, the viewer code says that this not a recognized callback type. Also,. the viewer doesn't work at all in mobile firefox or even desktop firefox when testing in responsive mode. Can't you push out something that cleans this up?

[nsitu]

I have had a similar experience with the Adobe PDF Embed features. The console is littered with warnings and errors. This does not inspire confidence in the product. 

[GWeimann]

Any information on when it will be fixed?

[matt_7013]

Same issue.  So many console errors and seeing them cause issues with other things such as monitoring PDF pages.  Nothing changed on our end.  Any update on if this is being worked on or when we can expect a fix?

[vinay_2576]

Anyone got solution to resolve this?

[Benjamin281283092hgu]

@Raymond Camden -- Can someone from Adobe please help with this? We have a feature that was developed in May but still can't be shipped because these errors prevent us from opening the comments panel programatically. The radio silence from Adobe makes me wonder if this service is being abandoned in favor of new offerings like Acrobat Studio. As developers who have put a lot of time and effort into integrating your product with our own offerings, I think we deserve a response at least.

[ronmmm]

Maybe we need to mention AI or put AI in the title of the original post to get Adobe's attention. 😉

[Jon35602802ifoo]

OK - that one was funny.

[Sebe_S5425]

Any updates on this issue, now