Participant

Question

Status Code 403 for main.js.map and ViewSDKInterface.js.map

Forum|Forum|5 years ago
February 5, 2021
10 replies
3916 views

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

This topic has been closed for replies.

S

Shubhanshu Dixit

Adobe Employee

Hello everyone,

The issue has been fixed now. We want to apologize and understand how frustrating this delay must be.

Thanks for the patience

Z

Zhenhua5D87

Participating Frequently

Thanks, the warning is gone. But it's still not showing well on my page. It works occasionally on Chrome, but never shows the document on Safary and Chrome Incognito mode: https://sodaa360.com/apps/newsletters/.

A

Antonio Ooi

Inspiring

Mine works well on Chrome Incognito too, just not sure about Safari. But for Safari, many devs feel like giving up because it is hard to be pleased, more like the old IE (although still considered as 'Modern Browser'). Many Mac and iPhone users rather choose to install Chrome on their device than using Safari.

Z

Zhenhua5D87

Participating Frequently

The same issue. Some it works and most of the times it's not showing anything!

Z

Zhenhua5D87

Participating Frequently

Occasionally works on Chrome. Never worked on Chrome Incognito mode and Safari.

E

EE04SG

Participating Frequently

What to do.... its free...

E

EE04SG

Participating Frequently

What I'm unhappy with is their website is not affected, but everyone's is down...
https://documentcloud.adobe.com/view-sdk-demo/index.html#/view/FULL_WINDOW/Bodea%20Brochure.pdf

A

Aman Jain

Participant

I'm also facing the same issue, Is any fix or alternate proposed by Adobe.?

I

Israa5E87

Participant

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 ?

R

Rui5E2F

Participant

Come on Adobe team, this shouldn't be very difficult to fix... And this is really boring

S

Shubhanshu Dixit

Adobe Employee

Sorry for the inconvenience caused. We are yet to resolve this issue. We are targeting to fix it soon.

T

Tovi5E20

Participant

Any updates on this?
Thank you!

S

Shubhanshu Dixit

Adobe Employee

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.

A

Abhishek Arora

Adobe Employee

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.