You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 51e9568
Browse filesBrowse the repository at this point in the historyBrowse files
* ios: consume the Flutter module as a Swift package (build swift-package)
flutter build ios-framework forces CocoaPods and skips podspec-less
plugins, so it cannot build SwiftPM-only plugins like adapty_flutter 4.x.
Switch the module build to `flutter build swift-package` and the host
project from 12 hardcoded xcframework refs to one local
FlutterNativeIntegration package dependency (per-target product + Flutter
Assemble build phase; per-scheme prebuild pre-action flips the
Debug/Release symlink). The mocked simulator flow builds the same package
with its dart-defines. sign-ios-frameworks now signs the prebuilt
third-party xcframeworks under the package's Frameworks/ dirs; plugins
vended as source packages no longer need ITMS-91065 origin signatures.
Drops the unreferenced legacy common/scripts/build.for.ios.sh.
Not buildable standalone: adapty_flutter 3.17.1 ships podspec+Package.swift
and the module pods pass collides with the plugin's remote AdaptySDK-iOS
targets; resolved by the 4.0.3 bump in the next commit (PR squash-merges).
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* deps: migrate Adapty SDK to 4.0 (Paywall → Flow) across Dart and Android
Coupled bump: adapty_flutter 4.0.3 (pub) + io.adapty:adapty-bom 4.0.1
(gradle) — the Flutter plugin pins the native BOM major internally, so
neither can move alone (supersedes #1199/#1201).
Dart (adapty.dart): Flow renames; setFallbackPaywalls → setFallback;
locale moves from getFlow (deprecated no-op) to createFlowView, else
flows silently render English; paywallViewDidFailRendering folds into the
mandatory flowViewDidReceiveError (kept log-only); flowViewDidDisappear
now drops the cached view — 4.0 releases dismissed views, and swipe-down
bypasses closePaymentScreen, so a spent view could otherwise be
re-presented. AndroidSystemBackAction handling kept (4.0 stopped
dismissing on back by default).
Kotlin (six flavor): Flow renames; locale moves to getFlowConfiguration;
PaymentBinding now extends AdaptyFlowDefaultEventListener so 4.0's new
analytics/app-rate/permission flow actions keep SDK default behaviour;
onBackPressed returns false to preserve the 3.x back-dismissal via the
dialog fragment; prorate-on-upgrade purchase params unchanged.
adapty_flutter is vendored (minus example/) under common/vendor with two
patches: a stub podspec — Flutter modules still force a CocoaPods pass
(flutter/flutter#184590) whose generated registrant pod hard-depends on
every plugin, and 4.x ships no podspec — and a Swift typealias for the
pubspec pluginClass, which upstream only exposes as an @objc name so the
generated Swift registrant fails to compile (report to Adapty). The
fallback-version CI script now also enforces pin == vendored version.
Fallback files are still format v9 and MUST be replaced with v10 exports
before release: SDK 4.x rejects v9 at cold start (error 2006) and the
failure is swallowed into paymentTempUnavailable.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* build(ios): sign script tolerates zero prebuilt plugin xcframeworks
Since Adapty 4 every plugin is a Swift source package, so the package's
Frameworks dir holds only the excluded Flutter/App bundles and the
zero-signed case is legitimate, not a broken build.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* fix(payment): address code-review findings on the Adapty 4 migration
- flowViewDidDisappear now resets the PaymentActor when a dismissal
bypassed closePaymentScreen (swipe-down, flow-internal close) — without
it _isOpened stayed true and the paywall could never reopen. A
dismissing-view marker keeps app-initiated closes reporting their own
isError without double-notifying.
- closePaymentScreen only invalidates the cached view when it is the one
being dismissed, so a fresh preload for another placement survives;
cache clearing deduplicated into _dropCachedView().
- Scheme surgery had MOVED each Build entry's BuildableReference into the
new pre-action instead of copying it, leaving Build actions empty —
restored in all 8 schemes.
- sign-ios-frameworks discovers xcframeworks recursively so a prebuilt
bundle in a new layout cannot silently skip ITMS-91065 signing.
- Fallback-version guard: vendor dir added to the workflow paths filter,
stub podspec version pulled into the lockstep check, pubspec pin regex
made order/indentation-proof.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* test(appium): wait for a stable frame before the paywall golden compare
The smoke run on Adapty 4 failed the paywall golden with 12% diff: the
screenshot caught the flow mid-presentation (content shifted by the
status-bar height, bar transiently hidden during the modal handoff),
while the settled frame — visible in the failure screenshot taken
moments later — matches the golden exactly. The fixed 4s pause was tuned
to the 3.x renderer's timing; the 4.0 flow runtime settles later.
Replace it with waitForStableScreen(): consecutive top-masked frames
compared until quiescent, so the timing never needs re-tuning. No regold
needed — the steady-state render is unchanged.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* test(appium): retry the paywall golden compare until the flow settles
The stable-frame wait latched onto the wrong state: the Adapty 4 flow
holds a stable intermediate layout for several seconds (content shifted
by the status-bar height — identical 12.14% diff across runs) before its
final reflow, so quiescence cannot distinguish the plateau from the
settled screen. compareToGolden gains retries/retryDelayMs and the spec
retries the comparison itself; only a frame that never matches fails.
Supersedes waitForStableScreen, removed.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* fix(payment): pin AdaptySDK-iOS to blokadaorg fork with footer-gate patch
The 4.x decorator rewrite dropped the includeBackground opacity gate on
static backgrounds, so the paywall's translucent footer scrim
(#000000BF, meant to appear only when content scrolls beneath the
footer) is painted unconditionally — rgb(57) → rgb(14) on the footer
band, breaking the design's scroll-under translucency. No legacy or
compat renderer exists in 4.0 (format<4.8 paywalls are decoded into a
synthetic single-screen flow), so the vendored plugin's Package.swift
now pins blokadaorg/AdaptySDK-iOS @ caf82a13 — tag 4.0.2 plus one
commit restoring the gate (branch
blokada/4.0.2-footer-include-background-gate). Return to the upstream
exact-4.x pin when Adapty ships the fix.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* chore(payment): refresh Adapty fallback paywalls to format v10
SDK 4 rejects the bundled v9 fallbacks at cold start (error 2006,
swallowed into paymentTempUnavailable), so offline cold-start paywalls
were broken until this lands. Fresh dashboard exports (all 7 placements)
installed into all three bundled copies via make adapty-paywalls;
ADAPTY_VER now matches the 4_0_0 export filenames and the CI guard
requires v10.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
* fix(payment): pass bare language codes to the Adapty 4 localization lookup
Device sign-off caught the paywall rendering English on a Spanish
device. Adapty 4 resolves the view locale client-side with an EXACT
dictionary lookup against the dashboard localization ids (bare language
codes: en, es, de, ...) — AdaptyUISchema+localization.swift has no
language-prefix fallback, unlike the lenient 3.x fetch-time matching.
Our region-tagged values (Dart I18n.localeStr = es_es, Android
toLanguageTag = es-ES) therefore missed and silently fell back to the
default (English). Pass I18n.languageOnly on the Dart path and the
language subtag on the native Android path.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Bwp4PT4b6f87avSxEbgqNH
---------
Co-authored-by: Claude Fable 5 <[email protected]>
0 commit comments