Control PaywallView dismiss about purchases-ios

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[NachoSoto]

Have you tried overriding .environment(\.dismiss, yourAction)?

[lionel-alves]

@NachoSoto Yes, here is what I tried:
1.

PaywallView(fonts: Font.Provider(), displayCloseButton: false)
.environment(\.dismiss, {})

Gives the error: Cannot convert value of type '() -> ()' to expected argument type 'DismissAction'
DismissAction doesn't have a public initializer

2. Define my own DismissAction

struct DismissAction: EnvironmentKey {
    static var defaultValue: () -> Void = {}
}

extension EnvironmentValues {
    var dismiss: () -> Void {
        get { self[DismissAction.self] }
        set { self[DismissAction.self] = newValue }
    }
}

Used as follow:

PaywallView()
    .environment(\.dismiss, {

    })

That didn't work, the view was still dismissed. Note that this actually prevents the view from being dismissed if used on one of my views, but it doesn't work on RevenueCatUI views like PaywallView.

[lionel-alves]

Hi @NachoSoto, to fix this issue what do you think of passing a dismiss closure so that can be handle by the caller. The one presenting the view / vc should be the one responsible for dismissing it, right?
Since I cannot use it the onboarding, this issue prevents me from using the templates all together.
Thanks for the great work on this project!

[vegaro]

Hi @lionel-alves we just released a new view modifier onRequestedDismissal you can use to handle the dismissal

purchases-ios/RevenueCatUI/View+PurchaseRestoreCompleted.swift

Line 269 in e65c323

public func onRequestedDismissal(_ action: @escaping (() -> Void)) -> some View {

Please note if this is set, the paywall will not be dismissed automatically and it's your responsability to dismiss it.

I think this fixes this issue, so I am closing it. Let us know if you face any problems.

Thanks!

[github-actions]

This issue has been automatically locked due to no recent activity after it was closed. Please open a new issue for related reports.