Device logs give us detailed information about the app which can help debug if the user is experiencing issues.
This guide will explain what sort of information you can get from the logs. Please note there are differences between iOS and Android logs, however the information that is outlined below can be found in both. The Pugpig support team will always be happy to help - this is just so that if you want to provide a bit of first line support (and try to see where a potential problem might lie) you can.
How to get the logs from a device:
- In the app go to Settings > General > Scroll to the bottom
- Click and hold 'Powered by Pugpig' and a prompt will appear which will say 'Email Logs'
- Our Pugpig Engineering email address will already be populated in the email, however you can change this to your own email in the 'to' field so you can send the logs to yourself
The type of information you can find in the device logs:
Name of the app, device type, product version:
First 5 lines of the log.
Can tell you if the user is on an old version of the app, which could cause issues if they aren't seeing the new features or general issues with extremely old versions. It can also help us to identify if there were any known issues with that version of Pugpig.
Store Subscription Status:
----- Example -----
2017-11-13 08:48:36 +0000: iTunesAuth UpdatedSubscription: <?xml version="1.0" encoding="UTF-8"?>
<subscription state="inactive" message="You have no active subscriptions.">
--------------------
Store Subscription Receipt:
----- Example ----- (this is just an extract from the full receipt)
2017-11-24 15:23:57 +0000: iTunesAuth UpdateSubscription on https://magazine.
--------------------
The receipt is everything after the `productid=&uuid=&receipt=`
Note: the receipts can vary in length
If you wanted to check what access the receipt allows, you can put it into the 'Receipt Validator' in the distribution service. Go to Stores > Apple or Google Store > Scroll to the bottom of the page and you'll see a test form. The receipt will be encoded, follow the steps on this article to understand how to decode and understand the test form.
Single Issue Purchase Breakdown:
----- Example -----
-->
<!-- User's receipt has been verified successfully -->
<issues>
<issue>com.examplepurchase.jan2018</
<issue>com.examplepurchase.dec2017</
</issues>
</subscription>
--------------------
Single Issue Purchases Receipt:
----- Example ----- (this isn't the full receipt)
2018-01-04 15:56:45 +0000: iTunesAuth UpdateSubscription on https://magazine.
--------------------
The receipt is everything after the `productid=&uuid=&receipt=`
Note: the receipts can vary in length
If you wanted to check what single issues the receipt is for, it's the same steps as validating subscription at this article.
Push Notification Token:
----- Firebase Example -----
2018-01-04 15:56:48 +0000: Firebase: Updated token d0hzbux4ukY:APA91bFbP_
-------------------------------
Note this is a token from the Firebase push provider, Urban Airship tokens look slightly different e.g. the below:
---- Urban Airship Example ----
2018-01-04 21:44:12 +0000: didRegisterForRemoteNotificati
------------------------------------
Comments
0 comments
Please sign in to leave a comment.