RevenueCat/purchases-ios

`Purchases.logLevel = .verbose` does not affect levels available in Console.app

Closed this issue · 3 comments

  1. Environment
    1. Platform: iOS (iPad)
    2. SDK version: 4.25.6
    3. StoreKit version:
      • StoreKit 1
      • StoreKit 2 (enabled with usesStoreKit2IfAvailable(true))
    4. OS version: 16.4 (simulator, iPad 10th) / 16.6 (iPad 9th)
    5. Xcode version: 14.3.1
    6. Device and/or simulator:
      • Device
      • Simulator
    7. Environment:
      • Sandbox
      • TestFight
      • Production
    8. How widespread is the issue. Percentage of devices affected.
  2. Debug logs that reproduce the issue. Complete logs with Purchases.logLevel = .verbose will help us debug this issue.
WARN: 🍎‼️ Unable to load receipt, ensure you are logged in to a valid Apple account. <snip>
WARN: 🍎‼️ App running on sandbox without a receipt file. Unable to determine into eligibility unless you've purchased before and there is a receipt available.
  1. Steps to reproduce, with a description of expected vs. actual behavior

Expected:

With Purchases.logLevel = .verbose, I expected to see logs with levels up to that maximum in Console.app.

Actual:

DEBUG and VERBOSE logs that appear in the xcode console do not also appear in Console.app.

What I was trying to do:

Investigate a defect observed in TestFlight and production using Console.app to see the logs of the physical device in developer mode, but could only see a limited set of RC SDK logs (error/warn level).

Comments:

My simplest repro case (for this issue, not the defect I was investigating earlier) is running a debug build in the simulator and just looking at what logs appear when the app starts and just shows the product offerings on a paywall (no UI interaction), then comparing what's shown in Console.app versus xcode console.

In Console.app I only see the two WARN logs pasted above in 2..

In xcode console I see:

  • The 2 WARN above
  • 46 DEBUG
  • 18 VERBOSE

There's no context in which I've been able to see VERBOSE/DEBUG in Console.app across any DEBUG/RELEASE/device/simulator combination.

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

  2. Additional context
    Add any other context about the problem here.

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

Thanks for the report.

This has been a bug in Console.app for many years, and it seems like it's still present to this date.

I recommend filing a Radar, unfortunately there's not much we can do.

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