11 days ago
Alamofire

5.12.0

Released on 2026-05-04. All issues associated with this milestone can be found using this filter.

Added

  • FreeBSD compilation support.

Updated

  • Various CI configurations.

Fixed

  • Rare race in Request.suspend() and Request.cancel() where the state update would be lost if it occurred before the task was created.
  • Request.cancel() incorrect called Request.finish() when the underlying task was already .completed.
  • Rare race in Request.resume() that could lead to multiple URLSessionTasks created.
  • Repeated calls to Request.suspend() and Request.resume() could lead to multiple pipeline executions.
  • Thread-safety issue in Session.deinit when accessing internal state.
  • Rare Request.finish() race in Session.deinit.
  • Session.deinit called Request.finish() on Requests that were already finished.
  • Request.onHTTPRequest didn't call the full Request.cancel() when the .cancel disposition was returned.
  • Multiple unlikely force unwrap or unowned self crashes.
  • Write to DataStreamRequest's outputStream after it was closed.
  • MIME type parsing, where a single element (text) or empty strings would be accepted.
  • Cancelled DownloadRequests could still trigger retry.
  • DataRequest.DataTask and DownloadRequest.DownloadTask could miss early cancellation events if they happened before the underlying Task was created.
  • 🔥 Multiple issues in AuthenticationInterceptor. These fixes slightly change the interceptor's behavior.
    1. adapt() enqueued adaptations, leading to requests restarted with a new credential to not execute the whole adapt pipeline again. AuthenticationInterceptor will now let those requests fail with the old credential and retry their whole pipeline with the new credential.
    2. Concurrent adaptations for the same stale credential could trigger multiple refreshes.
    3. retry() now lazily checks for new credentials rather than capturing eagerly.
17 days ago
CYLTabBarController

已支持 Lottie 的依赖最新版本, 支持指定渲染模式

CYLTabBarController 1.99.20以上版本,已对 Lottie 的依赖版本, 进一步细化, 采用二分法: ObjC 和Swift版本,进行区分。ObjC指定 ~>2.5.3 , Swift版本指定>=4.0.0。CYLTabBarController 内部 , 可以根据依赖版本的不同,执行不同逻辑。同时保持API接口不变。

用法见GitHub Demo演示。

#pod 'CYLTabBarController', '~> 1.99.20'        # 默认不依赖Lottie
#pod 'CYLTabBarController/LottieObjectiveC', '~> 1.99.20'  # 依赖Lottie Objective-C库
#pod 'CYLTabBarController/LottieSwift', '~> 1.99.20'  # 依赖Lottie Swift库

 

自我评估,已经可以满足大部分场景, 如需要更精细的 Lottie 版本区分, 请提issue, 描述清楚场景, 我排期开发。

注意LottieSwift支持的iOS版本最低为iOS13

s.ios.deployment_target = '13.0'

如果你的项目支持iOS12则不能使用Lottie Swift 版本。

你在选择时应该遵循这样的规则: Lottie OC版本仅在需要支持iOS12时引入,如果你的项目最低版本高于或等于iOS13那么你应该总是选择LottieSwift。

Lottie OC 对支持Lottie文件的暗黑模式有bug. 不再建议使用。

另外提一句, iOS26 未选中状态下的Label颜色,一直是总是 labelColor 也就是黑色或者白色, 无法通过appearance 自定义, 怀疑是Apple的bug, 或者是一个功能, 为了提高未选中时的辨识度。我没想到好的方案进行修复,调研了一下, 似乎大家都接受了这个bug? 如果你有好的方案,请提issue,社交媒体给我的留言,无法保证看见并回复。 issue为唯一反馈途径,谢谢理解。


添加接口lottie动画的渲染模式可以从外部指定 (默认渲染模式是fit) 增加didLayoutSubViewsBlock, 扩大PlusButton可点击面积, 解决iOS15有时候tabbar会变透明的问题;([bug]:iOS15在切换到某些vc后有可能出现TabBar变透明的情况 #574) reloadTabBarItemsWithAttributes; (关联 issue 动态更新 tabbarItem 的 icon 跟 title #303)

23 days ago
CryptoSwift

1.10.0

  • Add a ChaCha20 initializer with explicit 4-byte counter support and QUIC test vectors
  • Fix XChaCha20-Poly1305 nonce length metadata to require 24-byte nonces
  • Make the privacy manifest Apple-only via a dedicated resources target and add visionOS/macCatalyst support
  • Prefer FoundationEssentials when available, with Foundation fallback for compatibility
  • Fix Scrypt and SecureBytes memory handling to avoid unsafe baseAddress crashes and release allocated memory correctly
25 days ago
KSCrash

2.6.0-beta.1

[!NOTE] Please review this page in the wiki for a deeper dive into all the changes.

[!NOTE] We're naming this v2.6.0 to be clear that we expect it to be 100% compatible, non-source breaking with v2.5.1. Please report any issues you may find.

What's Changed

Full Changelog: https://github.com/kstenerud/KSCrash/compare/2.5.0...2.6.0-beta.1

2026-04-12 17:28:19
CYLTabBarController

CYLTabBarController 现已支持 iOS26 上实现以下效果, 请更新至版本1.99.4以上版本:



Preview of latest version

Preview of the latest version 1.99.4 on iOS 26+

CYLTabBarController 现已支持 iOS26 上实现以下效果, 请更新至版本1.99.3以上版本:

  • ✅同时展示 Lottie动画与液态玻璃效果;
  • ✅支持将加号➕按钮,展示在液态玻璃效果上,并居中展示。保留 CYLTabBarController 旧版本的所有加号按钮逻辑。仅增加玻璃遮罩效果;
  • ✅未使用私有API实现液态玻璃,可通过代码静态扫描,Apple 审核过审安全;
  • ✅采用纯原生的液态玻璃效果,支持 iOS 系统设置对液态玻璃属性的全部修改操作;
  • ✅企业生产环境级别开源解决方案;
  • ✅对于已经集成 CYLTabBarController 的开发者友好,升级适配开发难度, 代码修改低于10行,升级总时长低于1小时;
  • ✅不依赖UI兼容模式, iOS27 过审友好;
  • ✅不依赖UI兼容模式, 实现扁平风格UI, iOS27 过审友好;

即刻访问 这里 ,了解更多:

Image Image Image Image Image

2026-04-06 11:13:06
Alamofire

5.11.2

Updated

  • Use of #file to #fileID to prevent build system info leakage.
  • CI and dependencies.

Fixed

  • A rare race between the creation of StreamOf values and the start of their iteration, which could miss values.
  • Handling of duplicate URLSessionTaskMetrics callbacks, likely caused by using the new loading system (usesClassicLoadingMode = false).
2026-02-26 15:37:19
SDWebImage

5.21.7 - 5.21 Patch

See all tickets marked for the 5.21.7 release

Fixes

  • Fix AppKit SDImageCoderHelper does not use APNG instead of GIF for animated image creation #3870 #3871 @ijunfly
2026-02-23 09:34:50
realm-cocoa

v20.0.4

  • Update build scripts for Xcode 26.
  • Drop support for Xcode < 26.
  • Prebuilt binaries are no longer code signed as Realm is no longer officially distributed by MongoDB.
  • Fix compilation with Xcode 26.4.

Compatibility

  • Carthage release for Swift is built with Xcode 26.3.
  • CocoaPods: 1.10 or later.
  • Xcode: 26.1-26.4
2026-02-23 09:34:50
realm-swift

v20.0.4

  • Update build scripts for Xcode 26.
  • Drop support for Xcode < 26.
  • Prebuilt binaries are no longer code signed as Realm is no longer officially distributed by MongoDB.
  • Fix compilation with Xcode 26.4.

Compatibility

  • Carthage release for Swift is built with Xcode 26.3.
  • CocoaPods: 1.10 or later.
  • Xcode: 26.1-26.4
2026-02-13 22:21:02
SKPhotoBrowser

7.1.1

[!WARNING] Please use 7.1.1(this version) instead of 7.1.0. There are some tagging issues happened when release 7.1.0.

What's Changed

  • Fix a problem where latest tag commit is overlapped with previous tag commit by mistake.