Post

Replies

Boosts

Views

Activity

dyld: Symbol not found: ScrollView scrollDisabled
With 16.0b1, I am seeing a runtime error of: Symbol not found: _$s7SwiftUI10ScrollViewV14scrollDisabledyACyxGSbF This happens in both our app and test host apps. We are using Simulator 17.0.1. Has anyone else seen this issue? I'm still looking for anything that might be amiss, but it looks fine and runs on 15.4 fine. Edit: I have confirmed that this only happens when running 17.x simulators.
4
2
731
Jun ’24
AppIntents not working in Release
We have some AppIntents we are POCing and when we make a Release build, they no longer appear in the system. These AppIntents live in a Framework compiled and linked with the core app. We believe that this is related to Mergable Libraries. We have confirmed that the meta data for the framework still contains a list of all of the actions and their mangled symbols. The mangled symbols however now live in the app binary (confirmed by building Release with DEBUG_INFORMATION_FORMAT = dwarf) If we move the AppIntent code into the app target, things once again work as expected. Is there a flag we need to set, or is moving the code into the app target the only workaround? Thank you!
3
0
348
Aug ’25
dyld: Symbol not found: ScrollView scrollDisabled
With 16.0b1, I am seeing a runtime error of: Symbol not found: _$s7SwiftUI10ScrollViewV14scrollDisabledyACyxGSbF This happens in both our app and test host apps. We are using Simulator 17.0.1. Has anyone else seen this issue? I'm still looking for anything that might be amiss, but it looks fine and runs on 15.4 fine. Edit: I have confirmed that this only happens when running 17.x simulators.
Replies
4
Boosts
2
Views
731
Activity
Jun ’24
AppIntents not working in Release
We have some AppIntents we are POCing and when we make a Release build, they no longer appear in the system. These AppIntents live in a Framework compiled and linked with the core app. We believe that this is related to Mergable Libraries. We have confirmed that the meta data for the framework still contains a list of all of the actions and their mangled symbols. The mangled symbols however now live in the app binary (confirmed by building Release with DEBUG_INFORMATION_FORMAT = dwarf) If we move the AppIntent code into the app target, things once again work as expected. Is there a flag we need to set, or is moving the code into the app target the only workaround? Thank you!
Replies
3
Boosts
0
Views
348
Activity
Aug ’25