Databases
StackOverflow2013
Postsdbo
POAndroid billing v3 - no signature
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid billing v3 - no signature
    primarykey
    data
    text
    <p>What I want? After retrieving all purchased items I need to verify the purchase on my server, this I want to do with the signature and signed data received from the in-app payment.</p> <p>First I used the in-app billing v2 there I got every time with my developer account a correct signature and signdata for the static test sku <code>android.test.purchased</code>.</p> <p>I switched to the new billing v3 because it seems very nice to implement, however I get no signature any more.</p> <p>I have uploaded a previous version of my APK to Google (don't published ever because it is not finished yet), also I added a active in-app product for further testings.</p> <p>The upload of the APK was yesterday 10:00 pm so I think also I have waited enough.</p> <p>What I tried? I have installed my application in different version:</p> <ul> <li>unsigned apk with my self added "active" in-app product => no signature</li> <li>unsigned apk with the sku <code>android.test.purchased</code> => no signature</li> <li>signed apk with my self added "active" in-app product => no signature</li> <li>signed apk with the sku <code>android.test.purchased</code> => no signature</li> </ul> <p>Those 4 "app states" I tried both my developer phone (where my primary Google account is the same user as the developer console account) and with a test account on setup another phone, the test account is also placed in my account settings under "test accounts".</p> <p>Hmm and now I have no more ideas how I get my signature. I think I will get the signature with an active app + active in-app product because the payment process works (The adb logcat displays that I purchased the "Android.test.purchased") My self created in-app product I could also not test because if I use my developer account, the play store tells me "can not buy, already owned" and with my test account I got an error "This product is not available for your account".</p> <p>Do you have a solution for my problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeter O.
    1. USprdatur
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid billing v3 - no signature
      1. UStarkeshwar
      1. VTFavorite
    2. VO
      singulars
      1. POAndroid billing v3 - no signature
      1. USlunarnet76
      1. VTBountyStart
    3. VO
      singulars
      1. POAndroid billing v3 - no signature
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@lunarnet76, what the data is, is really simple. the signdata is the data which google send back to your account, the data tells you about the purchase state, and the signature can be used with your public app key to verify the signdata was not manipulated and that google has send it
      singulars
      1. POAndroid billing v3 - no signature
      1. USprdatur
    2. COprdarur. I am having the same problem, did you find a solution?
      singulars
      1. POAndroid billing v3 - no signature
      1. USmelodiouscode
    3. CONot for now, but by reading other posts which says "google's depricated says only that you should not use it but it will not get removed" i decided to stay on V2, because there my implementation worked as expected. But i do not stop searching for a solution with V3. Because i verify the payment through my server V2 let me do this without providing the public key within the app which is very nice, i only have the public key on my server which verifies. With V3 i think this is also not possible.
      singulars
      1. POAndroid billing v3 - no signature
      1. USprdatur
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload