Error: ITMS-90668 Invalid Bundle Executable. Framework contains incomplete bitcode about xamarin.iqkeyboardmanager HOT 33 CLOSED

@jkapsouras hmmm.. i had problems too initially but that's how i solved it. try removing it altogether, clean, rebuild, add and then clean and rebuild.

anyways, looks like we need a 1.3 soon with a fix for the issue @michaelstonis

from xamarin.iqkeyboardmanager.

Hm, I am not sure exactly what to do here about this. I don't see anything that jumps out from the library configuration though. Can you try building the application using LLVM (https://developer.xamarin.com/guides/ios/advanced_topics/compiling_for_different_devices/) when you are doing an AD Hoc or Release Build?

from xamarin.iqkeyboardmanager.

Sorry for the late response. I'm kinda occupied with other stuff at the moment so will try this later on. Thanks for the help!

from xamarin.iqkeyboardmanager.

So I tried building using LLVM, it still gives me the same error when uploading to iTunesConnect.

Funny thing is, I did manage to get a build uploaded without LLVM once without any errors of the nature, and now when using the same build settings, I am getting the same error again.

from xamarin.iqkeyboardmanager.

@michaelstonis I was thinking of including the Xamarin.IQKeyboardManager project in my project as I can not get any builds to TestFlight. How do I use it if I do so? Tried referencing the project and then kept the same code, but I get a null expection.

from xamarin.iqkeyboardmanager.

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

Someone have solved it?

from xamarin.iqkeyboardmanager.

@luigisaggese I think 1.2 was built with bitcode enabled or something, because no matter what I tried, I kept getting the same error.

For me, I went back to 1.1, Cleaned project, Rebuild project, and then archived for publishing. If there isn't a specific new feature you're looking to use from 1.2, I'd suggest you go back to 1.1 and then clean, rebuild and archive. HTH!

from xamarin.iqkeyboardmanager.

@n1schal I will do in that way (downgrade to 1.1) thanks.

from xamarin.iqkeyboardmanager.

@michaelstonis This was an issue with the original IQKeyboardManager adding some of Apple's private APIs. They've since fixed the issue, but this Xamarin binding needs to be updated. Maybe it's time for a 1.3? :)

from xamarin.iqkeyboardmanager.

Same problem here. Downgrade did not solve the problem. We had to remove the package. Waiting for solution with update!

from xamarin.iqkeyboardmanager.

@jkapsouras you need to clean and rebuild project after downgrading. it worked for me.

from xamarin.iqkeyboardmanager.

@n1schal we tried that, Xcode validated the archive but it failed to upload

from xamarin.iqkeyboardmanager.

@n1schal we will try once more. The problem is that the problem occurs in uploading and not in archiving and we cannot upload new versions only for checking this issue. Let's hope that the 1.3 version will be available soon! @michaelstonis

from xamarin.iqkeyboardmanager.

@jkapsouras i know. i had my builds failing to upload through Application Uploader as well but it was fixed by the steps I said

from xamarin.iqkeyboardmanager.

@n1schal , @jkapsouras I came up with a solution.

1. Download the official IQKeyboardManager code

2. Compile it yourself in XCode, and add a flag to force bitcode:
   Force usage of the flag by adding Other C Flags with OTHER_CFLAGS="-fembed-bitcode". Your xcodebuild invocation would look something like xcodebuild OTHER_CFLAGS="-fembed-bitcode" -target LookbackSDK build.
   (See http://stackoverflow.com/questions/31486232/how-do-i-xcodebuild-a-static-library-with-bitcode-enabled )

3. Download the Xamarin.IQKeyboardManager code, replace the .framework file with the one you generated in XCode, open up the project in Xamarin Studio, and compile it

4. This solution will not run on the iOS Simulator, but it WILL work on device!

from xamarin.iqkeyboardmanager.

I have the same problem with new version 1.3.

Any solution?

from xamarin.iqkeyboardmanager.

Have you tried doing a full clean and rebuild of the entire solution? The latest version is pointed against 4.0.10 and has the additional OTHER_CFLAGS="-fembed-bitcode" as suggested by @spaddlewit

from xamarin.iqkeyboardmanager.

Release 1.3 should resolve any issues with bitcode settings. If you are still experiencing this issue after upgrading, do a full clean and rebuild or better yet delete all bin and obj folders in your solution.

from xamarin.iqkeyboardmanager.

@michaelstonis the issue persists in the new version.

Compiling my own framework version with ENABLE BITCODE = NO (like @spaddlewit says) works for Apple Store upload. BUT fails with simulator (.Shareinstance = NULL issue)

from xamarin.iqkeyboardmanager.

I may have found another flag to remove the bitcode bits with the information here: https://stackoverflow.com/questions/37613550/xcode-error-itms-90635-invalid-mach-o-in-bundle-submitting-to-app-store/37624641#37624641. I verified that LLVM was removed using this guide: https://stackoverflow.com/questions/37613550/xcode-error-itms-90635-invalid-mach-o-in-bundle-submitting-to-app-store/37624641#37624641

I stripped the bitcode using the xcrun bitcode_strip command and verfied using otool. Looks good, so I pushed version 1.3.1. If you are still experiencing this issue, please try a clean and rebuild or a full deletion of the bin/obj folders. If that still doesn't work try fire or silver bullet.

from xamarin.iqkeyboardmanager.

@michaelstonis I solved the problem using this config in .csproj with version 1.3

<Target Name="BeforeCodesign">
    <Exec  Condition=" '%(_Frameworks.FullPath)'!='' " Command="$(_SdkDevPath)\Toolchains\XcodeDefault.xctoolchain\usr\bin\bitcode_strip &quot;%(_Frameworks.FullPath)&quot; -r -o &quot;%(_Frameworks.FullPath)&quot;" />
  </Target>

It seems to be the same solution that you use in v 1.3.1 but in the library code side.

I'll try this new version and comment you the result.

Thank you!

from xamarin.iqkeyboardmanager.

@michaelstonis we will try the new version and post the results.

from xamarin.iqkeyboardmanager.

@jkapsouras or @n1schal any luck with the new package?

from xamarin.iqkeyboardmanager.

unfortunately have not try it yet. I will inform as soon as I upload to apple

from xamarin.iqkeyboardmanager.

@michaelstonis sorry, haven't had the need to upload a new build yet. I'll try and see if it gets to the upload screen, if it does, we can close this issue once and for all :)

from xamarin.iqkeyboardmanager.

version 1.3.1 did not fix the issue for me
However adding the config suggested by facundoplagash worked

from xamarin.iqkeyboardmanager.

Unfortunately no luck (neither with 1.3.1, nor with @brenaud )

from xamarin.iqkeyboardmanager.

@jkapsouras or @brenaud did you do a full clean and rebuild after you upgraded to 1.3.1? There is a pretty good chance that the last release was still cached.

from xamarin.iqkeyboardmanager.

Yes I did. Made various tests. Both with versions 1.3 and 1.3.1. Bin and obj folders deleted. Csproj changed according to @brenaud solution with no luck. All ipas were cut out during verifying assets on itunes

from xamarin.iqkeyboardmanager.

I tried a clean & build, I also tried to uninstall the package and then reinstalling it, got to error when trying to upload the ipa in both cases

But adding

<Target Name="BeforeCodesign">
    <Exec  Condition=" '%(_Frameworks.FullPath)'!='' " Command="$(_SdkDevPath)\Toolchains\XcodeDefault.xctoolchain\usr\bin\bitcode_strip &quot;%(_Frameworks.FullPath)&quot; -r -o &quot;%(_Frameworks.FullPath)&quot;" />
</Target>

in the .csproj (in the second to last line, right before the closing tag) with version 1.3.1 fixed everything for me

from xamarin.iqkeyboardmanager.

I just released version 1.3.2 which includes the new BeforeCodesign call. I am not exactly what is different about this and what I had applied earlier though. Let me know if you hit this issue with the latest @jkapsouras and @brenaud.

from xamarin.iqkeyboardmanager.

On the next version update, I will inform you. The problem is that you have to upload to check if the problem is solved.

from xamarin.iqkeyboardmanager.

Good news @michaelstonis ! The 1.3.2 version worked like a charm. We started a new project today, so I added the keyboard package and the ipa was successfully uploaded to iTunes. Thumbs up for a great package!

from xamarin.iqkeyboardmanager.