Skip to content

ITMS-91065: Missing signature when using plugins on the "privacy-impacting" list in add-to-app #148300

Closed
#183399
Closed
ITMS-91065: Missing signature when using plugins on the "privacy-impacting" list in add-to-app#148300
#183399
Labels
P2Important issues not at the top of the work listcustomer: castawayplatform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

Description

@namtn
namtn
opened on May 14, 2024

Use case

I uploaded my app using: url_launcher to testflight, however Apple rejected it with following reason:

ITMS-91065: Missing signature - Your app includes “Frameworks/url_launcher_ios.framework/url_launcher_ios”, which includes url_launcher_ios, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks.

Proposal

Please help to resolve this issue?

Updated: Version url_launcher: ^6.2.6 and url_launcher_ios in pubspec.lock is: 6.3.0:
url_launcher_ios: dependency: transitive description: name: url_launcher_ios sha256: "7068716403343f6ba4969b4173cbf3b84fc768042124bc2c011e5d782b24fe89" url: "https://pub.dev" source: hosted version: "6.3.0"

Activity

  1. navaronbracke commented on May 14, 2024

    @navaronbracke
    navaronbracke
    on May 14, 2024
    Contributor

    What version of url_launcher_ios does your pubspec.lock indicate? You need version 6.2.4 or higher.

    https://pub.dev/packages/url_launcher_ios/changelog#624

  2. namtn commented on May 14, 2024

    @namtn
    namtn
    on May 14, 2024
    Author

    What version of url_launcher_ios does your pubspec.lock indicate? You need version 6.2.4 or higher.

    https://pub.dev/packages/url_launcher_ios/changelog#624

    Hi navaronbracke:
    I'm using 6.2.5 verion, so 6.2.4 will work?

    Thanks

    url_launcher_ios: dependency: transitive description: name: url_launcher_ios sha256: "9149d493b075ed740901f3ee844a38a00b33116c7c5c10d7fb27df8987fb51d5" url: "https://pub.dev" source: hosted version: "6.2.5"

  3. darshankawar
    added
    in triagePresently being triaged by the triage team
    on May 14, 2024

  4. darshankawar commented on May 14, 2024

    @darshankawar
    darshankawar
    on May 14, 2024
    Member

    @namtn
    This seems to be already addressed as part of #139759 that you can check and confirm.

  5. darshankawar
    added
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    and removed
    in triagePresently being triaged by the triage team
    on May 14, 2024

  6. namtn commented on May 14, 2024

    @namtn
    namtn
    on May 14, 2024
    Author

    @namtn

    This seems to be already addressed as part of #139759 that you can check and confirm.

    @darshankawar I don't really understand how to resolve it.

  7. github-actions
    removed
    waiting for responseThe Flutter team cannot make further progress on this issue until the original reporter responds
    on May 14, 2024

  8. navaronbracke commented on May 14, 2024

    @navaronbracke
    navaronbracke
    on May 14, 2024
    Contributor

    @namtn If you use url_launcher 6.2.6 you should be good. It depends on url_launcher_ios 6.2.4 or higher here https://github.com/flutter/packages/blob/main/packages/url_launcher/url_launcher/pubspec.yaml#L32

    As noted in the url_launcher changelog, that version specifically bumps the version of url_launcher_ios for this exact reason.

  9. namtn commented on May 14, 2024

    @namtn
    namtn
    on May 14, 2024
    Author

    @namtn If you use url_launcher 6.2.6 you should be good. It depends on url_launcher_ios 6.2.4 or higher here https://github.com/flutter/packages/blob/main/packages/url_launcher/url_launcher/pubspec.yaml#L32

    As noted in the url_launcher changelog, that version specifically bumps the version of url_launcher_ios for this exact reason.

    I tried with latest version 6.2.6, however apple still rejected.

  10. navaronbracke commented on May 14, 2024

    @navaronbracke
    navaronbracke
    on May 14, 2024
    Contributor

    Did you do the following as well?

    • delete ios/Podfile.lock
    • flutter clean && flutter pub get
    • cd ios && pod repo update && pod install

    Your pods might have been outdated.

  11. darshankawar
    added
    in triagePresently being triaged by the triage team
    on May 14, 2024

  12. 35 remaining items

  13. samarthagarwal commented on Oct 28, 2024

    @samarthagarwal
    samarthagarwal
    on Oct 28, 2024

    I have been using device_info_plus plugin and I am trying to add xcframeworks to my iOS app and all was working fine until recently when iOS build was rejected immediately after submission with the following message.

    ITMS-91065: Missing signature - Your app includes “Frameworks/device_info_plus.framework/device_info_plus”, which includes device_info_plus, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. If a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a signature file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a signature. For details about verifying the code signature for a third-party SDK, visit: https://developer.apple.com/documentation/xcode/verifying-the-origin-of-your-xcframeworks.

  14. jmagman commented on Oct 28, 2024

    @jmagman
    jmagman
    on Oct 28, 2024
    Member

    Unfortunately you'll have to manually codesign the plugin xcframeworks, we haven't added it to the flutter build ios-frameworks command yet.

  15. samarthagarwal commented on Oct 28, 2024

    @samarthagarwal
    samarthagarwal
    on Oct 28, 2024

    Wouldn't "Embed and Sign" automatically sign the framework during build? Also, my app signing is managed by XCode. How can I sign the framework manually?

  16. diegotori commented on Oct 29, 2024

    @diegotori
    diegotori
    on Oct 29, 2024
    Contributor

    Unfortunately you'll have to manually codesign the plugin xcframeworks, we haven't added it to the flutter build ios-frameworks command yet.

    Do you have a rough timeline as to when that will show up in the next Flutter release, hotfix or full release?

    @stuartmorgan at the very least, I think we should document in the Flutter docs the fact that frameworks may need to be signed, with a snippet of a script that automates this for all non-Flutter frameworks. Seeing that the deadline is fast approaching for iOS apps to submit apps with signed frameworks, a lot of devs will no doubt run into this very same issue.

    Thanks in advance.

  17. diegotori commented on Oct 29, 2024

    @diegotori
    diegotori
    on Oct 29, 2024
    Contributor

    @stuartmorgan In case you need the previously posted bash script properly formatted, that devs can use for signing their iOS frameworks when updating the existing documentation:

    #!/bin/bash

# Path to the output directory containing the built frameworks
OUTPUT_DIR="./Release"

# Path to your codesigning identity
CODESIGN_IDENTITY="Apple Development: My Identity (XXXXXXXXX)"

# Sign each framework
for framework in "$OUTPUT_DIR"/*.xcframework; do
  echo "Signing $framework with identity $CODESIGN_IDENTITY"
  framework_name=$(basename "$framework")

  if [ "$framework_name" != "Flutter.xcframework" ]; then
    echo "Signing $framework with identity $CODESIGN_IDENTITY"
    /usr/bin/codesign --force --sign "$CODESIGN_IDENTITY" "$framework"
  else
    echo "Skipping $framework"
  fi
done

echo "Frameworks signed successfully."
  18. stuartmorgan-g
    marked webview_flutter_wkwebview missing signature - causes "Invalid binary" rejection during App Review #162406 as a duplicate of this issue on Jan 29, 2025
  19. tirth-patel-nc
    marked Missing signatures _CodeSignature folders for third party frameworks #179634 as a duplicate of this issue on Dec 10, 2025

  20. anand-kulk commented on Dec 10, 2025

    @anand-kulk
    anand-kulk
    on Dec 10, 2025

    Hi all, to resolve this issue, I have to signed all frameworks mannually, exclude frameworks has signed by other teams (example Flutter.xcframework):

    1. build ios framework using command: flutter build ios-framework
    2. Run script to sign frameworks:

    #!/bin/bash

    # Path to the output directory containing the built frameworks OUTPUT_DIR="./Release"

    # Path to your codesigning identity CODESIGN_IDENTITY="Apple Development: NamTran (XXXXX7777)"

    # Sign each framework for framework in "$OUTPUT_DIR"/*.xcframework; do echo "Signing $framework with identity $CODESIGN_IDENTITY" framework_name=$(basename "$framework")

    if [ "$framework_name" != "Flutter.xcframework" ]; then echo "Signing $framework with identity $CODESIGN_IDENTITY" /usr/bin/codesign --force --sign "$CODESIGN_IDENTITY" "$framework" else echo "Skipping $framework" fi

    done

    echo "Frameworks signed successfully."

    Thanks for detailed reply @namtn , we are also encountering the same and would try this. Can Flutter team add this code signing part for third parties in the documentation if not already there?

  21. github-merge-queue
    added a commit that references this issue on Mar 18, 2026

    Codesign XCFrameworks for darwin add to app (#183399)

    6df82a9
  22. auto-submit
    closed this as completedin #183399on Mar 18, 2026
  23. mboetger
    added a commit that references this issue on Mar 26, 2026

    Codesign XCFrameworks for darwin add to app (flutter#183399)

    89c3332

  24. github-actions commented on Apr 1, 2026

    @github-actions
    github-actionsbot
    on Apr 1, 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.

  25. github-actions
    locked as resolved and limited conversation to collaborators on Apr 1, 2026
  26. ahmedsameha1
    added a commit that references this issue on Apr 14, 2026

    Codesign XCFrameworks for darwin add to app (flutter#183399)

    45a67ea
  27. Nakiha
    added a commit that references this issue on Sep 28, 2026

    Codesign XCFrameworks for darwin add to app (#183399)

    7263363
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

    P2Important issues not at the top of the work listcustomer: castawayplatform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions