RevenueCat/purchases-ios

Paywall bug for visionOS, Template 4, not enough room for "Monthly" split over two lines

MatthewWaller opened this issue · 1 comments

Describe the bug
I'm using the Template 4 Paywall in our visionOS app. Unfortunately, "Monthly" is split over two lines like "Month-ly" despite enough room. I tried adding more space to the paywall view, but no luck.

Screenshot 2024-02-18 at 9 16 06 PM
  1. Environment
    1. Platform: visionOS
    2. SDK version: 4.36.3
    3. StoreKit version:
      • StoreKit 1
      • StoreKit 2 (enabled with usesStoreKit2IfAvailable(true))
    4. OS version: visionOS 1.0
    5. Xcode version: 15.2
    6. Device and/or simulator:
      • [ x] Device
      • [ x] Simulator
    7. Environment:
      • [x ] Sandbox
      • [ x] TestFight
      • [ x] Production
    8. How widespread is the issue. Percentage of devices affected. 100%
  2. Debug logs that reproduce the issue. Complete logs with Purchases.logLevel = .verbose will help us debug this issue.
Logs here: None
  1. Steps to reproduce, with a description of expected vs. actual behavior

Create a Paywall view with Template 4 like so:

.sheet(isPresented: $payments.presentPaywall, content: { // We have to add another sheet here because you can't have two modals at once.
            PaywallView(displayCloseButton: false)
                .frame(width: 500, height: 800)
                .overlay {
                    VStack {
                        HStack {
                            Spacer()
                            Button {
                                payments.presentPaywall = false
                            } label: {
                                Image(systemName: "xmark")
                                    
                            }
                            .padding()
                        }
                        Spacer()
                    }
                }
        })

Have one of the options named: "Monthly" as a package.

See it split over two lines.

  1. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.) N/A

  2. Additional context
    Add any other context about the problem here. N/A

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