Embedded panoramas not refreshing when moving between features

[MikeLelliott]

Hi,

I'm trying to create a viewer of 360 panorama images using the Experience builder, where users can click on a point in the map and the Embed widget pulls the URL of each panorama from the attributes of the point.  

The URL is created by combining the Pannellum standalone viewer link (details here: https://pannellum.org/documentation/examples/simple-example/) with the URL of the 360 image for each point. 

This works perfectly when clicking on the first point, but it then won't refresh and load the new 360 view when clicking on the next point.

Any help on how to get the 360 view to refresh between each image would be much appreciated.

Thanks

[PeterMacKenzie2]

Hi @MikeLelliott . Any chance you can share what this experience builder app looks like? Or even a screenshot DM'd to me? I am keen to get one working with 360 images too. Thanks!

[babarsac]

@MikeLelliott @TonghuiMing @PeterMacKenzie2 

I'm using Experience Builder built into Enterprise 10.9.1 and am running into the same issue. I've got Pannellum integrated via the Embed widget however it will only load the first image I click on. 

Any ideas?

[TonghuiMing]

@babarsac - Based on both of your descriptions, it seems like an issue with similar URLs, however, I just tried the latest AGO environment as well as 10.9.1, and it looks fine:

In order to reproduce the issue and locate the problem, it could be helpful if you could provide your data, as well as how you configure the app/Embed widget.

If the data cannot be shared, you could reach out to Esri Tech support, the analysts will help with that.

[TonghuiMing]

@MikeLelliott What are your environment details?

[babarsac]

@TonghuiMing 

I was able to get it working. Turns out I had some spelling errors in my URL request.

[AndrewBowne]

Has anyone been able to get this working with secured services?  Each of our points have the 360 photos as attachments.  I'm passing the attachment URL to pannellum but they won't load because they are secured.  I tried passing a token in the URL with no luck either.