You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do open web app receipt checking. The getSelf() call for the mozApps, in the onsuccess, there will be a request.result._receipts array with receipts that can be checked for validity.
There should be a call to the "verify" url in each receipt to make sure it is still valid, and if the user is offline, the result of the check should be cached for offline use.
Some things to consider:
How to store the offline cached verification. _receipts is an array, but it can change over time, so try to find some other id to use for caching.
What UI action to take if a receipt is not valid? Maybe for now just show a twitter bootstrap alert? But it seems like an invalid receipt means the app should not run at all. Redirect to a "receipt not valid, here is what to do next" page? Ask the apps folks for guidance.
Do open web app receipt checking. The getSelf() call for the mozApps, in the onsuccess, there will be a request.result._receipts array with receipts that can be checked for validity.
This document describes the format of each request:
https://wiki.mozilla.org/Apps/WebApplicationReceipt
There should be a call to the "verify" url in each receipt to make sure it is still valid, and if the user is offline, the result of the check should be cached for offline use.
Some things to consider:
To see code with a receipt:
Go to:
https://marketplace-dev.allizom.org/en-US/app/myscotch/
install it, then go to this page to see a receipt dump:
http://andymckay.github.com/myscotch/
The text was updated successfully, but these errors were encountered: