Repeated error in console in relation to registering callbacks for GET_FEATURE_FLAG

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

@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.

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?

Any information on when it will be fixed?

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. 

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.

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

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.