Skip to main content
hdoidoi
Participant
Nov 11, 2014 6:01 AM UTC
Answered

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

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 is closed to new replies. Start a new post to keep the conversation going.
Anki_AG_
Anki_AG_Correct answer
Adobe Employee
Dec 8, 2014 11:05 AM UTC

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

View reply

16 replies

YopSolo75
YopSolo75
Participating Frequently
Nov 19, 2014 8:48 PM UTC

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.

Translate
zeh
zeh
Inspiring
Nov 19, 2014 8:22 PM UTC

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.

Translate
JJ1138
JJ1138
Participant
Nov 14, 2014 12:55 PM UTC

Adobe Bug Report for the issue:

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

Translate
chris.campbell
chris.campbell
Legend
Nov 19, 2014 4:59 AM UTC

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

Translate
    Frédéric C.
    Frédéric C.
    Inspiring
    Nov 19, 2014 8:52 AM UTC

    Hi, and thanks for the update.

    Does that mean that if I always signed my apps with a 2048-RSA key type, the issue won't occur at all with Android L, even on apps that were already published with former versions of the SDK?

    Translate
    JJ1138
    JJ1138
    Participant
    Nov 12, 2014 8:10 PM UTC

    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.

    Translate
      chris.campbell
      chris.campbell
      Legend
      Nov 13, 2014 12:35 AM UTC

      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

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