Crash when testing Speech sample app with FoundationModels on macOS 26.0 beta and iOS 26.0 beta

Question

Blume OP

Created 2w

Replies 4

Boosts 0

Participants 3

Hello,

I am testing the sample project provided here: Bringing advanced speech-to-text capabilities to your app.

On both macOS 26.0 beta and iOS 26.0 beta, the app crashes immediately on launch with a dyld "Symbol not found" error related to FoundationModels.framework.

It feels like this may be related to testing primarily on newer Apple Silicon devices, as I am seeing consistent crashes on an Intel MacBook and on an older iPhone device.

I would appreciate any insight, confirmation, or guidance on whether this is a known limitation or if there is a workaround. Is it planned to be resolved soon?

Environment

macOS:

Device: MacBook Pro (Intel)
Processor: 2 GHz Quad-Core Intel Core i5
Graphics: Intel Iris Plus Graphics 1536 MB
Memory: 16 GB 3733 MHz LPDDR4X
OS: macOS Tahoe Version 26.0 Beta (25A5338b)

iOS:

Device: iPhone 11
Model Number: MHDD3HN/A
OS: iOS 26.0

Xcode:

Version: 26.0 beta 3 (17A5276g)

Crash (macOS)

Abort signal received. Excerpt from crash dump:

dyld`__abort_with_payload:
    0x7ff80e3ad4a0 <+0>:  movl   $0x2000209, %eax
    0x7ff80e3ad4a5 <+5>:  movq   %rcx, %r10
    0x7ff80e3ad4a8 <+8>:  syscall
->  0x7ff80e3ad4aa <+10>: jae    0x7ff80e3ad4b4

Console:

dyld[9819]: Symbol not found: _$s16FoundationModels20LanguageModelSessionC5model10guardrails5tools12instructionsAcA06SystemcD0C_AC10GuardrailsVSayAA4Tool_pGAA12InstructionsVSgtcfC
  Referenced from: /Users/userx/Library/Developer/Xcode/DerivedData/SwiftTranscriptionSampleApp-*/Build/Products/Debug/SwiftTranscriptionSampleApp.app/Contents/MacOS/SwiftTranscriptionSampleApp.debug.dylib
  Expected in:     /System/Library/Frameworks/FoundationModels.framework/Versions/A/FoundationModels

Crash (iOS)

Abort signal received. Excerpt from crash dump:

dyld`__abort_with_payload:
    0x18f22b4b0 <+0>:  mov    x16, #0x209
    0x18f22b4b4 <+4>:  svc    #0x80
->  0x18f22b4b8 <+8>:  b.lo   0x18f22b4d8

Console

dyld[2080]: Symbol not found: _$s16FoundationModels20LanguageModelSessionC5model10guardrails5tools12instructionsAcA06SystemcD0C_AC10GuardrailsVSayAA4Tool_pGAA12InstructionsVSgtcfC
  Referenced from: /private/var/containers/Bundle/Application/.../SwiftTranscriptionSampleApp.app/SwiftTranscriptionSampleApp.debug.dylib
  Expected in:     /System/Library/Frameworks/FoundationModels.framework/FoundationModels

Question

Is this crash expected on Intel Macs and older iPhone models with the beta SDKs?
Is there an official statement on whether macOS 26.x releases support Intel, or it exists only until macOS 26.1?
Any suggested workarounds for testing this sample project on current hardware?
Is this a known limitation for the 26.0 beta, and if so, should we expect a fix in 26.0 or only in subsequent releases?

Attaching screenshots for reference.

Thank you in advance.

Screenshot 2025-08-17 at 2.27.57 PM.png

Screenshot 2025-08-17 at 2.29.55 PM.png

Answered by Frameworks Engineer in 854044022

Hi, this is because you are using an older Xcode (beta 3) with a newer OS (beta 6). During beta, we make changes to the API based on developer feedback, so we do not guarantee the compatibility of runtime symbols (ABI) between beta versions. This crash is unrelated to Intel or not.

The best way to resolve this is installing an Xcode that matches your OS.

Boost

Answer 1

Frameworks Engineer OP

Apple

2w

Recommended

Hi, this is because you are using an older Xcode (beta 3) with a newer OS (beta 6). During beta, we make changes to the API based on developer feedback, so we do not guarantee the compatibility of runtime symbols (ABI) between beta versions. This crash is unrelated to Intel or not.

The best way to resolve this is installing an Xcode that matches your OS.

0

Answer 2

Blume OP

2w

I’ve now upgraded Xcode to the latest available build: Xcode 26.0 beta 5 (17A5295f). This should, in theory, resolve the version mismatch issue you highlighted. Please let me know if I should expect to wait for beta 6 specifically, but since this is the latest release, I assume it covers the ABI/runtime symbol alignment.

Current behavior:

macOS (Intel MacBook Pro):

The app launches successfully, and the window is displayed.
Pressing the record button (⭘) results in console logs:

localeNotSupported
could not record: invalidAudioDataType
Playback works (I can hear the recorded sound), but there is no transcription displayed and no highlighting.

Play button plays back my speech.

iOS (iPhone 11, iOS 26.0 beta):

Same as macOS above, except playback volume is extremely faint, even at maximum system volume.

Question regarding Dictation:

I also tried enabling Edit → Start Dictation from the menu, and accepted the prompt. After that:

I don’t see any option to disable it within the app.
Turning off Dictation in System Settings → Keyboard → Dictation → Off does not stop the behavior triggered via the app (console logs indication).

Could you clarify:

Are these console errors (localeNotSupported, invalidAudioDataType) expected in beta 5, or is there a configuration workaround?
Is the low playback volume on iOS a known issue?
What is the correct way to disable Dictation once it has been enabled from the app menu?

Thanks again for your guidance!

0

Answer 3

Engineer OP

Apple

2w

Accepted Answer

Some features of the sample project do require specific hardware. The errors you are seeing are consistent with unsupported hardware.

Try replacing the sample project's use of SpeechTranscriber with DictationTranscriber. The latter supports a broader range of hardware.

You can use SpeechTranscriber.isAvailable to check for hardware support.

0

Answer 4

Blume OP

1w

That clears it up - I’ll try DictationTranscriber with the availability check. Thanks again for your help, really appreciate it!

0