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
Invalid Bundle Structure #28
Comments
Hey @bwalpoleuk the SwiftSupport folder needs to be outside your
|
@Flash3001 Thanks I'd missed that point, I can now upload a build but I get an error after it finishes processing:
|
I was struggling with the same error since yesterday for the new version of the library (for Swift 5). Please do a lipo LIBPATH -detailed_info for both libswiftCore.dylib on Frameworks and SwiftSupport and share the result. Also, how are you creating the SwiftSuport folder? |
I updated the script I use to generate that folder, see if helps you: https://github.com/Flash3001/ipa-packager/blob/master/package_ipa_default.sh |
I had to make a tweak at line 29:
Otherwise I was getting:
Unfortunately now I'm back to the original error. Below is the Swift Support:
Frameworks:
|
How are you running the command? it should be something like Like:
That being Invalid Bundle Structure?
Is this output from when? After you run the script I provided? When you got the Invalid Bundle error or from now after you changed line 29? I imagine it is after running the updated script as now the dylibs archs on SwiftSupport match the ones in Frameworks. What happens after you submit this version? |
@Flash3001 Sorry I wasn't clear in my explanation. Without the tweak to the script I got the I ended up with: After the tweak I was able to successfully upload the build but after processing I returned to the error below:
The |
@bwalpoleuk this issue is quite intriguing. I had the same issue and matching the architectures did solve the problem. The remaining thing would be to check if the original files are indeed the same by checking the version. I was looking at the original thread on #26 and you said you tried with 4.2.1 and 4.2.0 (#26 (comment)). Which is the one you are using now? If you are using Xcode 10.1 you should be using version 4.2.1. In any case, you can try another approach altogether. This week I release Xamarin.Swift 1.0.1. It is very different from the way the previous versions work, you don't have to install a bunch of packages and it will figure out which dylibs to include. It also checks if the version is valid and adds the files to SwiftSupport if your build is generating the IPA (there is a configuration on VS for that). https://www.nuget.org/packages/Xamarin.Swift/ |
@Flash3001 Yes you were right I was still using the 4.2.0 packages, after upgrading to 4.2.1 the updated script seems to be working as I've been able to successfully upload a build to iTunes. Thanks for your help with this. |
In an attempt to find a workaround for the issue described here #26 I've modified my AzureDevOps build to re-sign the application after the initial build.
This has got me a bit further so I've added the code to create the
SwiftSupport
folder, however when I submit builds to Apple I get the following error:ERROR ITMS-90171: "Invalid Bundle Structure - The binary file 'MyApp.app/SwiftSupport/libswiftCore.dylib' is not permitted. Your app can’t contain standalone executables or libraries, other than a valid CFBundleExecutable of supported bundles.
This is a bit confusing as I thought the whole point was that the Swift libraries had to be in that folder?
At the moment I'm still just testing the build process so the Swift Core NuGet package is the only one I'm pulling in.
The text was updated successfully, but these errors were encountered: