Skip to content

Remove bitcode support from recipes, migrate off ios-release-nobitcode artifacts #107886

@jmagman

Description

@jmagman

Once bitcode support has been removed from the engine #107884, remove --bitcode flags from the recipes. Unify the ios-release-nobitcode and ios-release artifacts. May need to publish both for awhile until customers are informed ios-release-nobitcode is going away?

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.

https://flutter.googlesource.com/recipes/+/a3a6b38798fcc6ee99602ef745150ca3555422f8/recipes/engine/engine.py#1399

  • Update recipe to upload a no-bitcode version to both buckets
  • Update the roll script to use ios-release instead of ios-release-nobitcode
  • Update recipe to stop uploading to ios-release-nobitcode

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: tech-debtTechnical debt, code quality, testing, etc.engineflutter/engine related. See also e: labels.platform-iosiOS applications specificallyteam-infraOwned by Infrastructure team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions