-
-
Notifications
You must be signed in to change notification settings - Fork 797
[IOS] Invalid Segment Alignment libmobileffmpeg.dylib does not have proper segment alignment. Try rebuilding the app with the latest Xcode version. #45
Comments
@thecsy which |
yes, 2.1.1 , 3.0 all try.. |
@thecsy Can you confirm that Run/Test/Archive does not fail and this issue happens only on upload? |
Can you try using this test version mobile-ffmpeg-full-3.0-ios-shared-universal.zip, built with |
Sorry, can't Xcode 9.4 mobile-ffmpeg-full-3.0-ios-shared-universal mobile-ffmpeg-full-3.0-ios-static-universal mobile-ffmpeg-full-2.1.1-ios-shared-universal |
Hi @thecsy. There is a misunderstanding. Can you test this version on your Xcode 10.1.
What is capture error, do you mean 'Invalid Segment Alignment' error? |
test is Xcode 10.1 version use yes , Invalid Segment Alignment' error share version is always Error (Segment Alignment) |
please , Just one test. (appstore upload) it's Build options to date
what's try option remain? |
Can you try with this one? This is different than the previous link. |
It was built with Sorry but I don't have any other suggestions. |
I copied this sentence from apple forum. "The main problem is that you've built the framework to include binaries for both the simulator and devices. This isn't officially supported at all (because the iOS simulator is actually macOS platform, while devices are iOS platform). Your framework must contain only ARM architectures for iOS platform. Try building the framework again with just the correct architectures and platform. It's possible all the other errors will go away too." ffmpeg libraries is running also on intel architecture. |
I tried to remove unwanted architectures but no changes echo "Target architectures: $ARCHS" APP_PATH="${TARGET_BUILD_DIR}/${WRAPPER_NAME}" find "$APP_PATH" -name '*.dylib' -type d | while read -r FRAMEWORK FRAMEWORK_TMP_PATH="$FRAMEWORK_EXECUTABLE_PATH-tmp" remove simulator's archs if location is not simulator's directorycase "${TARGET_BUILD_DIR}" in echo "Completed for executable $FRAMEWORK_EXECUTABLE_PATH" done |
yes finally I found the solution. Use static binary. there is a problems on framework and dynamic library. I successfully uploaded the store and tested on device. |
@codaman Yes, you really did it 👍 I was trying to find a solution for months and this I'd like to ask if you can test the following solution for dynamic frameworks. Can you add a new
|
@tanersener i didn't try it. I will try it |
Please use |
share version build ok, but not upload
dylib error... my Xcode 10.1 version
Originally posted by @thecsy in #18 (comment)
The text was updated successfully, but these errors were encountered: