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
Describe the bug
A clear and concise description of what the bug is. The more detail you can provide the faster our team will be able to triage and resolve the issue. Do not remove any of the steps from the template below. If a step is not applicable to your issue, please leave that step empty.
Environment
Platform:
SDK version 5.9.0:
StoreKit version:
StoreKit 1 (default on versions <5.0.0. Can be enabled in versions >=5.0.0 with .with(storeKitVersion: .storeKit1))
[] StoreKit 2 (default on versions >=5.0.0)
OS version 18.0, 18.1:
Xcode version Xcode 16.1:
Device and/or simulator:
Device
Simulator
Environment:
Sandbox
TestFlight
Production
How widespread is the issue. Percentage of devices affected.
Debug logs that reproduce the issue. Complete logs with Purchases.logLevel = .verbose will help us debug this issue.
Show paywall fullscreen ui.
Steps to reproduce, with a description of expected vs. actual behavior
Hi @ArmenZoom,
By default, the close button will be your app's accent color. You can change that in the app settings or override the color of the paywall close button in the paywall builder in the RevenueCat dashboard.
Describe the bug
A clear and concise description of what the bug is. The more detail you can provide the faster our team will be able to triage and resolve the issue. Do not remove any of the steps from the template below. If a step is not applicable to your issue, please leave that step empty.
.with(storeKitVersion: .storeKit1)
)Purchases.logLevel = .verbose
will help us debug this issue.Steps to reproduce, with a description of expected vs. actual behavior
Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: