Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asset validation failed Invalid Bundle Structure for libnpyrandom.a and libnpymath.a #814

Closed
kschepps opened this issue Jun 2, 2023 · 1 comment

Comments

@kschepps
Copy link

kschepps commented Jun 2, 2023

I'm trying to build a new app using Xcode 14.3 and Mac Ventura. I am experiencing this bug, #787, and I need to delete the libfreetype every time I recompile the app. However, I got a fully working app, but I'm having issues distributing the app. I can't find any info on how to resolve it.

It's complaining about two libraries, math and random. Both are in the numpy folder. I tried deleting them just like i did for freetype, but that produced a lot of errors when re-building the app.

When I try to distribute the app, I get these two errors:
× Asset validation failed
Invalid bundle structure. The "myapp.app/lib/python3.9/site-packages/numpy/random/lib/ libnpyrandom.a" 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
(ID: a29e7c8e-717-463b-b977-77b84f728898)

× Asset validation failed
Invalid bundle structure. The "myapp.app/lib/python3.9/site-packages/numpy/core/lib/ libnpymath.a" 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 ID:
42e9d725-dafd-4e8c-8d84-9a6682b1927f)

@kschepps
Copy link
Author

kschepps commented Jun 5, 2023

Nevermind... I fixed this by updating all the packages and rebuilding the toolchain from scratch. This is like the 3rd Kivy related issue that was fixed by simply updating something.

@kschepps kschepps closed this as completed Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant