-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Crash on launch after updating to ios-v3.4.0-beta.2 from ios-v3.4.0-beta.1 #6883
Comments
I just pointed a demo project I have at |
@boundsj Yes, crash happens every time, and reverting back to beta.1 fixes it. |
@jfirebaugh here is the diff between beta.1 and beta.2. There were a few core changes like #3563 and #6773 in this version. @JesseCrocker would it be possible to share a sample project that reproduces the crash? I'm not seeing this on a few different apps that I'm now using beta 2 in. |
@boundsj I'm seeing the crash on a closed-source project, but i'll try and come up with a test case to send over tomorrow morning. |
Thanks @JesseCrocker! Even if it is just a list of what you are doing (Mapbox iOS SDK related) when the app starts and details about your environment (i.e. Xcode version, Swift or Objective-C) that would be helpful. And, if you can manage, an Xcode project that reproduces the issue would help the most. |
From what I've seen, Initing with no frame cause MapBox to crash. |
I can confirm what @naluhh said, it's related to the frame. I was calling |
Thanks for narrowing this down @naluhh and @JesseCrocker. Here is the repro case then: // Don't use a frame
mapView = MGLMapView()
mapView.translatesAutoresizingMaskIntoConstraints = false
mapContainerView.addSubview(mapView)
mapView.topAnchor.constraint(equalTo: mapContainerView.topAnchor).isActive = true
mapView.leftAnchor.constraint(equalTo: mapContainerView.leftAnchor).isActive = true
mapView.bottomAnchor.constraint(equalTo: mapContainerView.bottomAnchor).isActive = true
mapView.rightAnchor.constraint(equalTo: mapContainerView.rightAnchor).isActive = true This problem is not entirely new, it seems. In beta.1 if the lines that add the constraints are commented out, the following endless log spew occurs:
In beta.2 the crash noted above occurs no matter if the constraints are added or not. |
I do see this crash with the repro mentioned above, and a |
Weirdly, in manually disabling GL error checking for a local dev copy, both setting an initial |
Similarly, adding |
Current status on debugging this is something outside of |
@incanus The worrying part here is that the stack trace contains |
Yeah, I am seeing that as a separate issue though—that we possibly rolled a build wrong. If I disable GL error checking, things don't crash, but we still get GL framebuffer bind warnings, which I want to get rid of. That's basically the core issue here now, though it should not technically be a crash. |
#1572 tracks the GL framebuffer bind warnings specifically. (That ticket notes that some users have experienced crashes due to that issue, but the crash is unreproducible.) |
We should still get to the bottom of why @JesseCrocker was seeing this crash only on v3.4.0-beta.2 but not v3.4.0-beta.1 with the same CGRectZero. Does #6883 (comment) prove that we inadvertently built beta 2 as a Debug build? We did make changes to the SDK build script between the last alpha and beta 1 (like #6581), but I’m unaware of any changes to the deployment script after beta 1. |
I have this issue about 1 of 5 launches, when it happens I rebuild and it works.
Let me know what to provide to help your finding the bug. |
@nitrag this appears to be a different issues related to the user annotation view and not GL error checking + IB constraints. Can you please open a new ticket with the stack trace you posted above? |
|
Platform:
iOS Simulator
Mapbox SDK version:
ios-v3.4.0-beta.2, installed with podspec https://raw.githubusercontent.com/mapbox/mapbox-gl-native/ios-v3.4.0-beta.2/platform/ios/Mapbox-iOS-SDK-symbols.podspec
Steps to trigger behavior
App was working properly on ios-v3.4.0-beta.1, after updating to os-v3.4.0-beta.2 it crashes on launch. The stack trace led me to believe it was related to showing user location, but disabling showing user location did not fix it.
Console output
Disassembly
Stack Trace
The text was updated successfully, but these errors were encountered: