README is not up to date

[iliescu-Andrei]

• I've read and understood the CONTRIBUTING guidelines and have done my best effort to follow.

Report

What did you do?

I updated our Pod at: https://cocoapods.org/pods/ZeroBounceSDK 5 days ago, but even though the version is up to date, the README is an old file. I even added the readme specifically in the podspec, changed it to another .md file and the README shown on CocoaPods site is still the old file. The readme argument seems to be ignored. This is happening since 2-3 versions ago (same outaded file is shown even though the README has changed multiple times).

What did you expect to happen?

Update the pod README on cocoapods.org to match the one on the github release.

What happened instead?

The readme on cocoapods.org is different than the updated readme.

CocoaPods Environment

Stack

   CocoaPods : 1.12.1
        Ruby : ruby 3.2.2 (2023-03-30 revision e51014f9c0) [arm64-darwin22]
    RubyGems : 3.4.10
        Host : macOS 13.5.1 (22G90)
       Xcode : 14.3.1 (14E300c)
         Git : git version 2.39.2 (Apple Git-143)
Ruby lib dir : /opt/homebrew/Cellar/ruby/3.2.2_1/lib
Repositories : trunk - CDN - https://cdn.cocoapods.org/

Installation Source

Executable Path: /opt/homebrew/Cellar/cocoapods/1.12.1/libexec/bin/pod

Plugins

cocoapods-deintegrate : 1.0.5
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.1
cocoapods-trunk       : 1.6.0
cocoapods-try         : 1.2.0

Podfile

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'Zero Bounce iOS SDK' do
  # Comment the next line if you don't want to use dynamic frameworks
  use_frameworks!

  # Pods for Zero Bounce iOS SDK

  target 'Zero Bounce iOS SDKTests' do
    inherit! :search_paths
    # Pods for testing
    pod 'Mocker', '~> 2.5.4'
  end

end

Project that demonstrates the issue

https://github.com/zerobounce/zero-bounce-ios-sdk/tree/0.1.7

[iDevelopper]

Same issue!

[cloverdaniel]

Did you ever figure this out? Seeing the same thing...

[iliescu-Andrei]

@cloverdaniel Unfortunately, no. The problem persists :(