Skip to content

Provide officially code-signed xcframeworks for add-to-app #183422

New issue
New issue
Closed as not planned
Closed as not planned
Provide officially code-signed xcframeworks for add-to-app#183422
Labels
a: existing-appsIntegration with existing apps via the add-to-app flowteam-iosOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.

Description

@hellohuanlin
hellohuanlin
opened on Mar 9, 2026

Use case

From the add-to-app instruction: https://docs.flutter.dev/add-to-app/ios/project-setup, under "Use frameworks" section, one of the step is to build the xcframeworks:

flutter build ios-framework --output=/path/to/MyApp/Flutter/

This caused validation failure (#148300) since Apple requires these xcframeworks to be signed.

Our latest effort (#183399) is to sign them using developer's own certs (rather than Flutter LLC) during flutter build ios-framework. However, this seems to defeat the purpose of this new validation - Apple's intention is to ensure these binaries are indeed from trusted sources (i.e. signed by Flutter LLC).

Proposal

Find ways to provide officially code-signed xcframeworks (Flutter.xcframework & plugins), signed by Flutter LLC cert, to add-to-app users.

Activity

  1. hellohuanlin
    added
    toolAffects the "flutter" command-line tool. See also t: labels.
    a: existing-appsIntegration with existing apps via the add-to-app flow
    team-iosOwned by iOS platform team
    on Mar 9, 2026

  2. vashworth commented on Mar 9, 2026

    @vashworth
    vashworth
    on Mar 9, 2026
    Contributor

    This is not possible for plugins since they are built on the user machine. The Flutter.xcframework is already codesigned so I don't think there's anything we can do here that isn't already done. The real solution is that plugins need to adopt SwiftPM, since SwiftPM does not build the plugins into XCFrameworks. Only CocoaPods does that.

  3. vashworth
    closed this as not plannedon Mar 9, 2026

  4. hellohuanlin commented on Mar 9, 2026

    @hellohuanlin
    hellohuanlin
    on Mar 9, 2026
    ContributorAuthor

    Oof, thanks for the details. @vashworth

  5. stuartmorgan-g commented on Mar 10, 2026

    @stuartmorgan-g
    stuartmorgan-g
    on Mar 10, 2026
    Contributor

    The real solution is that plugins need to adopt SwiftPM, since SwiftPM does not build the plugins into XCFrameworks. Only CocoaPods does that.

    Doesn't type: .dynamic still do that? I thought it was just the default build mode that was different for SwiftPM.

  6. github-actions commented on Mar 24, 2026

    @github-actions
    github-actionsBot
    on Mar 24, 2026 – with 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.

  7. github-actions
    locked as resolved and limited conversation to collaborators on Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    a: existing-appsIntegration with existing apps via the add-to-app flowteam-iosOwned by iOS platform teamtoolAffects the "flutter" command-line tool. See also t: labels.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions