Debugger extension for IE, Safari & Firefox | Community
Skip to main content
Level 2
May 4, 2018
Declined

Debugger extension for IE, Safari & Firefox

  • May 4, 2018
  • 6 replies
  • 10500 views

We have had a lot of issues troubleshooting a recent issue experienced in IE. Having an Adobe Experience Cloud Debugger for other browsers would have allowed us to be more efficient in our troubleshooting. This would also be helpful from an Analytics perspective.

6 replies

andylunsford1
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 25, 2020

For Safari, there is a solution that I just recently uncovered that has been a lifesaver:


https://requestly.io/desktop

 

You can create rules using the web extension in Chrome or Firefox that basically point the embed code URL from the production one to staging, and then the desktop app automatically runs your internet through the proxy in the tool and applies them.  All you need to select is "Request Redirect" and then enter your production library URL from the embed code setup, and then the library you want to test from the embed code setup.

 

It works great for me testing Safari, (I then review using the network tab after checking "Show Develop menu in menu bar").  It's in Beta and only available on MacOS currently, but you probably can do something with Fiddler on Windows, although not as easily.

cristinel
Adobe Employee
Adobe Employee
January 27, 2023

The Adobe Experience Platform debugger is now available for both Chrome and Firefox. For more details see the extension page on Experience League: https://experienceleague.adobe.com/docs/experience-platform/debugger/home.html?lang=en

 

November 24, 2023

The Adobe Experience Platform debugger-extension for Firefox can not be found, the link is broken Any solution? Thanks 😃

johnm1839017
Level 2
June 11, 2024

Has the firefox extension been discontinued ?

New Member
August 14, 2024

Yes, that is correct. The link found on experienceleague page is broken. 

https://experienceleague.adobe.com/en/docs/platform-learn/data-collection/debugger/overview
This link results to 
https://addons.mozilla.org/en-US/firefox/addon/adobe-experience-platform-dbg/

 

There is an alternate using Tampermonkey extension

link: https://www.tampermonkey.net/index.php?browser=firefox&locale=en

 

// URL of your new script
document.head.appendChild(newScript);

// Function to remove the existing script
function removeOldScript() {
const oldScript = document.querySelector('script[src="<current Launch Environment URL>"]');
if (oldScript) {
oldScript.parentNode.removeChild(oldScript);
}
}

// Function to add your new script
function addNewScript() {
const newScript = document.createElement('script');
newScript.textContent = "new Launch Environment URL";
console.log('New script loaded!');
document.head.appendChild(newScript);
}

// Execute the functions
removeOldScript();
addNewScript();

 

I know this is a longer approach but 

 

 

New Member
August 14, 2024

I am not sure if the extension is discontinued. The extension is not found on Firefox extension when we use the links found on ExperienceLeague documentation. 

https://experienceleague.adobe.com/en/docs/platform-learn/data-collection/debugger/overview

 

 

 

https://addons.mozilla.org/en-US/firefox/addon/adobe-experience-platform-dbg/

 

Obviously, the debugger has more options if it was available. If the primary purpose is to replace the Launch libraries for validate and evaluate beacon then use tamper monkey extension, here is the link. 

https://www.tampermonkey.net/index.php?browser=firefox&locale=en#google_vignette

 

Create a new script: 

// URL of your new script
document.head.appendChild(newScript);

// Function to remove the existing script
function removeOldScript() {
const oldScript = document.querySelector('script[src="current Launch Environment script URL"]');
if (oldScript) {
oldScript.parentNode.removeChild(oldScript);
}
}

// Function to add your new script
function addNewScript() {
const newScript = document.createElement('script');
newScript.textContent = "new Launch Environment Script URL";
console.log('New script loaded!');
document.head.appendChild(newScript);
}

// Execute the functions
removeOldScript();
addNewScript();

 

I hope that helps