-
Notifications
You must be signed in to change notification settings - Fork 122
XCode 13.3, iOS 15.4 - MGLMapView renderSync #650
Comments
I have the same problem. xcode update to 13.3, when first load mapbox component then app crashed. |
Same here. |
Same here: |
Thanks for the feedback. A few questions:
|
Hi, I am using your SDK directly in iOS. Hope it helps :-) |
I got the same error using Xcode 13.3 and iOS 15.4 Simulator: When trying to figure out what could cause the crash I reduced te map to load just te base style. When disabling all sources / layers the map loaded just fine. Then I started adding sources + layers gradually. I ended up having everything back on the map without crash so I'm no not certain on what caused it. Mapbox-iOS-SDK: 6.3.0
|
We're also getting the same crash with Xcode 13.3 |
I have the same crash. Only in simulator. |
I have the same crash: simulator only, Xcode 13.3, iOS 15.4, and using the mapbox sdk directly in iOS. If it can help:
So it seems related to the handling of the current location ? I also managed to make it run once (then the second time it crash) by commenting out in my code a line: // mapView.showsUserLocation = true |
I'm able to consistently replicate the crash in my simulator environment: Xcode:
This does not appear to affect device builds. |
the same problem |
Same problem here! |
yup, encountering the same problem |
Mapbox SDK version: 6.4.1 Stack trace:
|
Is anyone from Mapbox addressing this issue? Its extremely frustrating. |
Same problem here |
1 similar comment
Same problem here |
Bringing @1ec5, @ZiZasaurus & @jmkiley into the conversation. I know you guys have been working super hard on v10, but the legacy SDK (still officially Mapbox-supported until April 2023) could use a bit of attention. I know your customers and the developer community would very much appreciate resolutions to this and other persistent bugs. Thanks! |
I get this just about every time I launch our app in the iOS simulator. Hasn't happened once on a physical device that I know of, but debugging our setup is much easier in the simulator. Xcode 13.4.1, iPhone 13 simulator running 15.5. |
Happens to me too on Xcode 13.4.1 and iOS 15.5. This is preventing me from testing map related things on simulator. I intend to upgrade to v10 eventually, but this is a big issue! |
@knov - 👋 Hi Kristen, I see you were involved in triaging this issue a few months ago. Would you mind bringing it to the attention of the MapBox SDK engineers please? 🙏 |
Just driving by here, since I was pinged, but I haven’t worked on the map SDK for a long time and wasn’t involved in some of the more recent GLKit-related changes. I’ll defer to the map SDK team for an official response, but here are some observations based purely on the information in this issue.
If you’re only seeing this issue when the map view shows view-backed annotations, such as the user location indicator, then the introduction of It looks like all the reports above were observed in a simulator, except for #650 (comment). |
Thanks for your feedback @1ec5! Since you aren't currently working on the iOS Maps SDK, would you please loop in any of the MB PMs/engineers who are currently involved? There doesn't seem to be anyone from Mapbox monitoring this repo anymore. Appreciate it! |
Yes, they’re aware of this issue and will be following up as soon as they can. |
Anyone looking for a quick fix, I can confirm this crash does not occur when using the simulator with iOS 14.5, Mapbox v6.4.1. Saved my neck when creating screenshots! |
I have the same exact issue, when is this expected to be fixed? |
encountering the same problem 😞 |
I think there are two problems:
This did not occur to me with version 8.5.0, but started happening when using 8.6.0-beta.0. Rolling back to 8.5.0 fixed this for me. |
Same issue happening for months now too. iOS 16 is around the corner, and we still can't reliably test on iOS 15 Simulators. 😬 |
Hi @maios, @pjleonard37 and @evil159 -- as active Mapbox iOS SDK engineers, I'd like to loop you in on this issue affecting the legacy SDK (which appears to be officially Mapbox-supported until April 4, 2023 per the docs.) Your colleague @1ec5 mentioned in June that you guys would take a look at this bug and resolve ASAP. Could I kindly request on behalf of myself and other paying Mapbox customers that you please give this issue a glance? I'd be happy to support in the debugging/testing process. Many thanks! 🙌🏻 |
Just to be clear, I wasn’t making any promises about resolving the issue ASAP. If I was that sure about how to fix the issue, it probably would’ve been fixed already by someone more familiar with the underlying graphics code than I am. 😅 For what it’s worth, I personally find it very difficult to reproduce the issue. It happens sometimes but not frequently enough to experiment with any speculative workarounds. Maybe I’m just getting (un)lucky for the time being, but if any of you notice anything else unusual during debugging, that information could lead to a faster resolution than me killing some downtime by rerunning iosapp in a loop. |
@1ec5 For me it crash 100% of the time. So to help you I created a minimal project where it also crash 100% of the time: https://github.com/malaba/MapBoxCrash.git Just follow the instruction in the README.md Let's work from there. |
MapLibre users report that Apple has fixed the issue in the iOS 16 simulator in Xcode 14: maplibre/maplibre-native#268 (comment). Similarly, in this project, I haven’t encountered this crash in the iOS 16 simulator so far using iosapp, whereas it does reproduce occasionally for me in the iOS 15 simulator. |
So this just started happening when map is first being loaded. I have not made any local changes to my app.
Steps to reproduce
Expected behavior
Actual behavior
Thread 1: EXC_BAD_ACCESS (code=1, address=0x7fda25d7bf60)
Configuration
Mapbox SDK versions: 6.4.1
iOS/macOS versions: iOS 15.4
Device/simulator models: Simulator Version 13.3 (977.2)
Xcode version: Version 13.3 (13E113)
Probably related to this persons issue as well mapbox/mapbox-gl-js#11633
The text was updated successfully, but these errors were encountered: