Add Bitcode support for iOS

[eseidelGoogle]

Apple may eventually require Bitcode support for iOS. It's currently required for submissions to tvOS and watchOS stores.

We've seen Dart's toolchain produce Bitcode as a demo:
https://medium.com/dartlang/dart-on-llvm-b82e83f99a70

This bug tracks (eventually) turning that demo into a production solution.

[ngocdaothanh]

Bitcode support is also being added to Kotlin-Native:
JetBrains/kotlin-native#1564

[ngocdaothanh]

Hi, is there any progress on this feature?

[dnfield]

Additional reason:

• In an Add2App scenario, anyone using Flutter in their app can no longer use bitcode, and all targets/projects in their workspace will have to disable it.

[wederchr]

Hi Team,

I understand that Bitcode support is not a high prio feature for most Flutter users. However, for security critical apps Bitcode support is crucial since most app hardening frameworks rely on it. Meaning apps that need to be hardened (e.g. for legal reasons) cannot be developed with Flutter. Would you kindly reconsider the prioritization of this feature?

[eseidelGoogle]

@yapcwed I would like to learn more about that use case. Can you point us to some example hardening frameworks which depend on bitcode?

[evant]

https://www.guardsquare.com/en/blog/bitcode-ixguard is one

[magnatronus]

Hi,

so as far as I understand this is causing the issue I have put on StackOverflow here:
https://stackoverflow.com/questions/53048589/adding-a-watch-app-to-a-flutter-ios-application
Which means that no iOS Flutter based apps can have an associated WatchOS app added to them.

Is this correct?

[eseidelGoogle]

@magnatronus looks unrelated to bitcode, but I don't know for sure. @xster or @dnfield might.

[dnfield]

tvOS and watchOS stores require bitcode.

[Ruiqi-Zhou]

Need this feture too，otherwise app's size may increasing

[fvisticot]

Need iWatch and tvOS as well !

[sgalway00]

Also looking for WatchOS support.

[Portalesoft]

+1

[gimox]

Adding bitcode for iOs is mandatory for me . Without AppleTv or iWatchKit is not possibile to valuate Flutter as full replacement language for mobile. Please consider to increase task priority!

[zoechi]

@gimox you have the power to increase priority by upvoting the initial comment.

@Portalesoft @fvisticot @sgalway00

Using "add reaction" on the initial comment would increase priority while +1 comments are rather pointless and cause lots of people to get notified for no reason.
To get notified yourself use the [Subscribe] button to the top right instead.

Also upvotes on follow-up comments don't increase priority.

[magnatronus]

@eseidelGoogle my tests adding a watch app to an iOS app have moved on. I now kinda have it working.

My test Flutter project can be found here. As far as I have got it does basically works (I am yet to try and add a Watch Session to enabled real time comms). But I have come across an issue with Flutter (maybe?) which I have commented on in my project. The basic issue is that once I have added the Watch Kit target to the iOS project Flutter refused to either do a run or an iOS build. But if I use XCode directly I can get it to work, in both cases.

[dnfield]

@magnatronus that sounds pretty interesting. Can you provide any more details about how you added it to the project and got it to build? The normal way of doing this should trigger the same error as you're seeing.

AFAIK (and I may very well be wrong), you need to have bitcode enabled to submit to the store for watch apps. Are you able to submit your working version to the store?

[magnatronus]

@dnfield Basically I created a standard Flutter app, then in the iOS project just add a new target of a Watch Kit app (details in my project readme). After doing this it will not build/run using the Flutter tooling, but directly in the iOS project it will.

I built out the Watch App in XCode using Swift.

At the moment I have only build AD-HOC, but the steps are basically

• Set Device to Generic Device
• Build Archive
• In Organiser select project/Distribute App button
• Select the AD- Hoc option

At this point it offers 3 options (2 auto selected - which I left), which were

• Rebuild from BitCode
• Strip Swift Symbols

I then manually signed the app and then waited while it built the distro. This takes a while as it looks like it is rebuilding with BitCode.

The resulting IPA file is usable for test distro (I used HockeyApp for this) and have both the iOS app and the installed Watch App on my devices.

I want to try adding Watch session first, if that works I will try a store submission.

[dnfield]

Very cool - please do let us know if these steps end up working for the store!

[magnatronus]

@dnfield I now have the Watch Kit session communicating with the Flutter app. Need to tidy up both code bases then I will try an app Store submission.

[gimox]

@magnatronus impressive! Let us know if store submission is ok!

[vitor-gyant]

@dnfield Great. I'll give it a try.

[ngocdaothanh]

@dnfield Many thanks for the great work.

Can you give an instruction where to put ENABLE_BITCODE?

I guess it's ENABLE_BITCODE=yes flutter build ios (https://flutter.dev/docs/deployment/ios)?

[vitor-gyant]

@dnfield I'm facing a strange error while testing this. So, I've created a new flutter project, enabled bitcode on the app target and tried to archive the app which went just fine. I've added local_auth package to pubspec, , removed the post_install hook on pod file that disables bitcode for all the plugin targets and tried to archive but now it fails.

ld: warning: Could not find auto-linked framework 'Flutter'
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_FlutterError", referenced from:
      objc-class-ref in LocalAuthPlugin.o
  "_OBJC_CLASS_$_FlutterMethodChannel", referenced from:
      objc-class-ref in LocalAuthPlugin.o
  "_FlutterMethodNotImplemented", referenced from:
      -[FLTLocalAuthPlugin handleMethodCall:result:] in LocalAuthPlugin.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Is there anything missing on my side ? thanks

[larryaasen]

@vitor-gyant When you added local_auth to your pubspec, did you point to the version on pub.dev, or did you point to the one in master? If you pointed to the one in pub.dev, maybe the iOS project that gets generated is not compatible. Try pointing directly to master.

[vitor-gyant]

@larryaasen Thanks but it does not work too. I don't think this has something to do with the plugin itself since bitcode support has no impact on the current source code.

[vitor-gyant]

I should say that compiling in release works just fine. Compiling for Generic iOS Device too. Archive is the only step where the error occurs.

[dnfield]

I'll try this when I'm back at my desk tomorrow. It's likely there's still some work to do for plugins.

[dnfield]

@vitor-gyant - I was able to export a bitcode enabled app, but I did have to make sure to manually set ENABLE_BITCODE to YES for the Pods target. I've filed #39793 to track making that work better by default.

[danallen88]

Even when enabling bitcode for the Pods target, I'm still unable to build or archive in XCode - even when using a Generic iOS Device as the target. The error I'm getting is:

ld: library not found for -lFirebaseCore clang: error: linker command failed with exit code 1 (use -v to see invocation)

I've tried manually linking this library in the WatchKit extension targets to no effect. I imagine this points to dependencies needing bitcode support as well? Am I understanding that correctly? It seems odd that the WatchKit app would need to care about the iPhone dependencies at all. The only report I've seen of this working (from @magnatronus) is a trivial app with no dependencies.

[dnfield]

Yes. All of your targets must have bitcode enabled, and any frameworks your linking in must have been built with bitcode. I know I've seen at least one plugin out there that isn't (connectivity).

[danwulff]

@dnfield I tried to do a quick glance through of some of the flutter/packages to determine whether the iOS side has bitcode enabled or not but I couldn't get a clear understanding of what that looks like.

Could you give an example of how a package is setup to support bitcode, and what file that support lives in.

[dnfield]

It has to be built with ENABLE_BITCODE set to yes. There's no one good place to look for that - it could be in the .pbxproj for that project, or it could be in a .xcconfig that was used to build it. Unfortunately, the best way to tell is to try to build the library with bitcode and see if Xcode complains that some framework wasn't built with bitcode. If so, it will suggest you rebuild it with bitcode or request that the author ship a binary with bitcode.

Many flutter plugins should work - for example, local_auth definitely works. This should always be true if you're compiling the plugin from source yourself. However, you may run into trouble if you have a binary distribution that was not built with bitcode.

[danwulff]

@dnfield Thanks so much for the further details. That makes more sense.

I imagine we will see some issues created for packages that aren't compatible in the coming weeks.

[dnfield]

I've updated https://github.com/flutter/flutter/wiki/Creating-an-iOS-Bitcode-enabled-app-(experimental) with some more instructions/details around this.

[danallen88]

Would you mind sharing what you have configured for your Library Search Paths when you have dependencies like url_launcher? My troubleshooting up to this point has led me to believe that the project default is incorrect and causing the ld: library not found for -l<lib_name> errors.

[dnfield]

My library search paths are blank - I did this in just a brand new project:

flutter create bitcode_plugin_test
cd bitcode_plugin_test
# add plugin to pubspec.yaml
open ios/Runner.xcworkspace
# Select signing information, set ENABLE_BITCODE to Yes, Build

[danallen88]

Thank you for the support, @dnfield. I'll be curious to see if others are able to take an existing Flutter repo, make the updates to support bitcode, and add a WatchKit extension without issue. The documentation you've provided has been very helpful in understanding what needs to happen to enable bitcode, so I think at this point the issues I'm experiencing are project-related and not necessarily framework-related.

[vitor-gyant]

@dnfield Did you have the opportunity to test a sample app with at least one plugin (url_launcher) exported with bitcode enabled ? I have tried in a new flutter project with just url_launcher in the pubspec and still get the following error only when archiving:

ld: warning: Could not find auto-linked framework 'Flutter'
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_FlutterMethodChannel", referenced from:
      objc-class-ref in UrlLauncherPlugin.o
  "_OBJC_CLASS_$_FlutterError", referenced from:
      objc-class-ref in UrlLauncherPlugin.o
  "_FlutterMethodNotImplemented", referenced from:
      -[FLTUrlLauncherPlugin handleMethodCall:result:] in UrlLauncherPlugin.o
ld: symbol(s) not found for architecture arm64

Since url_launcher is a source code dependency I don't see a problem related to it. I've change the podfile to set ENABLE_BITCODE to YES. Also double check that every bitcode setting is now YES in the both app and pods target.

Is this something you're working on ?

Thanks,

[dnfield]

@vitor-gyant - I did successfully build and archive the Flutter Gallery with bitcode since this.

When you go to archive, are you sure you're archiving release mode? And are you sure you enabled bitcode on the pods targets as in the linked wiki page ( https://github.com/flutter/flutter/wiki/Creating-an-iOS-Bitcode-enabled-app-(experimental))?

[vitor-gyant]

@dnfield It seems my working copy was not in a good "shape". After running flutter build --ios it work as expected. What was strange was that changing the configuration to release in Xcode and compiling did not have the same effect of running flutter build --ios.

[zeucxb]

Are there some example using bitcode to watch apps?

[peroksid90]

I have checked bitcode which gets generated for the test project
Runner.app/Frameworks/App.framework/
and it looks like that is not "real" bitcode, but a Mach-O binary file instead.

There should be files like 1, 2, 3, 4,... of LLVM bitcode type and wrapper. And you should be able to process those using llvm-dis. However, we get a Mach-O binary there.

I have used bitcode_retriever tool to extract xar files from Runner.app/Frameworks/App.framework/App:

shell $ bitcode_retriever App
arm.xar
arm64.xar

shell $ xar -xf arm64.xar
shell $ file 1
1: Mach-O 64-bit object arm64

If you did the same for Runner.app/Runner binary, you would get correct bitcode of LLVM bitcode type:

shell $ bitcode_retriever Runner
arm.xar
arm64.xar

shell $ xar -xf arm64.xar
shell $ file 1
file 1
1: LLVM bitcode, wrapper

The root cause of that issue is that an assembly file got put as input for clang:

flutter/packages/flutter_tools/lib/src/base/build.dart

Line 257 in fb69a39

assemblyPath,

Clang produces correct xars that carry LLVM bitcode if you pass unmanaged code or llvm-bitcode, and set -fembed-bitcode flag (it is possible to re-create a binary containing bitcode from bitcode).

If it was possible to get Dart compiled into llvm-bitcode, it would be proper bitcode-enabled archives generated.

Thus, even it is now possible to build projects with BITCODE_ENABLE=YES, the community I believe is still facing the following issues:

1. Compatibility with analysis tools such as Veracode
2. Use of app-hardening solutions (rely on bitcode)

[dnfield]

@peroksid90 - it would probably be helpful to discuss this in a new issue. Feel free to tag me in it.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

[jmagman]

This issue is very old, but for interested parties: due to Apple dropping bitcode in an upcoming release, Flutter will be removing support for bitcode.

Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.

Xcode no longer builds bitcode by default and generates a warning message if a project explicitly enables bitcode: “Building with bitcode is deprecated. Please update your project and/or target settings to disable bitcode.” The capability to build with bitcode will be removed in a future Xcode release. IPAs that contain bitcode will have the bitcode stripped before being submitted to the App Store. Debug symbols for past bitcode submissions remain available for download. (86118779)

https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes

Work tracked in #107887. Please file new issues if you see bugs or have documentation requests. Thanks!