Fix iOS build error: replace legacy EXFatal with fatalError#15
Open
DivadOger wants to merge 1 commit into
Open
Fix iOS build error: replace legacy EXFatal with fatalError#15DivadOger wants to merge 1 commit into
DivadOger wants to merge 1 commit into
Conversation
…atalError EXFatal and EXErrorWithMessage are legacy Objective-C APIs in ExpoModulesCore that are not bridged into Swift scope in newer Expo SDK versions, causing build failures. Replace with Swift's native fatalError() which serves the same purpose.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
EXFatal(EXErrorWithMessage(...))with Swift's nativefatalError()inMicrophonePermissionRequester.swiftEXFatalandEXErrorWithMessageare legacy Objective-C APIs in ExpoModulesCore that are no longer bridged into Swift scope as of Expo SDK 55, causing iOS build failuresThis PR was prepared with AI assistance.