Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Wrong binary type for cv2 when uploading to Apple Cloud connect

Aperta
  • Qualcosa non va?
#169 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
flutter, opencv, python
Ambito
build-system, mobile

Direzione di ricerca

Inizia ispezionando il tipo Mach-O di cv2.abi3.so e la gestione dei framework cv2 in serious_python_darwin.podspec; confrontali con il wheel di numpy e il relativo tipo binario accettato. Riproduci il flusso di packaging con flutter build ipa e --cleanup-packages, quindi determina quale modifica è necessaria affinché la convalida Apple accetti il bundle generato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hello !

I've built and tested an Flutter app using Serious Python with several non-pure Python packages ( Like opencv ).
I've successfully publish my Apk but i got an error when publishing on the TestFlight of Apple Store.

Here are 3 issue about the same file cv2.cv2 explaining why Apple refuse my .ipa.

TMS-90171: Invalid bundle structure - The “Runner.app/Frameworks/cv2.cv2.framework/cv2.cv2” binary file is not permitted. Your app cannot contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles. For details, visit: https://developer.apple.com/documentation/bundleresources/placing_content_in_a_bundle

ITMS-90124: The binary is invalid - The executable 'Runner.app/Frameworks/cv2.cv2.framework/cv2.cv2' has type 'BUNDLE' that is not valid. Only 'EXECUTE' is permitted.

ITMS-90210: Missing load commands - The executable at 'Runner.app/Frameworks/cv2.cv2.framework' does not have the necessary load commands. Try rebuilding the app with the latest Xcode version. If you are using third party development tools, contact the provider.

If i download wheels (numpy and opencv) from the https://pypi.flet.dev/ repository, and i extract the content, the file command returned 2 differents output for the .so built.

$ file numpy_1_26_4_2_cp312_cp312_ios_13_0_arm64_iphoneos_whl/numpy/core/_umath_tests.cpython-312-iphoneos.so
_umath_tests.cpython-312-iphoneos.so: Mach-O 64-bit dynamically linked shared library arm64

$ file opencv_python_4_10_0_84_1_cp312_cp312_ios_13_0_arm64_iphoneos_whl/cv2/cv2.abi3.so
cv2.abi3.so: Mach-O 64-bit bundle arm64

Do you have any idea why this package is refused by AppleStore ? Did you succeed to publish a iOS app using this package ( using serious python or Flet ) ?
Is a workaround to recompile the package using mobile-forge and adding a compilation flag to change the file type?

Note :

  • I'm on MacOS 26 & xcode 26. (out Github actions CI building and publishing too)
  • Adding the cv2 xcframeworks as a resources instead of frameworks ( serious_python_darwin.podspec ) doesn't change the error.
  • I had to change the CFBundlePackageType from APPL to FRMK in all info.plist of all python packages, or i got an issue about BundleID and AppId. Cannot determine the Apple ID from Bundle ID 'org.python.numpy.random.-pcg64' and platform 'IOS'. (12)
  • Apple Profiles and certs should be okay as it is not our first app Version deployed with our CI.
  • serious_python ( forked ) is a dependencie of a custom Flutter plugin, which is a dependencie of our application.
  • I explored the cv2.cv2.frameworks and xcframeworks folder after "ios preparation", i can't see any other issue in the plists of this xcframeworks.
  • app is build with flutter build ipa ... and uploaded with xcrun altool --upload-package ./path/app.ipa --type ios
  • I used the --cleanup-packages arg of the package command to remove all .a files.

Thanks a lot for any insights and for this awesome package.

Lingua principale
Dart
Stelle
325
Fork
46
Merge medio
14h 53m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di flet-dev/serious-python

Tutte le issue di flet-dev/serious-python

Issue simili

Altre issue su Dart

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.