You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pod install fails in ward with and error: CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/Specs/a/a/6/Kingfisher/8.2.0/Kingfisher.podspec.json Response: Error in the HTTP2 framing layer
But succeeds in iTerm etc.
pod install --repo-update
Framework build type is dynamic framework
[Codegen] Generating ./build/generated/ios/React-Codegen.podspec.json
Updating local specs repositories
$ /usr/bin/git -C /Users/klabo/.cocoapods/repos/visualstudio-defaultcollection-_git-cocoapods fetch origin
--progress
remote: Azure Repos
remote: Found 457 objects to send. (1753 ms)
Receiving objects: 100% (457/457), 928.59 KiB | 11.75 MiB/s, done.
Resolving deltas: 100% (233/233), completed with 18 local objects.
From https://msblox.visualstudio.com/DefaultCollection/_git/CocoaPods
79c5ef47bf..a4e745cef0 master -> origin/master
$ /usr/bin/git -C /Users/klabo/.cocoapods/repos/visualstudio-defaultcollection-_git-cocoapods rev-parse
--abbrev-ref HEAD
master
$ /usr/bin/git -C /Users/klabo/.cocoapods/repos/visualstudio-defaultcollection-_git-cocoapods reset --hard
origin/master
HEAD is now at a4e745cef0 [Update] AugloopTypes (0.1.3202)
Analyzing dependencies
[!] CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/Specs/a/a/6/Kingfisher/8.2.0/Kingfisher.podspec.json Response: Error in the HTTP2 framing layer
To reproduce
run pod install on a repo using cdn.cocoapods.org
Expected behavior
It should succeed.
Screenshots
No response
Operating system
MacOS
Operating system and version
macOS 15.2
Shell Version
15.2
Current Warp version
v0.2025.01.29.08.02.stable_03
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Dupe Check
Describe the bug
Pod install fails in ward with and error:
CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/Specs/a/a/6/Kingfisher/8.2.0/Kingfisher.podspec.json Response: Error in the HTTP2 framing layer
But succeeds in iTerm etc.
pod install --repo-update
Framework build type is dynamic framework
[Codegen] Generating ./build/generated/ios/React-Codegen.podspec.json
Updating local specs repositories
$ /usr/bin/git -C /Users/klabo/.cocoapods/repos/visualstudio-defaultcollection-_git-cocoapods fetch origin
--progress
remote: Azure Repos
remote: Found 457 objects to send. (1753 ms)
Receiving objects: 100% (457/457), 928.59 KiB | 11.75 MiB/s, done.
Resolving deltas: 100% (233/233), completed with 18 local objects.
From https://msblox.visualstudio.com/DefaultCollection/_git/CocoaPods
79c5ef47bf..a4e745cef0 master -> origin/master
$ /usr/bin/git -C /Users/klabo/.cocoapods/repos/visualstudio-defaultcollection-_git-cocoapods rev-parse
--abbrev-ref HEAD
master
$ /usr/bin/git -C /Users/klabo/.cocoapods/repos/visualstudio-defaultcollection-_git-cocoapods reset --hard
origin/master
HEAD is now at a4e745cef0 [Update] AugloopTypes (0.1.3202)
Analyzing dependencies
[!] CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/Specs/a/a/6/Kingfisher/8.2.0/Kingfisher.podspec.json Response: Error in the HTTP2 framing layer
To reproduce
run pod install on a repo using cdn.cocoapods.org
Expected behavior
It should succeed.
Screenshots
No response
Operating system
MacOS
Operating system and version
macOS 15.2
Shell Version
15.2
Current Warp version
v0.2025.01.29.08.02.stable_03
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
The text was updated successfully, but these errors were encountered: