Skip to content

Mac plugin_lint_mac failing: Couldn't determine repo type for URL: https://cdn.cocoapods.org//: certificate verify failed (unable to get local issuer certificate) #112130

Closed

Description

@jmagman
[plugin_lint_mac] [STDOUT] Flutter root at /opt/s/w/ir/x/w/recipe_cleanup/tmpba8j6fab/flutter sdk
[plugin_lint_mac] [STDOUT] Executing "pod lib lint /opt/s/w/ir/x/w/recipe_cleanup/tmpba8j6fab/flutter sdk/packages/integration_test/ios/integration_test.podspec --use-libraries --verbose" in "/opt/s/w/ir/x/t/flutter_plugin_test.2mLq07" with environment {BOT: true, LANG: en_US.UTF-8}
[plugin_lint_mac] [STDOUT] stdout: 
[plugin_lint_mac] [STDOUT] stdout: [!] Couldn't determine repo type for URL: `https://cdn.cocoapods.org//`: SSL_connect returned=1 errno=0 peeraddr=172.67.74.167:443 state=error: certificate verify failed (unable to get local issuer certificate)
[plugin_lint_mac] [STDOUT] stdout:

https://ci.chromium.org/p/flutter/builders/prod/Mac%20plugin_lint_mac/8945

Tree closed.

Activity

  1. added
    team-infraOwned by Infrastructure team
    P0Critical issues such as a build break or regression
    on Sep 22, 2022
  2. jmagman commented on Sep 22, 2022

    @jmagman
    MemberAuthor

    Failures seem to be happening only on arm hosts, maybe related to #109889, though plugin_lint_mac did pass on an arm machine on that PR in presubmit.

    https://status.cocoapods.org/ doesn't report any issues, not sure why there would be a cert failure.

  3. self-assigned this
    on Sep 22, 2022
  4. jmagman commented on Sep 22, 2022

    @jmagman
    MemberAuthor

    #112133 merged, that should reopen the tree, and then this priority can be lowered.

    Still need to figure out what's up with the ssl certs on these machines.

  5. jmagman commented on Sep 22, 2022

    @jmagman
    MemberAuthor

    Tree is green, reducing priority.

  6. added
    P1High-priority issues at the top of the work list
    and removed
    P0Critical issues such as a build break or regression
    on Sep 22, 2022
  7. removed their assignment
    on Sep 22, 2022
  8. keyonghan commented on Sep 22, 2022

    @keyonghan
    Contributor

    There are two issues with Mac plugin_lint_mac:

    1. fails on arm64 bots (the certificate verify failure)
    2. flake on x64 bots. Created Mac plugin_lint_mac is flaky with incorrect FlutterMacOS.framework architecture #112146 to track

    As for 1), the builder succeeds in try pool, but fails in prod pool. Filed https://crbug.com/1366657 to see if any differences between these two pools.

  9. keyonghan commented on Nov 1, 2022

    @keyonghan
    Contributor

    All try and prod bots are configured the same without any difference: https://crbug.com/1366657.

    Will rerun LED builds to confirm the issue is still reproducible before asking to reinstall prod bots.
    (LED runs on arm64 bots are currently blocked on #113231)

  10. godofredoc commented on Dec 14, 2022

    @godofredoc
    Contributor
  11. StillOnMyWay commented on Dec 26, 2022

    @StillOnMyWay

    Experiencing the same.

    arm based Mac Metal 2 (M1 chip) EC2 INSTANCE. Pod install output in the terminal producing couldn't determine repo type for url: https://cdn.cocoapods.org/`: ssl_connect returned=1 errno=0 peeraddr=172.67.74.167:443 state=error: certificate verify failed (unable to get local issuer certificate)`

  12. godofredoc commented on Jan 13, 2023

    @godofredoc
    Contributor

    @StillOnMyWay this is caused by your version of ruby not being able to find the cacerts.pem. I'd recommend to uninstall/install your system's ruby and ensure that it takes precedence over the one bundle with xcode.

  13. godofredoc commented on Jan 13, 2023

    @godofredoc
    Contributor

    Fixed with hermetic ruby bundles and https://flutter-review.googlesource.com/c/recipes/+/38088.

  14. jmagman commented on Jan 13, 2023

    @jmagman
    MemberAuthor

    Thank you!

  15. github-actions commented on Mar 4, 2023

    @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.

  16. locked as resolved and limited conversation to collaborators on Mar 4, 2023
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

    P1High-priority issues at the top of the work listteam-infraOwned by Infrastructure team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions