You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crash is likely caused by the GeometryReader in the FrameGetter and SafeAreaGetter of the Util class. Could you please take a look at how to fix this bug?
The text was updated successfully, but these errors were encountered:
kobeisgod
changed the title
App crash SIGABRT
App crash SIGABRT caused by the GeometryReader in the FrameGetter and SafeAreaGetter of the Util class
Apr 8, 2024
kobeisgod
changed the title
App crash SIGABRT caused by the GeometryReader in the FrameGetter and SafeAreaGetter of the Util class
App crash SIGABRT , caused by the GeometryReader in the FrameGetter and SafeAreaGetter of the Util class
Apr 8, 2024
I had the same crush - so I used swiftui instrument to check the body getters. There were severe hangs because of popup view and another problem of mine. It seems the problem is not the exyte popupview itself but the code that keeps calling the popup. And it could be you just ran out of memory and system terminated the app at another popup go. When I fixed my issue the SIGABRT went away. Maybe it's the same for you
Hey @kobeisgod, did you manage to locate what causes the problem? This FrameGetter is a standard frame getting practice in SwiftUI, as far as I know, and shouldn't cause any issues by itself. If you think exyte popup causes this issue, please attach a minimal example so I can reproduce the crash
After opening the App from the widget, it's likely for the App to crash.Error message as follows:
$s14ExytePopupView11FrameGetterV4body7contentQr7SwiftUI01_C16Modifier_ContentVyACG_tFAF03AnyC0VAF13GeometryProxyVcfU_yyScMYccfU_ + 140
$s14ExytePopupView14SafeAreaGetterV4body7contentQr7SwiftUI01_C16Modifier_ContentVyACG_tFAF03AnyC0VAF13GeometryProxyVcfU_yyScMYccfU_ + 40
The crash is likely caused by the GeometryReader in the FrameGetter and SafeAreaGetter of the Util class. Could you please take a look at how to fix this bug?
The text was updated successfully, but these errors were encountered: