Did Exactly that and im having an issue that just won’t go away. I set a jpg file for an image, it’s in the bundle for iOS, works on the preview “player” but image won’t show up in iOS there is nothing i can do about it, it juste won’t show. Any Ideas? Also if i set the image source in Javascript and then use it for the source i get the same ‘BundleFileImageSource-failed-conversion’ error no matter what.
Also i guess it’s normal that Fuse renames each image once it’s in Xcode?
Do you have a small, isolated test case with your code that replicates your issue so we can take a look at it and help you figure out what’s happening? If you don’t want to post here in the forum you can send us your project via Dropbox as well (ZIP file (and skip the .build folders please)): https://www.dropbox.com/request/ZgndLtJQm5eGzG9cicGK
Looks like some files are missing (the whole components folder is missing, so the file located at components/views/Landing.ux cannot be loaded and therefore the project won’t build). You can use the same Dropbox link again to send an updated ZIP-file for us to take a look at.
the root cause of your issue turns out to be the excessively large images. You should resize them to be somewhat closer to the actual screen size (do mind density) of the devices you’re targeting.
Since this is a device-dependent limit, there is no one-size-fits-all solution or a hard limit. You will need to figure out what it is for your devices, but a general rule is to try and stay below 3000 px in any direction.
Hey, Thanks for the update. The problem is, i know for a fact that these images work on iOS and Android Native, my app already exists in these formats and work perfectly. So i would say it’s a hard limit for Fuse or Metal/GL ? Because i don’t think there is a way to know in UX what type of device is running the app, so there is not way to get an image that fits the device that’s running. I can try to make it a big lower than 3000 but it’s still a problem. The app uses a search engine to look up images from the web. I can’t control the size of these images, so that’s a big limitation.
@Marc Giroux: Sorry for this problem. We have had a plan for dealing with this for a while, but we were waiting for some pending rewrite in this area to land first, which it hasn’t. However, I decided to give it a go, and it seems this was easier than I feared: