Skip to content

Releases

v1.1.1-beta.5

v1.1.1-beta.5 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 03 Nov 11:37

Added — the Superwall bridge ships

  • BillDogSuperwallIntegration (SuperwallBillDogPurchaseController, a SuperwallKit 4.x PurchaseController backed by BillDog) is published for the first time: SwiftPM https://github.com/billdogai/billdog-ios-superwall.git (product BillDogSuperwallIntegration, exact BillDog version) and the BillDogSuperwallIntegration pod. It is a separate package because SwiftPM fetches every dependency a package declares, so SuperwallKit in billdog-ios-spm would download into every BillDog app; apps that don't add it are unaffected. Only the bridge's two Swift files ship as source, built with the app against the SuperwallKit it resolves; the SDK stays the binary BillDogFull, pinned at the same version. SuperwallKit range: 4.0.3 and later 4.x (4.0.0–4.0.2 named the event type SuperwallPlacementInfo); Xcode 26 compiles SuperwallKit 4.14.0 and later only. Built against 4.18.3, whose PurchaseController is unchanged since 4.0.0.

Fixed — analytics batches name the SDK that sent them

  • Each ingest batch carries lib / lib_version (PostHog's $lib / $lib_version): billdog-ios at the SDK version, or the wrapper that runs it (billdog-flutter, billdog-react-native, billdog-expo, …, from BillDogRuntime.platformInfo) at the wrapper's version. Native rows were stored with no lib, so their event_source was 'other' instead of 'mobile'.

Fixed — analytics flushes when the app goes to the background

  • The queue is flushed on didEnterBackground (server flush_on_background, default on) and on willTerminate (flush_on_close), and the background sync is scheduled, whether or not session auto-tracking runs. Both lived in the session tracker, which is off by default, so an app on defaults sent what it tracked last only at its next launch (measured on device: 60–90 s+ late; with the fix, 1 s after Home). posthog-ios flushes on every didEnterBackground the same way.

Added — session replay for the wrappers

  • BillDogReplayOptions.externalFrames and BillDog.shared.replay.appendExternalFrame(_:): a recording whose frames the host draws and masks itself (the Flutter SDK), encoded and uploaded like screenshots.
  • BillDogReplayOptions.maskAllInputs (default true): text fields stay covered when maskAllText is off.
  • React Native text views (RCTParagraphComponentView, RCTTextView) are masked as text by both recorders.

Changed (round 3 platform parity)

  • The web-checkout return scheme is app-specific. WebCheckoutManager.customUrlScheme (and the new BillDogConfig.customUrlScheme) default to <bundle id>.billdog (CheckoutURLScheme) instead of the billdog every app shared — iOS picks one app when two register a scheme, so a return or redeem link (a bearer token) could open another BillDog app. An app whose CFBundleURLTypes still list only billdog keeps using it (logged) until it adds its own; incoming billdog:// links stay accepted in default mode. A scheme the host sets is the only one claimed.
  • One consent path. ConsentManager posts didChangeNotification after every write, and BillDog drops its kept placement answers on it, so a per-purpose grant, a module's own consent setter or a wrapper calling ConsentManager directly (React Native did) has the same effect as setConsentGiven. New facade calls setConsent(for:granted:) / hasConsent(for:) (Android parity).

Deprecated (could never work; no longer offered by any wrapper)

  • BillDogVirtualCurrencyManager.addBalance, deductBalance, grantCurrency, exchangeCurrency and resetBalance throw BillDogError.configurationError at once, without a request. Every wallet write needs the project's secret key and the server answers an app's publishable key 403, so they failed on every device (/exchange is retired server-side, and RESET is no transaction type). Virtual currencies are read-only in the client, as in RevenueCat: credit and spend from your server (POST /v1/virtual-currency/transactions or /adjustments). getBalance and getTransactionHistory(currencyId:) take a currency code as well as its id. Android: the same.
  • BillDogNotificationsManager.addTag / addTags / removeTag / removeTags / getTags, the alias calls, addEmail / removeEmail / getEmails and addSms / removeSms / getSmsNumbers are no-ops that log one warning; the getters return nothing. They kept their values in memory and never sent them. Tags, email and phone are contact fields only your server may write (sync-subscriber, secret key); an alias is logIn(appUserId). Android: the same.

Added

  • PaywallPresentationHandler.onOAuthSuccess (public, also an init parameter) with a public PaywallSignIn (provider, user, email, ID token): the paywall closed after a sign-in made on it that the server verified, with no purchase or restore. Called just before onDismiss, from presentPaywall and from register(placementId:from:params:presentationHandler:), which reported that close as a plain dismissal. Same shape as Android.

  • BillDogEngSDK.logIn(_:), identify(userId:), logOut() and appUserId: an engagement-only app can identify its user. Push opt-in and notification revalidation, in-app messages, A/B tests and feature flags, and store recording (the purchase's claimant, storeAccountToken) used to stay anonymous in BillDogEng, because only the Full facade's logIn set the identified user. logOut() leaves the install on a new guest, drops the modules' user-scoped state (flags and assignments, in-app triggers, balances, push tags) and resets analytics; a BillDog Auth sign-out in BillDogEng does the same. The identity rules both products share are in BillDogIdentity (BillDogCore). Android's billdog-eng has these through billdog-core.

  • Social sign-in (OAuthManager, OAuthResult, OAuthProvider, the hosted redirect for Google and Facebook) ships in BillDogEng: it moved from BillDogPaywall to BillDogAuth, which both products link. import BillDogFull and import BillDogPaywall still reach it unchanged.

  • Feature flags record $feature_flag_called ($feature_flag, $feature_flag_response, and $feature_flag_payload when the flag has one) once per flag value per session, from getFeatureFlag(key:) and getFeatureFlagVariant(key:), as PostHog and the web SDK do. Flag results (MCP get_feature_flag_results) count only this event, so native flag results were always empty. BillDogConfig.sendFeatureFlagEvents: false turns it off.

Fixed

  • Session replay (BillDog.shared.replay, video): frames were black. The capturer rendered a snapshotView's layer, which draws nothing off-screen, so a recording held only the grey mask boxes. It now draws with drawHierarchy, as PostHog does.

  • Session replay (video): each 5 s chunk waited for its own upload before the next one opened, and frames taken in between were dropped — a 3–4 s hole after every chunk on a phone. The chunk is queued on disk and its upload started without waiting.

  • Session replay (both recorders): masks stay on moving content. Mid-scroll, drawHierarchy draws the frame on screen while mask rects come from the view tree, and part of a masked view showed beside its box. The masked regions are sampled twice, 25 ms apart (PostHog's settle check): unmoved, the frame is drawHierarchy; moved, the layer tree the masks were measured from. New in BillDogCore: BillDogReplayMaskRegion, BillDogReplayMasking.masksAreStill, drawWindow, swiftUILayerMaskRegions.

  • Session replay (sessionReplay, screenshots): frames were 3× the 720 px they are meant to be (~170 KB each, one $snapshot event per frame); now 720 px, ~27 KB.

  • Push: a tap BillDog's notification delegate recorded is not recorded again when the app also reports it with onNotificationOpened (from firebase_messaging's onMessageOpenedApp, which forwards taps through the delegate it wraps, or from its own didReceive). It was counted twice. The key is the BillDog notification id and the tapped button (action_id), held until the app reports that tap once or the module resets, as Android does (autoRecordedOpens).

  • BillDogRevenueCatIntegration: a purchase no longer fails when RevenueCat's offerings cannot be loaded. BillDog owns the paywall, so a RevenueCat project often has no offerings, and RevenueCat then fails the offerings fetch (as it does offline); that error was rethrown before the bare-product fallback ran, so nothing could be bought. The package from the offerings is still preferred (RevenueCat's offering attribution); otherwise the product is bought directly, as Android's adapter always does.

  • In-app messages: a fullscreen message lays its content out from the top, below the ✕. The content stack was stretched to the full screen height, so the title label took the spare height: the title floated mid-screen and the body and buttons were pushed to the bottom (and the title's frame reached under the ✕). The ✕ now has its own row, read as "Close" by VoiceOver.

  • A purchase through BillDogSuperwallIntegration is attributed to the BillDog offering behind the Superwall paywall on screen, when SuperwallBillDogPurchaseController(offeringMap:) names it (Superwall paywall identifier → BillDog offering identifier). Superwall presents its own paywall, so no BillDog paywall was on screen and a product sold in more than one offering (experiment arms, a seasonal offering) was credited to the first loaded offering selling it — the wrong offering and placement. A purchase with no mapped paywall on screen, or whose mapped offering is not loaded or does not sell the product, is attributed as before (the last two log a warning). New: PurchaseParams.presentedOfferingContext (Builder.with(presentedOfferingContext:)) names the offering a purchase(params:) is attributed to, ahead of the first loaded offering selling the product, as a package's own context does (RevenueCat `PurchaseParams.Builder.presentedOffe...

Read more

v1.1.1-beta.4

v1.1.1-beta.4 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 24 Oct 08:12

Added

  • BillDogConfig.showsPurchaseFailureAlert (default true): when a purchase tapped on a BillDog paywall fails (not cancelled, not pending) the SDK shows an "An error occurred" alert with the error, and when a restore tapped on it finds nothing, "No Subscription Found" (Superwall shouldShowPurchaseFailureAlert parity). Before, the paywall stayed exactly as it was and the button looked broken. Set it to false if the app shows its own message from BillDogDelegate.onPurchaseFailed / onRestoreCompleted.
  • BillDog.register(placementId:from:params:presentationHandler:): follow a placement's presentation live through a PaywallPresentationHandler (Android parity). onSkip reports .userHasEntitlement, .holdout and .noPaywallConfigured; a presented paywall reports onPresent, onPurchaseSuccess (.keepOpen honoured), onRestore, onDismiss and onFinish as they happen, each naming the placement. PaywallPresentationHandler gains onLoadingStateChange (.loading / .ready / .failed) and onFinish, which every presentation now calls.
  • PaywallAlreadyPresentedError (code PAYWALL_ALREADY_PRESENTED): see below.

Changed

  • A top-level presentation while a BillDog paywall is on screen, or while another is still loading, is refused: the handler's onError (and register's .error) gets PaywallAlreadyPresentedError, the call returns false, and the paywall on screen is untouched. So is a presentation from a view controller that is not in a window or is already presenting. A second presentation used to overwrite the state of the paywall on screen (its Purchase button stopped working) and return true for a present UIKit refused. A wall presented from the paywall in front still stacks when it is a "Show Another Paywall" tap or presentPaywall(wallId:from:) (post-purchase "show paywall"); presentPaywall(identifier:from:) and register from the paywall in front no longer stack a second copy.
  • Native paywalls show trial and introductory-offer copy (.automatic) only to users StoreKit calls eligible; unknown eligibility counts as ineligible (RevenueCat parity). The SDK's own presentations now pass StoreKit's eligibility to the paywall; a host that builds PaywallViewController / PaywallView itself should pass trialEligibility.

Fixed

  • register(placement:) async no longer throws "timed out" while its paywall is on screen: the 30 s bound covers resolving the placement only, and the result (a purchase included) is returned whenever the paywall closes. Every hybrid bridge awaits this call.

  • A gated placement waits (at most 5 s) for the current user's customer info before deciding its gate, in register, getPaywall(forPlacement:) and getPresentationResult(forPlacement:). After a cold launch nothing had loaded it, so paying subscribers were shown the paywall. If it cannot be loaded in time the request fails with an error and nothing is shown or unlocked (Superwall parity).

  • A paying subscriber who is offline at a cold launch gets through a gated placement. Each placement's last-known gate (gated + required_entitlement) is kept per user on the device; when the server cannot be reached (no connection, a lookup, connect or timeout failure — never a server answer such as the 403 withheld or a 5xx) and that gate is a gate, the customer info on the device decides it: holding the required entitlement (or any active one when it names none) reports .entitled / onSkip(.userHasEntitlement), runs register's feature closure, getPresentationResult says .userSubscribed, getPaywall(forPlacement:) throws PaywallSkippedError(.userHasEntitlement) and hasAccessForPlacement answers true. Anything else still fails as before; an ungated or never-resolved placement is never unlocked offline, and one user's gates never answer for another (Superwall falls back to its persisted config the same way). A customer restored from disk counts as known for the gate's wait also when the server names it by another of its ids.

  • A double tap on a paywall's Purchase or Restore runs it once (two purchase_completed events and two host callbacks before).

  • A purchase on a placement's paywall is credited to the offering, placement and experiment that paywall was presented with, also when the current offering sells the same product. paywall_presented carries placement_id.

  • A paywall kept in memory is fetched again in the background once 5 minutes old, and a paywall the server reports gone or inactive is dropped from memory and disk. A republished or unpublished paywall shown by identifier or UUID stayed as first fetched until the app was killed.

  • WebView paywalls on a non-USD storefront showed prices in US dollars: every package and its product now carry the store's currencyCode / currency_code and localized price_string / priceString.

  • Per-month, per-week, per-day and per-year price variables use calendar units (a year is 12 months, 52 weeks, 365 days): an annual $59.99 plan read "$4.93/mo" instead of "$5.00".

  • A downloaded renderer update is validated on its whole content; every update was rejected (the check read the first 4 KB) and re-downloaded 30 minutes later.

  • Customer info belongs to the user it was fetched for. configure() restores the current user's own cached customer info from disk before anything reads it, so hasEntitlement, register gates, entitlementsForProduct, subscriptionStatus, customerInfo and getCustomerInfo() (offline too) reflect a subscriber's access at launch; it is read from the server at launch when missing or older than five minutes. Nothing restored it: a subscriber was shown the paywall at every launch until something fetched. An answer that arrives for a user who is no longer current (a read in flight across logOut) is dropped instead of becoming the new user's customer info, and logIn / switchUser switch to the new user's own cached customer info (or none) before fetching, so a failed fetch no longer leaves them with the previous user's entitlements. switchUser keeps other users' cached customer info on disk for when they return, and invalidateCustomerInfoCache() (run after a web-checkout redemption) and a StoreKit refund/revocation forget only the current user's cached customer info before reading it again; they wiped every user's. subscriptionStatus and customerInfo follow the identity too: configure, logIn, switchUser and logOut show the current user's own cached customer info and status, else that user's own last-known status, else .unknown — never the previous user's. The last-known status is kept per app user id (it was one device-wide value, restored for whoever launched next) and every user's is wiped at logOut. .cachedOrFetched (the getCustomerInfo() default) refreshes in the background only when its cache is over five minutes old (RevenueCat), not on every call.

  • A purchase by product id from a paywall on screen is credited to the offering that paywall rendered. When the SKU was in more than one offering (experiment arms, a seasonal offering), it was credited to the first cached offering selling it — the wrong offering and placement, under the right paywall_id. An explicit package's context still wins; with no paywall on screen nothing changes. OfferingManager.presentedContext(forProductId:renderedOffering:) takes the rendered offering (Android parity).

  • A purchase that fails by throwing — StoreKit offline, parental controls, a storefront that does not sell the product, an unknown product, a transaction that fails verification, or a host PurchaseController (including purchase(custom:)) that throws — now calls onPurchaseFailed and sends purchase_failed once, as a returned .failed does (Android parity); purchase() still throws it. Only a recording refusal reached either. The delegate receives BillDog's failures as BillDogError, as for .failed. A cancel StoreKit throws instead of returning (StoreKitError.userCancelled, SKError.paymentCancelled), or a host controller throws (PurchaseError.userCanceled, BillDogError.userCancelled), returns .cancelled and calls onPurchaseCancelled instead of throwing; a thrown PurchaseError.pending returns .pending. Every other error StoreKit throws leaves PurchaseManager as a PurchaseError (networkError, or storeKitError with the store's code) instead of raw.

  • Journey actions across an identity change: after logOut, an answer to the signed-out user's poll still in flight is no longer delivered (their step reached the next guest), and a result report of a step already run is no longer cancelled by logIn / switchUser / logOut (its result was lost, or — with the action still marked delivered — never sent). A replaced poller's report is no longer dropped when the poller is released. reset() cancels every poller's unsent reports, including one queued just before it.

  • Fonts from an older paywall config's family map (resources.fonts: { "Inter": { weights: [...] } }) load as the server serves fonts: one face per weight, each with the Google Fonts CSS for that one weight, regular weight first. Each weight fetched the same multi-weight CSS. A family with an uploaded file is one face.

  • A tab label in a custom font draws the face of its weight (a bold tab drew the regular face). A family name with non-ASCII letters is UTF-8 encoded in the Google Fonts URL, as the server encodes it; a face's weight may be a decimal or a numeric string.

  • Session-replay uploads, the WebView survey page's API base and the notification service extension's delivery event follow the proxy (setProxyURL) and the environment; they used the production URL always. Relative paywall asset paths resolve against the proxy's host when one is set (BillDogConfig.activeFunctionsBase / assetHostRoot).

  • A setProxyURL URL that already ends in /v1 is used as given; /v1 was appended always, so `https://proxy.example....

Read more

v1.1.1-beta.3

v1.1.1-beta.3 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 17 Oct 08:01

Fixed — a configure()-only app sent no analytics

  • BillDog.shared.configure(config:) registers the analytics module when the app has not
    registered one. It registered none, so trackEvent reached no uploader and the SDK's own
    paywall, purchase and lifecycle events went out on the event bus to no subscriber: an app
    following the dashboard's Quick Start (configure + register(placementId:)) sent config,
    identity and experiment assignment, and not one event.
  • An analytics module the app registers itself still wins. Before configure(), the SDK
    registers none; after, the app's replaces the SDK's, which stops recording (timers, trackers,
    bus subscription) and leaves its queued events to the replacement. Apps and bridges that call
    use(module: BillDogAnalyticsManager()) after configure() keep working unchanged.
  • New: BillDog.shared.analytics (BillDogAnalyticsManager?), the module events go through.

Fixed — a journey action delivered twice across an identity change

  • An action the guest's poll delivered was delivered again by the poll logIn (or switchUser,
    identify) starts: each identity got a new poller with its own record of delivered actions,
    and once the guest is adopted the server returns the same pending action to both. The host ran
    one journey step twice. The record is now shared by every poller the install has, and emptied
    only by reset(); reporting or releasing an action still removes it.

Added — feature flags without setup, and a way to wait for them

  • BillDog.shared.abTest (BillDogFull): the A/B test manager, the app's own if it registered one,
    otherwise created and registered on first use. Not at configure(): its experiment-config
    fetch enrols the user in every running experiment.
  • BillDogABTestManager.waitForFlags(timeout:) (default 5 s) returns once this launch's flags
    have arrived (true), or on timeout or failure (false, getters answer from the cache).
    isReady reports the same without waiting. Replaces await getVariant(experimentId: "") as
    the way to wait.
  • BillDogABTestManager no longer needs setUserId: without it, flags and experiments are
    evaluated for the SDK's identity — the identified user, else the install's anonymous id — once
    the app asks (waitForFlags, refreshExperiments, BillDog.shared.abTest). configure()
    alone still fetches only for a setUserId id, so a module the RN bridge or the Inspector
    registers for every app enrols nobody.

Fixed — every package of a bound product list is shown

  • A product list bound to the offering (bindToPackages) drew only its authored cards, so a
    package added to the offering (a new lifetime plan, say) never appeared until someone added a
    card in the builder. A package beyond the authored cards now gets a copy of the last card:
    its own ids (__pkg<n>) and selection state, filled from its package like any card. Fewer
    packages than cards still shows the first N, and a copy of the badged card shows no badge.
    The same rule runs on iOS, Android and the web, pinned by a shared conformance suite.

Fixed — a one-time product's card shows no period

  • A lifetime or other one-time product's period is empty; its card showed a bare "/". It now
    shows nothing, as on the web.

Fixed — shadows and theme colours drawn as designed

  • Shadow geometry authored as {value, unit} (what the builder exports) was read as missing,
    so a default shadow became a hard 4 pt copy under the element and an authored one lost its
    numbers. It is read as a unit value now, and no non-zero geometry means no shadow.
  • An unresolved var(--x) colour no longer draws transparent: the component's theme fallback
    is used. A theme token left in the configuration (e.g. hsl(var(--muted-foreground))) is
    resolved against the palette in effect when the paywall is rendered.
  • hsl(… / 50%) is drawn at 50 % alpha, not opaque.

Removed — ImmediatePaywallHandler

  • BREAKING: ImmediatePaywallHandler (BillDogWebView) is removed. Nothing in the SDK called it,
    and nothing stored the "immediate" paywall ids that shouldShowImmediately(paywallId:) read, so
    it always answered false.

Fixed — signing in keeps the user's cached paywalls

  • logIn and switchUser keep the incoming user's own cached paywalls (memory and disk) and
    drop every other identity's. They cleared the whole cache, although it is keyed by user; and
    identity starts each launch as the install's guest, so an app calling logIn at every launch
    discarded the disk cache the user built last session, and its first paywall went to the
    network. logOut still clears everything.

Fixed — the first request after the app returns from the background

  • A request that fails with "The network connection was lost" is sent once more. The server
    closes idle connections while the app is in the background, and the first request after it
    returns can go out on one of them. URLSession sends only a GET again by itself; every BillDog
    call is a POST, so on a device fetch-paywall failed this way and the paywall did not open.
    Covers paywall fetches, journey action polling, post (placements, customer info, store
    evidence) and analytics uploads. auth-token and the other calls made through
    post(endpoint:body:customHeaders:) are not sent again: a refresh rotates the token, and
    sending one the server may already have rotated can end the session.

Changed — WebView paywalls open on a renderer page started ahead of time

  • Once the app has fetched a wall that draws in a web view, BillDogWebView starts one renderer
    page off screen, and the paywall screen shows that page and only injects the paywall. Every open
    used to build a web view, read and scan the ~3 MB renderer file on the main thread, and load it.
    One page is kept; the next is started after one is shown. It is released on a memory warning and
    on reset(), and started again when needed. PaywallPrerenderer.enabled = false turns it off.
  • The renderer file is chosen off the main thread, once per downloaded renderer.
  • The pool no longer starts a hidden web view for every fetched wall (native walls included); the
    paywall screen never used them. WebViewPoolManager.registerPaywall is kept for apps that call it.
  • A paywall web view whose content process ends loads the renderer again instead of staying blank.
  • After BillDog.reset(), BillDogWebView listens for fetched paywalls again once it is configured;
    it used to stop warming WebView paywalls until the app restarted.

Fixed — paywall images and fonts warmed before display

  • Every image a paywall's server manifest lists (every device layout's, up to 64) is warmed.
    The list was cut to 12 after every URL had been marked warmed, so images 13+ were never
    requested — by that fetch or any later one.
  • An image that failed to warm (an error or a non-2xx answer) is tried again on the next fetch.
  • A paywall with fonts and no images has its fonts warmed; it returned before reaching them.
  • Media is warmed for the renderer that draws the wall — the route the paywall screen takes
    (resolvedRenderStrategy). A wall drawn in a web view because of its render_mode was
    warmed into the native image cache, which the web view does not read.
  • A native wall's image is warmed again on its wall's next fetch whenever it is no longer decoded
    in memory. It used to count as warm for the life of the process, though the system empties the
    decoded image cache when memory runs short and the image disk cache trims itself to its size: the
    paywall then drew a placeholder before the image, or downloaded it. Whether an image is ready is
    now asked of the cache: decoded → skipped; bytes still on disk → decoded from there with no
    request; neither → downloaded.
  • A WebView wall's image or font is warmed again on its wall's next fetch once 5 minutes have
    passed since it loaded. It used to count as warm for the life of the process, so once it left
    the web view cache (WebKit trims the cache to its size; an app can clear web data) the paywall's
    page downloaded it while drawing. WebKit cannot say whether a URL is still cached; warming one
    that still is reads it from the cache and sends no request.
  • A WebView wall's images and fonts are warmed in the web view cache, where its page reads them
    (measured: a warmed image is not requested again by the paywall's page). The warmer stopped at
    12 images, marked the wall warmed before anything had loaded — so a failed load was never tried
    again — and warmed no fonts. Each image and font is now marked warmed only once it loaded, and
    a Google Fonts sheet is warmed with its font files.

Fixed — a paywall's offerings, prices and intro eligibility are ready before it opens

  • Offerings are served from cache and refreshed in the background once older than 5 minutes
    (up to a day), instead of making the next paywall wait for a refetch. They are refreshed on
    return to the foreground and for a newly signed-in user, and another user's are never served
    (logIn did not drop them).
  • StoreKit intro eligibility is asked for when offerings arrive and kept, instead of at every
    paywall open (injectPackagesIntoRendererJson and the native products component each asked
    StoreKit again). Refreshed in the background after 5 minutes; dropped and asked again
    whenever the caller's active entitlements change — a purchase here or on another device, a
    restore, a web redemption, a renewal, an expiry. An answer being fetched when that happened
    is not kept. The 500 ms wait for an answer not yet kept now holds even when StoreKit is slow.
  • A placement's offering is enriched from the StoreKit products already fetched; only products
    not yet known are asked for.

Changed — register presents a preloaded placement at once

  • register acts on the answer it kept for the placement — from preloadPaywalls(forPlacements:)
    or the previo...
Read more

v1.1.0-beta.3

v1.1.0-beta.3 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 12 Oct 08:27
release(v1.1.0-beta.3): single-module xcframeworks; rename BillDog ->…

v1.0.2-beta.3

v1.0.2-beta.3 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 03 Oct 02:57
release(v1.0.2-beta.3): single-module xcframeworks; rename BillDog ->…

v1.0.0-beta.2

v1.0.0-beta.2 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 17 Jul 06:42

BillDog iOS SDK 1.0.0-beta.2

Fixed

  • XCFramework resource bundles are now shipped. The binary SPM distribution previously dropped every SPM resource bundle at packaging time. Because SPM's generated Bundle.module accessor ends in fatalError, this surfaced as a crash (not a graceful fallback) the first time a WebView paywall loaded with a cold cache. Affected 1.0.0-beta.1.
  • PrivacyInfo.xcprivacy is now included. The privacy manifests for BillDogCore and Lottie were stripped by the same packaging bug, which could cause App Store submission warnings for integrating apps.

Notes

  • Bundled WebView renderer updated to the 1.0.0-beta.2 bundle.
  • Upgrading from beta.1 is recommended for anyone using the WebView paywall path.

v1.0.0-beta.1

v1.0.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@billdogai billdogai released this 23 Jun 08:38

v1.0.0-beta.1 binary package release