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
As pointed out by @jasssonpet, the underlying issue is that SymbolLoader does not resolve module names to framework bundles correctly, leading to searching for a data or function symbol in the wrong bundle. Our class resolution logic has somewhat subverted this issue, because we resolve classes through the Objective-C runtime which looks into all bundles, ambient and explicit alike.
Currently this means that any function or extern data symbol exported from a framework has a chance of not being resolved at runtime.
Reported by @Fatme:
The text was updated successfully, but these errors were encountered: