SDK was working fine but now its start showing following error.
DevTools failed to load SourceMap: Could not load content for https://documentcloud.adobe.com/view-sdk/2.13.1_2.0.0-bb177d3/private/main.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://documentcloud.adobe.com/view-sdk/2.13.1_2.0.0-9ef32cc/private/ViewSDKInterface.js.map: HTTP error: status code 403, net::ERR_HTTP_RESPONSE_CODE_FAILURE
I'm also receiving this error too.
Thanks for reporting the errors. We have noted it down and will work on fixing them in the coming release. Though these errors are completely harmless (can be ignored) and only show up when developer tool is opened.
When I get this error, nothing displays on the webpage either. Not sure why.
Not really, such errors may harm our SEO performance. Look at the attached screenshot, isn't that too much not to be devalued by Google Search? Besides, APIs provided by reputable organization like Adobe should have such problem, just for the corporate image sake.
Can't edit my comment, this is the correction:
"...organization like Adobe shouldn't have such problem"
You guys are SUPERB! No more warnings and errors now! Adobe Embed API is the only way to embed PDF in HTML without browser warnings and errors! Bravo! 😄
Unfortunately, looks like those warnings are back again. 😞
Same problem here too. Used it for the first time on a site yesterday, so am not sure if this is a regular thing, or rare and Adobe need to sort it, or if it's something I'm doing wrong.
Honestly speaking, this is quite common to all sorts of PDF embed even if we use the conventional methods like <iframe>, <embed>, and <object>. But the Adobe team did able to solve it several days ago (you can see it on my above screenshot), but since yesterday, I noticed this problem came back again. It may not be a serious technical problem, but as I said, it can be a serious "business problem", especially in terms of SEO. It can be hard for Google to rank you highly with this whole bunch of warnings being logged on the browser.
Yes, it was. You're not sure, but I'm sure.
If you think the Adobe team has yet to resolve this issue, you should have replied to my comment with screenshot earlier ago.
Same problem here guys!!!!
Sorry for the inconvenience caused. We are yet to resolve this issue. We are targeting to fix it soon.
Any updates on this?
Thanks for checking. We are actively working on this. Again, we are incredibly sorry for the inconvenience this has caused and will update you as soon as we have a resolution.
Come on Adobe team, this shouldn't be very difficult to fix... And this is really boring
I have use the api today, and I have test it on local, but I have the same warning and I'm afraid to push the code with those warning, is there any update ? does adobe fix the issue ?