ERROR ITMS-90668 - Uploading application to App Store

[marlonconstante]

Hello guys, I'm having trouble submitting my application that uses the Card.io component in the App Store.

The following error is presenting the Application Loader:

ERROR ITMS-90668: "Invalid Bundle Executable. The executable file 'Demo.iOS.app/Frameworks/CardIOSharp.framework/CardIOSharp' contains incomplete bitcode. To compile binaries with complete bitcode, open Xcode and choose Archive in the Product menu."

Any idea how to solve this issue?

Note: I am using the Xamarin component (https://components.xamarin.com/view/cardioios)

[bluk]

@marlonconstante How are you building the framework? Is the Enable Bitcode set to YES in Xcode target configuration? Sorry not familiar with Xamarin's build process.

You can see the original source at https://github.com/card-io/card.io-iOS-source which has the Project Config with Bitcode enabled by default for the framework build.

[marlonconstante]

@bluk I am using the Xamarin component (https://components.xamarin.com/view/cardioios), which is official, right?

I believe that is the case then generate a new build with this option bitcode enabled to solve the problem, correct?

[bluk]

@marlonconstante The Xamarin component is being built by a 3rd party and isn't official from anyone associated with card.io AFAIK. Judging from the link, the publisher says it's Xamarin Inc, so maybe someone from Xamarin is repackaging? I would personally be a little bit cautious since it's an unknown 3rd party building something that handles credit cards as a binary library.

You may want to see if you can just try disabling bitcode entirely in your build process. That may work for now since Bitcode isn't required by Apple. Normally for Xcode projects or Cordova/React Native based projects, you can modify the Xcode project settings to Enable/Disable. I'm not sure how you would do that with Xamarin unfortunately.

[SOFSPEEL]

Note that I am experiencing exact same problem, note the following, when I backed down to version 5.1.0.0 the problem goes away.

Note too that I have emailed Xamarin support directly to try to get a resolution for this issue on more recent version of cardio. Once known I will update this post.

[mlimbocker]

Just checking in on this. Have you heard anything from Xamarin about what's going on here?

[EdHubbell]

I had this issue when uploading to the App Store. I just installed the latest version (5.3.2.1) of the component from Xamarin via https://components.xamarin.com/view/cardioios#

I had to directly download as the integrated Xamarin component store wasn't working for me. Again.

This version was posted after the comment by @mlimbocker , so they may be all set already.

[Redth]

Hey folks, I work on the Xamarin component and we had a few requests from customers around this issue. v5.3.2.1 was released to address this issue :)

To the Card.IO team: If you're interested in taking over ownership of the bindings to the SDK's, we'd be more than happy to help transition the bindings and code over. The current code is all open-sourced and located here: https://github.com/xamarin/XamarinComponents/tree/master/XPlat/CardIO

Thanks!

[braebot]

Great thanks for the update @Redth! I'll close this issue.

As for ownership, let's open a new issue, or have a conversation outside of GitHub about whether it makes sense for the code to move over to github.com/card-io.

[alxbog]

@Redth would you please describe how you fixed it? We have the same problem binding another library.

[Redth]

@alxbog the tl;dr is that we had an xcode project referencing this library which we bound, but forgot to disable BITCODE on our own xcode project. ymmv...