Copy link to clipboard
Copied
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?
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
Copy link to clipboard
Copied
There is a bug in Lollipop concerning Apps that are signed with a key generated by Adobe AIR:
It looks like your App is also affected by this. Lets hope that Google can fix this quickly.
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
Adobe Bug Report for the issue:
Bug#3850225 - Certificate generated by adt doesn't work with Android 5 Lollipop
Copy link to clipboard
Copied
Here's the current status:
We'll continue to update you with new information as it becomes available.
Thanks,
Chris
Copy link to clipboard
Copied
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?
Copy link to clipboard
Copied
Frédéric C. wrote:
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?
Yes, from what I've been told if you had a 2048-RSA signature, your app would not have encountered any problems with Android L.
Copy link to clipboard
Copied
Hi,
You can check with openssl if a key/certificate is affected by this issue. I have described this in the above mentioned bug report:
https://code.google.com/p/android/issues/detail?id=79089#c8
I also found out what seems to be the problem with certain keys:
https://code.google.com/p/android/issues/detail?id=79089#c9
Unfortunately, I think there is no workaround for existing Apps that are signed with a key suffering from this issues.
Copy link to clipboard
Copied
Thank you very much Chris and JJ1138. I made the test with openssl and keytool, and my certificate seems fine. That's great news!
Copy link to clipboard
Copied
Developers have to create a new app ID and a new entry in the Google Play Store creating a new certificate containing 2048-RSA.
And using the next AIR beta? Hope we can use the same app ID and entry.
Copy link to clipboard
Copied
FeDeGbR89: The AIR version doesn't matter at all. This is not an AIR issue, it's a certificate sign issue. Event apps that started as AIR apps but have since then moved on to the native version (but keeping the same certificate/id) are suffering from the problem.
Copy link to clipboard
Copied
Just added a new blog post that describes the current problems and workarounds. We've also provided a beta version of ADT (linked in the post) that fixes the 1024-RSA issue with new applications.
Copy link to clipboard
Copied
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?
Copy link to clipboard
Copied
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
Copy link to clipboard
Copied
this problem fixed on Android 5.0.1
Thanks for your support!
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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.