Troubleshooting of Custom Permission issue on Android 5.0

In-App Purchase for Android 5.0 

Troubleshooting of Custom Permission issue on Android 5.0  

+ Posted : 2014-11-13

Hi, this is T store developer center.

On recently launched Android 5.0 Lollipop, applications with the same custom permission must have the same Signing Key, due to the changed security policy.  Because of that update of safety regulation, we distributed the latest version of T store IAP SDK (Ver 14.01. 01). with many security updates and we also decided to erase custom permission in this latest IAP version to support Lollipop.  

In addition, starting from the 13th November, we also updated T store developer center to check up that custom permission in advance to minimize your inconvenience when you update your new APKs. You can see an error pop-up windows like [Figure 1] below when you update the APK with the previous version of IAP. 

[ Figure 1: the new Error pop-up windows about Custom permission]

How To update new SDK?

All you have to do for this update is very simple! 
Just follow the steps below

1) Library replacement 

Please replace it with a latest version, 14. 01.01(hot-fit), through T store IAP library

2) Delete custom permission

You need to delete the permission below that has been declared at AndroidManifest.xml

<uses-permission android:name="com.tmoney.vending.INBILLING" /> 
<permission android:name="com.tmoney.vending.INBILLING" />

3) Change API_verison (2)

From now on,  API version matched on SDK Version should be clarified on Android manifest file.

<meta-data
                   android:name="iap:api_version"
                   android:value="2" />

- the Previous version In-App Purchase SDKs have API_version fixed to 1. From newest version (v14.01.01) API_version '2' is applied.
- Please check out the manifest file if you use API level coordinated with version(v14.01.01) and see the unopen In-App payment window.

When APK is updating, things changed are following

APK file that applied existing V13.01.01 or less will be rejected in the review process. In addition, as we examine your Androidmanifest.xml when you upload new APK files to check Custom permission as [Figure 2] below

Specifically, the issues that you fail to upload new APK files are following: 
- com.tmoney.vending.INBILLING within uses-permission and permission is used, 
-  android:name="iap:api_version" within meta-data is indicated, the issue that the value is set as the value other than android:value="2"

[Figure 2] Workflow of new permission check logic in Dev Center

Other: Additional Information related to T money In-App Purchase

Users have to update their T-money app due to the update of Android 5.0. However, you don't have to worry about the fact that users' app is not updated. That's because T store SDK is providing Toast message like the [Figure 3] below for helping users not to be in panic.

[Figure 3: Toast message ]