-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod official page redirected to homepage/github source page #457
Comments
We have the same issue for several pods, some listed in #390 - and https://cocoapods.org/pods/NabtoEdgeClientSwift, https://cocoapods.org/pods/NabtoEdgeClientApi. |
We are facing the same issue as well https://cocoapods.org/pods/OTXCFramework . |
Same is happening with https://cocoapods.org/pods/RevenueCat:
This looks like a bug? |
Any updates on this issue? We are seeing a similar problem for our project. |
This is the root cause: https://github.com/CocoaPods/cocoapods.org/blob/master/app.rb#L114-L124 Essentially, if Cocoapods is not able to fetch the Github metrics (stargazers, etc) for whatever reason, it will simply redirect to the pod's homepage. As far as I can tell, these metrics are no longer displayed anywhere in the Cocoapods pages, so ideally this check would simply be removed, as well as the metrics fetch/anything depending on it. I could be wrong about this still being in use though. |
The metrics in this case also includes things like the rendered readme/changelog, so there wouldn't be anything to render without that info! Those are generated by https://github.com/CocoaPods/cocoapods-metadata-service - so maybe the issue lays there |
@orta looks like CocoaPods/cocoapods-metadata-service#24 might have been the fix? 🙏🏻 |
Yeah, it looks like about 20 times a day we hit this in the logs too:
so maybe not completely done |
Hi, one of our pod (https://cocoapods.org/pods/BoringSSL-GRPC) is always redirected to its homepage URL instead of landing on the official pod page on cocoapod. I noticed there are a number of similar reports having the same issues
#448
#443
Appreciate if anyone can help look into it
The text was updated successfully, but these errors were encountered: