Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xcode 16 + iOS 18 Assertion failed on runtime #1619

Open
xmercade opened this issue Nov 15, 2024 · 0 comments
Open

Xcode 16 + iOS 18 Assertion failed on runtime #1619

xmercade opened this issue Nov 15, 2024 · 0 comments

Comments

@xmercade
Copy link

Hello, since we recently updated to Xcode 16 and iOS 18 we are facing random runtime crashes due to an assertion failed. Here the error returned:

Assertion failed: (MIN(dstLo->s, dstUp->s)<=isect.s), function CheckForIntersect, file /Users/jenkins/.jenkins/workspace/WhirlyGlobe-Maply_ios_nightly/third-party/glues/source/libtess/sweep.c, line 792.
Can't show file for stack frame : <DBGLLDBStackFrame: 0x3e0ba45f0> - stackNumber:12 - name:-[MaplyBaseInteractionLayer addVectorsRun:]. The file path does not exist on the file system: /Users/jenkins/.jenkins/workspace/WhirlyGlobe-Maply_ios_nightly/WhirlyGlobeSrc/WhirlyGlobe-MaplyComponent/src/MaplyBaseInteractionLayer.mm

We are using the 2.5 precompiled version of the framework, and this is happening either running the project in Debug or Release configurations. We think the issue is more related to the iOS version than Xcode, as in previous versions of Xcode the issue is happening as well, while same project with previous iOS versions was not crashing.

The weird thing is that the crash is totally random, happening from time to time on startup. If the app starts without crashing then seems that this assertion is not affecting the session.

Is there any way to avoid this assertion to be triggered? Either by configuring the library somehow or adding any build setting in the project? We tried with NS_BLOCK_ASSERTIONS set to NO, adding '-ld64' on linker flags and some other workarounds with no success. Any suggestion to avoid this to happen?

Any help would be welcome as we are kind of blocked by this. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant