Skip to content

Version 2.3.0 Release - #71

Merged
ZweWaiYanHtet merged 1 commit into
masterfrom
version/2.3.0
Sep 29, 2026
Merged

ZweWaiYanHtet merged 1 commit into
masterfrom
version/2.3.0

Conversation

@ZweWaiYanHtet

Copy link
Copy Markdown
Contributor

Adopts the newly published iOS Pokepay 2.3.0 and bumps the plugin to 2.3.0.

Why

Pokepay 2.3.0 (pokepay/ios-sdk#128) raised its minimum deployment target to iOS 15.0, because Xcode 26 and later refuse to build anything below that, and dropped the dead antitypical/Result dependency.

Changes

  • ios/pokepay_sdk.podspec — Pokepay 2.2.1 → 2.3.0, s.platform 12.0 → 15.0, version → 2.3.0.
  • ios/Classes/SwiftPokepaySdkPlugin.swift — dropped import Result. Required, not cosmetic: the pod is no longer in the dependency graph, so the import would not compile. The Result values the plugin handles are the standard library's, which is what that package had resolved to since Swift 5 anyway. No Dart-facing API changed.
  • README.md — new Requirements + iOS setup section.
  • .github/workflows/ci.yml — the ios-build job applies the same setup to the example app it generates.
  • pubspec.yaml / CHANGELOG.md — 2.3.0.

⚠️ Action required by consuming apps

platform :ios, '15.0' alone is not enough. Every app embedding this plugin also needs a post_install hook — the first verification build failed on two pods, not one:

error: IPHONEOS_DEPLOYMENT_TARGET is set to 11.0 ... (in target 'Flutter')
error: IPHONEOS_DEPLOYMENT_TARGET is set to 9.0  ... (in target 'APIKit')

APIKit (transitive, last released 2021) declares iOS 9.0 and Flutter's own pod declares 11.0. The hook must run after flutter_additional_ios_build_settings(target), which resets the setting:

platform :ios, '15.0'

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    target.build_configurations.each do |config|
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '15.0'
    end
  end
end

The Runner target's own minimum deployment must be 15.0 too. All of this is in the README.

Verification

Generated a throwaway Flutter app, added the plugin by path, and resolved against the published pod (no local overrides, Pods/ and Podfile.lock deleted first):

PODS:
  - APIKit (5.4.0)
  - Flutter (1.0.0)
  - Pokepay (2.3.0):
    - APIKit (~> 5.4.0)
  - pokepay_sdk (2.3.0):
    - Flutter
    - Pokepay (= 2.3.0)

No Result pod, and xcodebuild -target pokepay_sdk → ** BUILD SUCCEEDED **.

Notes

  • Android pokepaylib stays at 2.2.0 — unchanged, as in the 2.2.1 and 2.2.2 releases.
  • Minor rather than patch: raising the iOS floor to 15.0 is breaking for apps still supporting iOS 12–14.

🤖 Generated with Claude Code

The native Pokepay pod raised its minimum deployment target to iOS 15.0
in 2.3.0, because Xcode 26 and later refuse to build anything below it.

- Bump the pod dependency to Pokepay 2.3.0 and raise s.platform to 15.0.
- Drop `import Result` from SwiftPokepaySdkPlugin. Pokepay 2.3.0 removed
  its antitypical/Result dependency, so the pod is no longer installed
  and the import would not compile. The `Result` values the plugin
  handles are the standard library's, which is what that package had
  resolved to since Swift 5 anyway. No Dart-facing API changed.
- Document the iOS setup consuming apps now need: `platform :ios, '15.0'`
  plus a post_install hook raising IPHONEOS_DEPLOYMENT_TARGET for every
  pod. The hook is not optional -- APIKit declares iOS 9.0 and the
  Flutter pod declares 11.0, and both fail the build without it. It must
  run after flutter_additional_ios_build_settings, which resets it.
- Apply the same setup to the example app the ios-build CI job generates.

Verified against the published pod: a generated Flutter app resolves
APIKit 5.4.0 / Pokepay 2.3.0 / pokepay_sdk 2.3.0 with no Result pod, and
the plugin target builds.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@taniryo-kun taniryo-kun left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ZweWaiYanHtet
ZweWaiYanHtet merged commit 7afcd2c into master Sep 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants