Skip to main content
H
hdoidoi
Participant
November 11, 2014
Answered

Android 5.0 Lollipop In-App-Billing v3 Test Purchasing not work.

  • November 11, 2014
  • 4 replies
  • 9302 views

I installed  Android 5.0 developer preview on Nexus 7(2013). ( Android L Developer Preview | Android Developers )


In-App-Billing V3 test purchasing currently works on Nexus 7 with Android 4.4.2.

But, Android L returns error,

11-11 14:17:53.126: D/Finsky(1403): [1] PurchaseFragment.handleError: Error: PurchaseError{type=3 subtype=12}

11-11 14:17:53.126: D/Finsky(1403): [1] PurchaseFragment.fail: Purchase failed: PurchaseError{type=3 subtype=12}

and have system dialog below.

This version of the application is not configured for billing through Google Play. Check the help center for more information


Other application (not using AdobeAIR) is working fine on Android L...

Any solutions?

This topic has been closed for replies.
Correct answer Anki_AG_

I have an app in the GooglePlay store, but it's still in beta development and hasn't been distributed outside my development team. The existing certificate is 1024-RSA. 

Chris Campbell wrote:

We've also provided a beta version of ADT (linked in the post) that fixes the 1024-RSA issue with new applications.

Can I just compile with the beta version of ADT at this point and keep my existing GooglePlay entry and appID? Or would it be safer to generate a new 2048-RSA key, and create a new entry in the GooglePlay store?


Hi,

Could you please try initiating the in-app purchase now? The issue has been fixed by google at their end. Please let us know if you still face issues.

Thanks,

Adobe Air

4 replies

YopSolo75
YopSolo75
Participating Frequently
November 19, 2014

My app is working fine on lollipop (captive runtime)

https://play.google.com/store/apps/details?id=air.com.lagardere.tele7jeux&hl=fr_FR

The only issue come from in-app.

zeh
zeh
Inspiring
November 19, 2014

Chris, here's a thought. I don't know that much about how Android verifies the keys, so I could be completely off base.


But: I could get an existing application generated by ADT in the same way as before, add a NEW key (using jarsigner, same as Android apps), and upload that to Google Play as an update. Because it still has the old key, it's a valid update, just signed twice.

If a user installs that version BEFORE updating to Android 5, when the update is made, could it allow the update because one of the signatures would be correct?

This wouldn't do anything for people who already updated their phones, but if my assumptions are correct, it could prevent apps from breaking going forward.

Never mind. Signing with several certificates seem to have been disabled, and the store will reject your file.

JJ1138
JJ1138
Participant
November 14, 2014

Adobe Bug Report for the issue:

Bug#3850225 - Certificate generated by adt doesn't work with Android 5 Lollipop

chris.campbell
Community Manager
chris.campbellCommunity Manager
Community Manager
November 19, 2014

Here's the current status:

  • We've reported this bug to Google and they were aware of the issue.  They are working on a fix, ETA unknown.  Both Adobe and Google are aware that this is a critical for you guys and we'll continue to ping them for updates.  Existing applications will need to wait for Google to push out this update.
  • There are two potential workarounds for *new* applications.  Please note that this will not address existing applications.  Developers will need to use a new app ID, creating a new entry in the Google Play Store.
    • Developers can use the current version (15.0.0.356) of the AIR SDK to create new applications using a self signed cert containing key_type "2048-RSA"
    • We are making a change to our next AIR beta (possibly as soon as next week) that will address the 1024-RSA key_type.  Developers can wait for this beta release and create their applications using the default ADT settings with 1024.

We'll continue to update you with new information as it becomes available.

Thanks,

Chris

    H
    hdoidoiAuthor
    Participant
    February 17, 2015

    Hi,

    Could you please try initiating the in-app purchase now? The issue has been fixed by google at their end. Please let us know if you still face issues.

    Thanks,

    Adobe Air


    this problem fixed on Android 5.0.1

    Thanks for your support!

    JJ1138
    JJ1138
    Participant
    November 12, 2014

    There is a bug in Lollipop concerning Apps that are signed with a key generated by Adobe AIR:

    Issue 79089 - android - Lollipop: In-app billing broken because SHA1 fingerprint calculated from APK certificate differ…

    It looks like your App is also affected by this. Lets hope that Google can fix this quickly.

      chris.campbell
      Community Manager
      chris.campbellCommunity Manager
      Community Manager
      November 13, 2014

      Hi guys,

      I wanted to let you know that I'm looking into this and will report back once I have additional info.

      Thanks,

      Chris

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices