You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running through a proof of concept which is attempting to load images from a remote host as a material on a collection of blocks. The code is very simple:
photoUrl is valid and I do see requests to load these images going out in Chromes network inspector. However, the url loads are immediately cancelled which I can only assume is a CORs issue although there is no error information being displayed. I did see on the aframe github issues that there is a need to pass in "crossorigin"="anonymous" but cannot see how to inject that here.
If I change the remote url for a locally hosted image the code is working fine.
Thanks
The text was updated successfully, but these errors were encountered:
Same issue, I tried to put crossOrigin='anonymous' in img tag (in the section a-assets) and in THREE.ImageLoader, THREE.FileLoader, document.querySelector('a-assets').fileLoader ... everywhere , I still have CORS issue
My Config: "aframe-react": "^4.4.0" / "aframe": "1.0.4" @andrewrutter@yogiprsetya please have you found a solution ?
I don't know if it's related to aframe-react or aframe component , everywhere in my react app I don't have CORS issues.
I am running through a proof of concept which is attempting to load images from a remote host as a material on a collection of blocks. The code is very simple:
photoUrl is valid and I do see requests to load these images going out in Chromes network inspector. However, the url loads are immediately cancelled which I can only assume is a CORs issue although there is no error information being displayed. I did see on the aframe github issues that there is a need to pass in "crossorigin"="anonymous" but cannot see how to inject that here.
If I change the remote url for a locally hosted image the code is working fine.
Thanks
The text was updated successfully, but these errors were encountered: