Closed braess closed 1 month ago
Hi @braess
Thanks for raising this with us. We've added a task to our backlog to investigate this further, as this is something we should be able to test for.
While I don't currently have an ETA I can share on exactly when this will be addressed, we'll make sure to post any updates here.
Hi Milo, thanks for your quick reply. Let me know if you need any further information.
Hi @braess
A fix for this has now been released in v6.30.1 of bugsnag-cocoa. Mac Catalyst targets now only attempt to call os_proc_available_memory() for version 13.1 or above of Mac Catalyst. Please let us know if you have any questions about this!
Thanks for the update! This should solve the problem.
Hi @hannah-smartbear,
release v6.30.1 does not seem to resolve this issue. Mac Catalyst apps running on macOS 10.15 are still terminated on launch with the same symbol not found exception.
Only extending @available
as in the current fix is probably not enough. To check for api availability in this case, the TARGET_OS_MACCATALYST
macro would need to be used as well.
Hi @braess
Thanks for letting us know. We’ve added another task to look into this further and consider the approach of using TARGET_OS_MACCATALYST to check for API availability. We will be sure to let you know of any updates on this.
Describe the bug
Mac Catalyst apps running on older macOS versions (10.15) are terminated on launch with a symbol not found exception:
Symbol not found: _os_proc_available_memory
Function os_proc_available_memory is available on iOS 13.0+ and Mac Catalyst 13.1+: Apple Documentation
It looks like BSGRunContext.m UpdateTaskMemory might be incorrectly checking api availability: BSGRunContext.m
This issue could be related or a regression of a similar problem: Fix os_proc_available_memory runtime link error on Mac Catalyst
This crash was reported by users, unfortunately I can't reproduce it myself as I don't have macOS 10.15 anymore for testing. Below the limited information I received.
I'm not quite sure that this really is the problem, but BugSnag appears to be the only sdk using os_proc_available_memory. It would mean that Mac Catalyst apps supporting older macOS versions can't use bugsnag-cocoa at the moment.
Thanks for looking into this issue.
Steps to reproduce
Environment
Crash report