Unexpected fatal error! Please report this to us. Build started: FullCompile Configuring (7.35s) Compiling syntax tree (2.63s) Generating code and data (5.73s)
Does this happen to all your projects, or just one? Can you please share the full build log, including the command you used to start the build?
Hey Anders, I have uploaded the log on the link below. I tried what you recomended and the error persists and yes it only happens on my project as I downloaded an example and it ran perfect.
this is the command I used:
fuse preview -t=local
This looks like a crash in our png loader. Could it be that your app is using an image that’s actually a jpeg, but saved as
.png? I know we recently had an issue with this causing crashes, and I don’t think the fix has beed deployed to production yet.
Please check if your images are saved with the correct extension, and if that doesn’t help, please upload your project to https://www.dropbox.com/request/ZgndLtJQm5eGzG9cicGK so we can have a look at it. Files uploaded to that link is only available to the Fuse team.
Anyway, sorry for the crash, if this is indeed an issue with an image like I suspect, we should (and very soon will) give an error message instead of crashing.
By the way, which version of Fuse (
fuse --version) are you running?
Hey @Anders this a project Kelvin and I are working on so the code works on Windows runs perfectly nothing wrong, but on osx it crashes.
We’re on the latest version
Fuse version 0.20.3 (build 6549)
I’m doubting that’s the problem since it works on windows, what happens if that’s not the case? What else can we do?
BTW we can’t upload the project
The underlying Fuse code for Windows and OS X is not always identical. This means that while you should normally expect to see the exact same behaviour on Windows and OS X, some bugs in Fuse can manifest on one platform only. The bug I mentioned above only affects OS X.
That bug has been fixed in the underlying support library, but has not made its way to a Fuse installer yet, and will not do so in a few days still.
If you’re unable to upload the project, the only options I can think of in the mean time are:
- Check that your images are saved with the correct extension.
- Comment out one image at a time until you find the one that’s crashing your preview, and if possible send that to us, or try to figure out what’s wrong with it.
If this is still an issue in a few days, I can send you an experimental installer that contains a fix that might solve your issue. This won’t be officially released until next week however.
Awesome, we’ll try that and we can wait till next week thanks.
Hey Anders so that was the probelem, but it crashes whenever we switch to a page with an image, might be with every image then. Could you please send us a link to that experimental installer?
I’ll PM you the new installer on Slack.
Cool sounds good, I’m under @Edwin
Hey @Anders we’re on the latest fuse version 0.22 build 6996
and we’re still getting some error which is non readable to a non Objective C/Uno person. Anyway to know what’s going on? this is the error we’re getting:
If you can’t figure it out don’t worry too much about it we’ll be refactoring our app soon
2016-07-23 22:53:05.125 Crowder[789:216206] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x126d78700 h=-&- v=-&- MKMapView:0x124de5700.height == UIView:0x126c7df10.height>", "<NSLayoutConstraint:0x126cb7550 UILayoutGuide:0x126cb6fd0'Edge Insets'.top == MKMapView:0x124de5700.top + 20>", "<NSLayoutConstraint:0x126cb7d40 UILayoutGuide:0x126cb6fd0'Edge Insets'.bottom == MKMapView:0x124de5700.bottom>", "<NSLayoutConstraint:0x1288181f0 'UIView-Encapsulated-Layout-Height' V:[UIView:0x126c7df10(0)]>" ) Will attempt to recover by breaking constraint <NSLayoutConstraint:0x126cb7d40 UILayoutGuide:0x126cb6fd0'Edge Insets'.bottom == MKMapView:0x124de5700.bottom> Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful. 2016-07-23 22:53:08.222 Crowder[789:216206] Trying to start MapKit location updates without prompting for location authorization. Must call -[CLLocationManager requestWhenInUseAuthorization] or -[CLLocationManager requestAlwaysAuthorization] first. libc++abi.dylib: terminating with uncaught exception of type uBase::Exception: uBase::Exception (lldb)
I’m afraid I don’t know what that means without some more investigation. So maybe we should just save both of us some time and get back to it after your refactoring if it’s still a problem then?
So going back to the error we are getting when building the project in IOS. We just made an example project and uploaded to the DropBox/Request hoping you can take a look at it when you get a chance, the name of the File is -“Error Example”.
Thanks in advance. Kelvin
If you’re now talking about the runtime crash, this is because some of your pngs are actually jpegs.
Assets $ identify * pic1.png PNG 634x423 634x423+0+0 8-bit sRGB 774KB 0.000u 0:00.000 pic2.png PNG 959x639 959x639+0+0 8-bit sRGB 1.775MB 0.000u 0:00.000 pic3.png JPEG 1276x669 1276x669+0+0 8-bit sRGB 696KB 0.020u 0:00.029 pic4.png JPEG 2496x1664 2496x1664+0+0 8-bit sRGB 2.123MB 0.010u 0:00.000 pic5.png JPEG 960x640 960x640+0+0 8-bit sRGB 125KB 0.000u 0:00.000 pic6.png JPEG 2560x1840 2560x1840+0+0 8-bit sRGB 630KB 0.000u 0:00.000 pic7.png JPEG 844x550 844x550+0+0 8-bit sRGB 143KB 0.000u 0:00.000
Try to make sure your images have the correct extension and you should get around this issue.
Of course Fuse shouldn’t crash in this case, I’ll make sure we improve in that regard in a future version.
Yea we were hoping for better errors, we don’t understand any of that? Any resources to understand any of the above you posted?
What I’m saying in the above post is that I checked all your
.png files, and it looks like many of them are actually JPEG images that for some reason are saved with a
.png extension. If you save your images with the correct file extension, the error should go away.
Yea I got that part, and got it to work Anders thanks. It’s because I got those images of the internet, most likely the person thought changing the extension would just convert them (still wondering when OSes are going to make it that easy lol) and just uploaded them that way. So it downloaded as png’s or something like that, idk those images are old was a while back. But I guess I don’t need to really understand where you got that data from, since you’ll be providing better errors soon.
I got that info from
identify, a tool from ImageMagick (
brew install imagemagick)