Problem: PDF Embed API dc-core loaded twice

Any update on this yet, I am also facing the same issue.

Has anyone figured out a way to get rid of this issue?

The PDF I have embedded in my NextJS app doesn't load with navigation(i.e., If I go back and come again to that page, the pdf is not showing). It shows when I reload that page. I don't get the 'dc-core loaded twice' error, however.

Hi, when you close or hide the pdf viewer, also do: 

window.AdobeDC = undefined; 
window.adobe_dc_sdk = undefined; 
window.adobe_dc_view_sdk = undefined; 

after that you can load the viewer again without trouble

@Raymond Camden 
I''ve created a minimal repo that demonstrates this issue (or something close to it) in Next.JS:
https://github.com/HolySamosa/adobe-dc-view-isssue

Interestingly, w/ this example in Chrome I'm not seeing the dc-core loaded twice error message, however I still see the same behavior w/ only the initial instance of the PDF component rendering.  When running in an embedded Safari webview on the iOS simulator, we do see the dc-core loaded twice message.  

I have some updated code that I am now using, this was because in certain use cases, I was still getting an error.

the new code waits for everything to load and it then checks if it needs to load the dc core. Hope this helps somebody...

<script type="text/javascript">
  function initializeAdobeDCView() {
    var adobeDCView = new AdobeDC.View({clientId: "Your Token", divId: "adobe-dc-view"});
    adobeDCView.previewFile({
      content: {
        location: {url: "URL"} // URL to your Adobe PDF File
      },
      metaData: {fileName: 'Filename'} // The name you wish the file to have when downloaded
    }, {
      embedMode: "FULL_WINDOW",
      defaultViewMode: "FIT_WIDTH",
      showFullScreen: true,
      showAnnotationTools: false,
      showZoomControl: true,
      focusOnRendering: true,
      showDownloadPDF: true
    });
  }

  function loadViewerScript() {
    if (window.AdobeDC && window.AdobeDC.View) {
      setTimeout(initializeAdobeDCView, 100); // Delay the call to ensure the SDK is loaded
    } else {
      var viewerScript = document.createElement('script');
      viewerScript.src='https://acrobatservices.adobe.com/view-sdk/viewer.js';
      viewerScript.onload = function() {
        setTimeout(initializeAdobeDCView, 100); // Delay the call to ensure the SDK is loaded
      };
      document.body.appendChild(viewerScript);
    }
  }

  loadViewerScript(); // Load the Adobe DC View SDK and initialize the viewer
</script>

We're facing the same problem/error. It worked great until something changed on Adobe's side. It's hard to make a reproducable case when you have a full-fledged web app that relies on other things to even remotely reproduce this in another environment. If it provides any insight, in my case, this error is occuring when an initial PDF is loaded on the page, but a new one is retrieved and attempts to replace the old one - which as mentioned, worked perfectly fine up until a month or so ago and nothing has been changed with our code.

Same issue here. Can we get a reply on this thread ASAP as we have client deliverables that are at risk because of this bug. 

I thought the problem was with the script tag that we have to add in our html, but I'm seeing another script related to adobe being added. I'm noticing that the ViewSDKInterface.js is being added twice.

Is there any official solution to this? I'm having the same problem 😞