Skip to content
Discussion options

You must be logged in to vote

Hello @vulv-nals,
A fix for this was released yesterday - rails/rails#54260
Kindly try running this build again. If this issue persists, please temporarily roll back the CocoaPods version to 1.13.0 to solve the problem

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Answer selected by dam-ease
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
2 participants