0% found this document useful (0 votes)
3 views2 pages

Debugging Screen Log Analysis

The document appears to be a debugging log for a software application, showing various timestamps and system messages related to purchases and subscriptions. It includes details about product requests, subscription statuses, and connection states. The log is intended for troubleshooting and may require screenshots for further analysis of any bugs encountered.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views2 pages

Debugging Screen Log Analysis

The document appears to be a debugging log for a software application, showing various timestamps and system messages related to purchases and subscriptions. It includes details about product requests, subscription statuses, and connection states. The log is intended for troubleshooting and may require screenshots for further analysis of any bugs encountered.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

--- THIS PAGE IS FOR DEBUGGING PURPOSES ---

If you get in touch with me about a possible bug I might ask you for a screenshot
of this screen.

Q...3 🔻♦️ L...ES 🇪🇸 V...2.0.90-3 N...0 T...mdt2 ✅ I...17.5.1 J...1955


F...2.0.87 C...MX

> 1:21:58 p r :)
> 1:21:58 IN 2
> 1:21:58 s m2
> 1:21:58 ask m
> 1:21:54 >> adBAc
> 1:21:54 >> awRAc
> 1:21:48 s m2
> 1:21:48 ask m
> 1:21:48 p r :)
> 1:21:48 IN 2
> 1:21:43 QR :)
> 1:21:43 QR 2
> 1:21:38 p r :)
> 1:21:38 IN 2
> 1:21:38 s m2
> 1:21:38 ask m
> 1:21:28 s m2
> 1:21:28 ask m
> 1:21:28 p r :)
> 1:21:28 IN 2
> 1:21:23 QR :)
> 1:21:23 QR 2
> 1:21:18 p r :)
> 1:21:18 IN 2
> 1:21:18 s m2
> 1:21:18 ask m
> 1:21:8 s m2
> 1:21:8 ask m
> 1:21:8 p r :)
> 1:21:8 IN 2
> 1:20:58 s m2
> 1:20:58 p r :)
> 1:20:58 IN 2
> 1:20:58 ask m
> 1:20:48 QR :)
> 1:20:48 QR 2
> 1:20:48 p r :)
> 1:20:48 IN 2
> 1:20:48 @ CON cS end after UL
> 1:20:48 @ CON cS end before UL
> 1:20:48 @ CON cS success
> 1:20:47 s [Purchases] Checked EntFromSt
> 1:20:47 s [Purchases] E 3
> 1:20:47 s [Purchases] Set PurchFromSt
> 1:20:47 s SK has no purchase
> 1:20:47 s !! LT to false
> 1:20:47 s [Purchases] P did setFromSt LT has LTA
> 1:20:47 s [Purchases] no latest result
> 1:20:47 s [Purchases] P did setFromSt LT has product
> 1:20:47 s SK has no purchase
> 1:20:47 s !! LT to false
> 1:20:47 s [Purchases] P did setFromSt LT has LTA
> 1:20:47 s [Purchases] no latest result
> 1:20:47 s [Purchases] P did setFromSt LT has product
> 1:20:47 s [Purchases] Set SubFromSt
> 1:20:47 s [Purchases] P setFromSt has finished setSubStatus
> 1:20:47 s SK has sub active
> 1:20:47 s [Purchases] P SetSubSt2
> 1:20:47 s [Purchases] P S has newSubscription
> 1:20:47 s [Purchases] P S after renewalInfo
> 1:20:47 s [Purchases] P S before renewalInfo
> 1:20:47 s [Purchases] P S Periodo de reintento de facturación
> 1:20:47 s [Purchases] P S
> 1:20:47 s [Purchases] P SetSubSt
> 1:20:47 s [Purchases] P setFromSt has product
> 1:20:47 @ CO Q step 6
> 1:20:47 @ CON cS iteration
> 1:20:47 @ CON after catch
> 1:20:47 @ CO Q function end
> 1:20:47 @ CO Q step 5
> 1:20:47 @ CO Q step 4
> 1:20:47 @ CO Q step 3
> 1:20:47 @ CON cS NOT CONNECTED
> 1:20:47 @ CON cS
> 1:20:47 s [Purchases] found 5 products.
> 1:20:47 @ CON cAS
> 1:20:47 @ > launch()
> 1:20:47 -- V2 parse
> 1:20:47 >> adBAc
> 1:20:47 s [Purchases] req products
> 1:20:47 s SK has sub active
> 1:20:47 launch a2>>
> 1:20:46 >> dfLwo

You might also like