user is unable to view the extensions when logged into experience.adobe.com
allowed pop-up, still the same, reset IE, still same
shared my screen and tried, it worked
Recreated user windows profile, still the same
tried on an alternate machine, still the same.
Logged into a newly imaged machine wth my credentials, it worked
Logged out and had the user try, it worked.
Hi @ManoranjanPa ,
Can you please check if network calls are being sent from your browser properly. Filter the Network console for "b/ss". All Adobe Analytics hits include "b/ss" in their URLs.
In case if you don't find these network calls, then browser is being prevented from sending the calls, possibly an browser setting or firewall in your office.
Thanks
Tarun
Since you mentioned IE as the browser, I wanted to check if you could try in other browsers such as Chrome as well?
As per the documentation, IE is not one of the supported browsers - https://experienceleague.adobe.com/docs/experience-platform/tags/extension-dev/browsers.html?lang=en
Thanks
Narendra
Tried with Chrome and Edge browser and for both showing the same.
Clear the browser cache and cookies: The user can try clearing the browser cache and cookies to see if that resolves the issue. This can be done by going to the browser settings and selecting the option to clear browsing data.
Disable browser extensions: The user can try disabling any browser extensions that may be blocking the extensions from loading. This can be done by going to the browser settings and selecting the option to manage extensions.
Check browser security settings: The user can check the browser security settings to ensure that they are not blocking the extensions from loading. This can be done by going to the browser settings and selecting the option to manage security settings.
Try a different browser: The user can try logging in from a different browser to see if the issue is specific to the current browser.
Still facing the same issue.
Still facing the same issue
Browser extension is what I was also thinking could be the problem. If you could share any error logs in the console might help to further debug this. Meanwhile, you can try creating an Adobe ticket for this as well.
Thanks
Narendra
@ManoranjanPa Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies