Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

Bug --notarize-app is missing one or more required options: --asc-provider.

Discussion in 'Unity Build Automation' started by Visartech, Oct 6, 2022.

  1. Visartech

    Visartech

    Joined:
    Aug 10, 2012
    Posts:
    31
    Our team using Unity Cloud to build Mac standalone app and also sign application.
    We have credentials to sign application and it was works fine 2 month ago.

    App signature stopped working about 2 months ago, it seems at the beginning of August, maybe after August 17.
    And after ~August 17 we got failed build on notarization steps:


    Code (CSharp):
    1. 41621: <?xml version="1.0" encoding="UTF-8"?>
    2. 41622: <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    3. 41623: <plist version="1.0">
    4. 41624: <dict>
    5. 41625:     <key>os-version</key>
    6. 41626:     <string>11.6.2</string>
    7. 41627:     <key>product-errors</key>
    8. 41628:     <array>
    9. 41629:         <dict>
    10. 41630:             <key>code</key>
    11. 41631:             <integer>-1027</integer>
    12. 41632:             <key>message</key>
    13. 41633:             <string>Unable to upload your app for notarization.</string>
    14. 41634:             <key>userInfo</key>
    15. 41635:             <dict>
    16. 41636:                 <key>NSLocalizedDescription</key>
    17. 41637:                 <string>Unable to upload your app for notarization.</string>
    18. 41638:                 <key>NSLocalizedFailureReason</key>
    19. 41639:                 <string>--notarize-app is missing one or more required options: --asc-provider.</string>
    20. 41640:             </dict>
    21. 41641:         </dict>
    22. 41642:     </array>
    23. 41643:     <key>tool-path</key>
    24. 41644:     <string>/APPLICATION_PATH/Xcode13_2_1.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/Frameworks/AppStoreService.framework</string>
    25. 41645:     <key>tool-version</key>
    26. 41646:     <string>4.071.1221</string>
    27. 41647: </dict>
    28. 41648: </plist>

    Fastlane xcode command:
    Code (CSharp):
    1. /BUILD_PATH/.rvm/gems/ruby-2.7.4/gems/fastlane-2.208.0/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': Exit status of command 'xcrun altool --notarize-app -t osx -f "/BUILD_PATH/<project_name>.mac64notarization/.build/last/mac64notarization/EM.app.zip" --primary-bundle-id <BUILD_ID> --output-format xml -u <USER_EMAIL> -p @env:FL_NOTARIZE_PASSWORD' was 1 instead of 0. (FastlaneCore::Interface::FastlaneShellError)
    As I found in xcode documentation I know that --asc-provider flag is required when pass --notarization-app and this understandable from error.

    Why Unity Cloud and Fastlane don't pass --asc-provider ?

    In Credentials we have filled field Provider Short Name
     
    Last edited: Oct 6, 2022
    Visartech, Oct 6, 2022
    #1

  2. phuong_unity

    phuong_unity

    Unity Technologies

    Joined:
    Apr 25, 2018
    Posts:
    52
    Hi @Visartech. It's possible the credentials used for your project are associated with more than one team which would require the asc-provider flag to be passed to the notarization call. In order for the Cloud Build team to investigate this issue further, could you open a support ticket and include the link to this forum post?
     
    phuong_unity, Oct 11, 2022
    #2

  3. Visartech

    Visartech

    Joined:
    Aug 10, 2012
    Posts:
    31
    Sure
     
    Visartech, Oct 12, 2022
    #3
    phuong_unity likes this.