395

I have this new warning about the Google Framework in my app:

(null): URGENT: all bitcode will be dropped because '/Users/myname/Library/Mobile Documents/com~apple~CloudDocs/foldername/appname/GoogleMobileAds.framework/GoogleMobileAds(GADSlot+AdEvents.o)' was built without bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. Note: This will be an error in the future.

Xcode 7 is giving me around 204 warnings about this same concept, and I could not get around with this. Also I have a problem accessing the network from my app. This is the error from the Debugging Area:

-canOpenURL: failed for URL: "kindle://home" - error: "This app is not allowed to query for scheme kindle"

All of these problems were not present in iOS 8.

Improve this question
9
  • So you've enabled bitcode in your Xcode target? Commented Jun 15, 2015 at 14:51
  • Sorry I am new to this, can you tell me how please? Commented Jun 15, 2015 at 14:53
  • I've never done it, but it looks to be something you have to set deliberately. You appear to have done that. Commented Jun 15, 2015 at 14:57
  • 4
    @Droppy AFAIK the setting is turned on by default, but you can deactivate it any time in your project settings. Commented Jun 15, 2015 at 15:04
  • I turned them off and all the warnings went away. I researched a bit and Google needs to update their framework for this error to be off, until now just turning it off will work. Does anyone know about the -canOpenURL: failed for URL: "kindle://home" - error: "This app is not allowed to query for scheme kindle" ? This I have no idea what Xcode is talking about Commented Jun 15, 2015 at 15:13

7 Answers 7

Reset to default
1033

Your library was compiled without bitcode, but the bitcode option is enabled in your project settings. Say NO to Enable Bitcode in your target Build Settings and the Library Build Settings to remove the warnings.

For those wondering if enabling bitcode is required:

For iOS apps, bitcode is the default, but optional. For watchOS and tvOS apps, bitcode is required. If you provide bitcode, all apps and frameworks in the app bundle (all targets in the project) need to include bitcode.

https://help.apple.com/xcode/mac/current/#/devbbdc5ce4f

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

@Centurion the previous google analytics lib is deprecated and does not compile with xcode 7 / ios9 either
@goelv yes you should be able to submit apps with bitcode disabled. it is optional right now. it may become required in the future.
Did NOT work for me for archiving. Pre XCODE 7 project was working fine, now can not ARCHIVE even with Enable Bitcode set to NO. This is for the AWS library.
Still getting the error after disabling Bitcode on all targets.
113

After Xcode 7, the bitcode option will be enabled by default. If your library was compiled without bitcode, but the bitcode option is enabled in your project settings, you can:

  1. Update your library with bit code,
  2. Say NO to Enable Bitcode in your target Build Settings

Enter image description here

And the Library Build Settings to remove the warnings.

For more information, go to documentation of bitcode in developer library.

And WWDC 2015 Session 102: "Platforms State of the Union"

Enter image description here

Improve this answer

Comments

43

In my case for avoiding that problem:

  1. Be sure that you are dealing with Xcode 7, NOT lower versions. In lower version this flag does not exist.

  2. Setup: Project>Build Settings>All>Build Options>Enable Bitcode = NO

enter image description here

Improve this answer

1 Comment

So, you will have to recompile the libraries included in your project with XCode7 and with EnableBitcode set to YES. Quite complicated if you are working with 3rd party .a librarires.
15

Method canOpenUrl is in iOS 9 (due to privacy) changed and is not free to use any more. Your banner provider checks for installed apps so that they do not show banners for an app that is already installed.

That gives all the log statements like

-canOpenURL: failed for URL: "kindle://home" - error: "This app is not allowed to query for scheme kindle"

The providers should update their logic for this.

If you need to query for installed apps/available schemes you need to add them to your info.plist file.

Add the key 'LSApplicationQueriesSchemes' to your plist as an array. Then add strings in that array like 'kindle'.

Of course this is not really an option for the banner ads (since those are dynamic), but you can still query that way for your own apps or specific other apps like Twitter and Facebook.

Documentation of the canOpenUrl: method canOpenUrl:

Documentation about the LSApplicationQueriesSchemes key

Improve this answer

2 Comments

Supposed that a static library will check a parent app deeplink, how to use exception 'LSApplicationQueriesSchemes' in the static library? Normally you do not have a Info.plist for that.
I'm not really sure about that, if a library needs to check for apps outside it's parent the parent should define the url's in it's info.plist (so document it for the framework). If canOpenUrl also returns no will the parent app can handle it, than you should (i assume) also include those in the info.plist
14

If you are using CocoaPods and you want to disable Bitcode for all libraries, use the following command in the Podfile 

post_install do |installer| installer.pods_project.targets.each do |target| target.build_configurations.each do |config| config.build_settings['ENABLE_BITCODE'] = 'NO' end end end
Improve this answer

Comments

8

Disclaimer: This is intended for those supporting a continuous integration workflow that require an automated process. If you don't, please use Xcode as described in Javier's answer.

This worked for me to set ENABLE_BITCODE = NO via the command line:

find . -name *project.pbxproj | xargs sed -i -e 's/\(GCC_VERSION = "";\)/\1\ ENABLE_BITCODE = NO;/g'

Note that this is likely to be unstable across Xcode versions. It was tested with Xcode 7.0.1 and as part of a Cordova 4.0 project.

Improve this answer

Comments

2

To fix the issues with the canOpenURL failing. This is because of the new App Transport Security feature in iOS9

Read this post to fix that issue http://discoverpioneer.com/blog/2015/09/18/updating-facebook-integration-for-ios-9/

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.