Embed API issue

[Carl37356504spww]

Since today we have an Embed API issue. 
The pdf viewer doesn't show a preview anymore.

I get this error:
`Feature can't be enabled or disabled` @featureConfig.js

[Raymond Camden]

Can you share the URL where you see this? We had a release a few days ago (https://developer.adobe.com/document-services/docs/overview/pdf-embed-api/releasenotes/).

[nsitu]

I don't know if this helps, but I am currently seeing an error on this page
https://documentservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf


The error is  similar to the one reported by @Carl37356504spww 
Feature can't be enabled or disabled
setFeatureEnability @ featureConfig.js:188
Setting a breakpoint here reveals that the console error is happening in the context of a series of cases among which various features are possible, but the feature "GENAI_ANON"  has no corresponding case, and as such it falls back to the default case. 

Of note, there is also an additional error here, not yet explicitly mentioned.  (It may or may not be related):
Uncaught (in promise) Edit dropin is not loaded

[Raymond Camden]

So I see the error in console as well, BUT, the PDF loads, and in your screenshot it loads as well. Can you confirm that the error *appears* to be harmless, vs what Carl said?

[Prabhakaran37605252fx08]

Hi Raymond,

We started having this same issue from today and the PDF is not loading in the viewer when using FireFox.

=========================================

Feature can't be enabled or disabled

Uncaught (in promise) Edit dropin is not loaded

rendering worker created

Uncaught (in promise)

Object { code: "PREVIEW_RENDERING_FAILED" }

rendering worker created

===================================================

However, in Edge and Chrome browsers the PDF is loading in the viewer.

At the same time its opening in few other PCs in all the browsers.

Cheers

Prabhu

[Raymond Camden]

What OS? I tried Firefox on Windows and it worked fine.

[Prabhakaran37605252fx08]

The OS is Windows and since it works in Firefox in few other PCs, we suspect this to be a local issue. We will see from our side for any specific in those PCs.

[nsitu]

@Raymond Camden thanks for your question. Indeed the PDF does load on this URL. https://documentservices.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf 
As for whether the error is "harmless", this may depend on the situation. I see your point that the core functionality is not affected. However if your goal is to inspire confidence among users, then in my mind error messages are not enitrely harmless. But I would love to learn more about others' expectations and experiences in this regard. 

[Thorsten Schneider]

We have the same issue and the PDFs won't render anymore.

We had plenty of times the problem already that after recent updates the API was not working anymore at all. Overall there seems to be some kind of very poor quality management which leads us to look for another product instead. If there were at least some options to work with older (stable) versions, but in a product where you always gets the latest version thats really not acceptable.

[Raymond Camden]

Being able to specify a specific version is something we've absolutely flagged as a must have improvement. Right now though it isn't possible. 

[Thorsten Schneider]

Would be highly appreciated if that was possible. Overall I am always wondering why so few implementations of the Adobe API are in place. But this might be exactly the reason. Right now in our company there are 20 people in proofreading department who can't work anymore and there is absolutely nothing we can do about it, except changing to another product of Enfocus. Impossible to use your product for a live production system.