Closed
Bug 744873
Opened 12 years ago
Closed 6 years ago
App reinstalls via mozApps.install should retain old receipts
Categories
(Core Graveyard :: DOM: Apps, defect)
Core Graveyard
DOM: Apps
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: anant, Unassigned)
Details
Calling navigator.mozApps.install() for an app that was previously installed currently replaces old receipts. Any such re-install should persist receipts in an additive manner (add the new receipt to the receipts array instead of replacing the old receipt). The main reason for persisting receipts is to allow the user the option to use the old receipt (if the site was still accepting them, this depends on the reason for which a reinstall was invoked) to unlock functionality that they have previously paid for. This calls into question the method by which will distinguish which receipt is the latest (without having to parse it). We can think about adding convenience methods for this, but that's separate bug.
Comment 1•12 years ago
|
||
Sounds like this could affect the functionality of an application deciding to use in-app payments, right? If so, we need to get this fixed as soon as possible.
Updated•12 years ago
|
blocking-basecamp: --- → ?
Updated•12 years ago
|
Whiteboard: [blocked-on-input]
Comment 3•12 years ago
|
||
In-app does not use receipts. The only documented use of a receipt is to confirm payment of an app. The overwriting of receipts is not great, but doesn't degrade any functionality. I think this is an enchancement, not a blocker.
Updated•12 years ago
|
blocking-basecamp: ? → ---
Whiteboard: [blocked-on-input]
Updated•7 years ago
|
Product: Core → Core Graveyard
Comment 4•6 years ago
|
||
Core Graveyard / DOM: Apps is inactive. Closing all bugs in this component.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•