Closed nbelyh closed 1 year ago
Could it be the issue with providing SPFx web part hosted directly from your organization's App Catalog to external users in general
If you’re not using CDN with your SPFx webparts, most likely they’re hosted from your app catalog’s SiteAssets/ClientSideAssets library. If you have external users accessing your site, they won’t by default be able to access this site at all, and will hence encounter weird issues with the SPFx webparts.
How to enable your external users to access your SPFx webparts that are not hosted on CDN: Enable the CDN and re-deploy the app there How to fix Office 365 CDN if it breaks? Modify the ClientSideAssets -library’s permissions in the app catalog site to allow external users access there. This includes at least the following steps. Enable external sharing on your tenant if it isn’t enabled already. Enable external sharing on the App Catalog site Invite a group with your external/guest users to the ClientSideAssets library as visitors/readers.
Another reference, how to enable hosting of SPFx web parts from AppCatalog for guests: https://www.crowcanyon.help/article/431/
The new version 1.2 this is resolved, it is using CDN (jsdelivr). This eliminates the dependency on the user infrastructure. There is still a self-contained build created under releases that would not use CDN.
The normal file viewer shows the diagram properly. The users can access the files.