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
Describe the bug
Compiler during the build shows warning No platform load command found in pathToProject/MLKitTextRecognitionCommon, assuming: iOS
AND
It's unable to create xcframework using xcodebuild command - the error says error: unable to determine the platform for the given binary pathToFramework/MLKitTextRecognitionCommon; check your deployment version settings
Only this particular framework has this issue - others are ok.
To Reproduce
Build project and see Xcode log OR
execute otool command to see that platform info is missing OR
try to build xcframework to use in project without cocoapods
Expected behavior
No warning in build log and possibility to build xcframework
SDK Info:
GoogleMLKit/TextRecognition 6.0.0
Development Environment:
IDE version: Xcode 15.1
The text was updated successfully, but these errors were encountered:
Im also facing same issue
No platform load command found in '/Users/MyUsername/Documents/Flutter_Apps/MyProject/ios/Pods/MLKitTextRecognitionCommon/Frameworks/MLKitTextRecognitionCommon.framework/MLKitTextRecognitionCommon', assuming: iOS
Describe the bug
Compiler during the build shows warning
No platform load command found in pathToProject/MLKitTextRecognitionCommon, assuming: iOS
AND
It's unable to create xcframework using xcodebuild command - the error says
error: unable to determine the platform for the given binary pathToFramework/MLKitTextRecognitionCommon; check your deployment version settings
Only this particular framework has this issue - others are ok.
To Reproduce
Build project and see Xcode log OR
execute otool command to see that platform info is missing OR
try to build xcframework to use in project without cocoapods
Expected behavior
No warning in build log and possibility to build xcframework
SDK Info:
Development Environment:
The text was updated successfully, but these errors were encountered: