xcode archive failure- missing signing identifier ... site-packages/google/..._api_implementation.cpython-39-darwin.so

[nicholas-buscaglia]

simulation building and testing on device was success but now kivy project won't archive

[vrepo54]

I have exactly the same issue! There's also a similar error for the package yaml on my side

[nicholas-buscaglia]

Search for these files and delete the redundancies - Somehow during the xcode build (not sure if it has anything to do with the ios kivy toolchain actually) the project ended up containing redundant executables... these files were found in both build phases in xcode: "link binaries with libraries" and "copy bundle resources." I located the 5 or so redundancies in the directory found in "copy bundle resources" and deleted. After that the submission was successful. And everything still works so thats nice:)

On Thu, Apr 28, 2022 at 6:39 PM vrepo54 @.***> wrote:

I have exactly the same issue! There's also a similar error for the package yaml on my side

— Reply to this email directly, view it on GitHub https://github.com/kivy/kivy-ios/issues/697#issuecomment-1112717909, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVWQ33KZTFBA7LA2VGTTFSDVHMHQVANCNFSM5TAC2D6Q . You are receiving this because you authored the thread.Message ID: @.***>

[vrepo54]

Hi Nickstradamus, thank you for your answer! I can find those files in the lib folder in dist/root/python3 which is listed in the "Copy Bundle Ressources" phase, but not in the "Link Binary With Libraries" that seems to be looking at very different files. I've tried removing the files in question from dist/root/python3 but then the app does not run anymore since those packages are required by it. Did it look like that for you too?

[nicholas-buscaglia]

Pretty sure I was able to clearly id the overlap so maybe it is a different issue for you. But you could just copy the files to your desktop before you delete and if doesn't like that just put back:) Good luck! There is always a way!

On Fri, Apr 29, 2022 at 2:10 AM vrepo54 @.***> wrote:

Hi Nickstradamus https://github.com/Nickstradamus, thank you for your answer! I can find those files in the lib folder in dist/root/python3 which is listed in the "Copy Bundle Ressources" phase, but not in the "Link Binary With Libraries" that seems to be looking at very different files. Did it look like that for you too?

[image: Screenshot 2022-04-29 at 07 39 33] https://user-images.githubusercontent.com/79753063/165892833-4614bcc3-7537-47a3-9f59-a9e78d46e811.png

[image: Screenshot 2022-04-29 at 07 41 23] https://user-images.githubusercontent.com/79753063/165892864-4a92f032-d45d-4aef-8a74-8dabe78ae31a.png

[image: Screenshot 2022-04-29 at 07 41 55] https://user-images.githubusercontent.com/79753063/165892880-cc58aaeb-09a1-43b5-af9c-c5c653d88dd9.png

— Reply to this email directly, view it on GitHub https://github.com/kivy/kivy-ios/issues/697#issuecomment-1112908171, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVWQ33MMMIGXRLJNP7VM7RDVHN4OHANCNFSM5TAC2D6Q . You are receiving this because you authored the thread.Message ID: @.***>

[misl6]

Hi @Nickstradamus , How did you built protobuf? Did you created a local recipe for that? (See: https://github.com/kivy/kivy-ios/issues/702)

[pakal]

I just had a similar issue with my kivy-ios project.

I switched to manual signing, and it allowed me to have clear error messages about the issue : simply put, ".so" files are forbidden in iOS uploads, all the code must be gathering into a single executable.

So it's as mentioned in https://github.com/kivy/kivy-ios/issues/702 : you need to compile protobu using a kivy-ios reciped, so that its .so is actually empty, and all code gets integrated into .a files which will be statically linked to the final program.

[misl6]

Duplicated of #702