We have an ArcGIS Hub page developed with embedded "Cards" which re-direct to Experience builder applications. This application was working as expected for several weeks until this morning.
When user clicks on a "Card" to go to their Experience builder application the Applications layers do not draw with an error message saying "An error occurred loading this layer" under each layer.
If the user accesses the experience builder by avoiding the hub and instead navigating through ArcGIS Online's content page then the app opens as expected and layers draw as they should.
The URL for the application when re-directed through hub is as follows:
https://*hubname*.hub.arcgis.com/*ItemID*/explore
When the user goes through the ArcGIS Online content and access the experience builder the URL is as follows:
https://experience.arcgis.com/experience/*ItemID*(same ID as above)
It seems to be the hub name in the redirect from the hub page is breaking it and something isn't being passed correctly to the layers for them to be drawn.
Anyone seen this issue before?
Solved! Go to Solution.
The issue has been addressed. Could you please let us know if it works for you?
@C_M_F, my organization is experiencing the same with ExprienceBuilder this morning (post June AGO update yesterday). We did not have this issue yesterday.
I am submitting a ticket now to ESRI in RE to this.
@Jianxia Tagging you here, I think this is probably a HUB issue, but maybe something goofy in ExB?
@MeganEngel , on it now. Thanks for letting us know.
Layers are not showing up in EB- in HUB. If you open the EB on its own, it's OK. Dashboards appear to be working in Hub (embedded). S123 is working embedded in Hub. None of the data layers are working in widgets, in EB, in HUB.
I am seeing the same thing with my other embedded applications, great to point out!
The issue has been addressed. Could you please let us know if it works for you?
Yes, problem is resolved now and layers are displaying when using the Hub page re-direct. Thanks.
Seems to working good now. Can you tell us what happened?
@GIS_Guy_USA, my previous reply is about another issue in the Experience Builder community. Sorry for the confusion. For this issue, the reason is that an internal library is upgraded in Experience Builder which causes Hub not being able to communicate with Experience Builder apps.