| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
On Android we have some third party code which is needed for
connecting to the Google Play service and verification of the
returned pay load. The attributions for this were missing.
Task-number: QTBUG-60122
Change-Id: I0ecd5b3f9c4ef946d4b38c20e48b1f68e6f3640c
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
| |
In preparation of submitting to the Qt Project, change all domains
from com.digia to org.qtproject.
Change-Id: Id5e9676fdb6de6244447288d35c5c4cb41bbd577
Reviewed-by: Andy Nichols <andy.nichols@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To speed up product requests, we can batch them in bundles of
at most 20 SKUs (according to the documentation).
To do this, we add a new virtual function to the back-end which
allows sending in the whole list of pending products. The
default implementation of this just calls the regular
queryProduct() function so that behavior stays the same
on iOS.
Change-Id: I093e254792d23ed39199392748b7163925856081
Task-number: QTRD-3506
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In an application with many products (e.g. 50), some would
randomly fail to be requested, sometimes with remote exceptions
and other times with regular failures. It could be that the
service object is not thread-safe, but it seems to be easier
to reproduce on low-end devices, so a plausible explanation
is that the amount of simultaneous requests drains all
resources. Synchronizing access will slow it down a little
bit, but this can be fixed in a follow-up patch where we
request all products in a single request instead of
individually.
Change-Id: I19ca5aa43dd780fdd264f179f8a8ece603215a3e
Task-number: QTRD-3506
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
|
|
|
|
|
|
| |
Includes backends for iOS and Android
Change-Id: If2ae69537fae46d83c8a026582922cb791fb8608
Reviewed-by: Eskil Abrahamsen-Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
|
|
|
|
|
|
| |
Adds three properties which are useful to the transaction, and implement
these on Android. iOS implementation pending.
Change-Id: Ie5541cb518b8c0766b69eb803a529f213e09a34a
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|
|
|
|
|
|
|
|
|
| |
After discussing this for a little while, we decided to go with
Qt Purchasing as the module name in the tech preview with the option
to change this later if necessary.
Change-Id: I08fbd4b7a63da1391e1323f6bde842af050e1757
Reviewed-by: Eskil Abrahamsen-Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
|
|
|
|
|
|
| |
Add the final piece of functionality to the Android port.
Task-number: QTRD-2932
Change-Id: Ic011fb5a93648a1497abe61c13bc58aa48d6874f
Reviewed-by: Eskil Abrahamsen-Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
We were checking for the wrong property name in the bundle and
bailing out before we registered the unlockable products as
previously purchased, so we would get into a asynchronized state.
Task-number: QTRD-2934
Change-Id: I572ec273794260b9108fb049c681f71edac8f49c
Reviewed-by: Eskil Abrahamsen-Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
|
|
|
| |
Change-Id: I15110af62207c1a6fe66b0b10eb93d69d6d774d8
Reviewed-by: Eskil Abrahamsen-Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
|
|
|
|
|
|
| |
Use the new APIs in Qt 5.3 to launch intents and issue a purchase
request.
Change-Id: Ia514a92f78d14368df3ea9d56b2b4309d885e95a
Reviewed-by: Eskil Abrahamsen-Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
At this point, contains an unfinished in-app purchase API
with an unfinished Android implementation.
Change-Id: Id01b61f6d588557404a7df0b002b4b6d3cb00f33
Reviewed-by: Andy Nichols <andy.nichols@digia.com>
|