T store in-app SDK, wrap-up for major developments for Android 5.0

Android 5.0

Major developments to support Android 5.0 Lollipop

+ Posted : 2014-12-03

Hi, this is the T store developer center.

Yeah, the winter is coming! Time surely flies, doesn’t it? I hope all of our developers reap best results through T store this year. Now let’s cut to the core. Finally in late November, the image of the official version of Android 5.0 Lollipop system was unveiled and, although more or less delayed than expected, OTA updates have started to be deployed in Google’s reference terminals such as Nexus 5 and Nexus 7. In addition, with G3 and Galaxy S5 being the first, manufacturers of terminals officially being distributed in Korea are planning to accommodate updates involving Android 5.0 Lollipop. I guess most Android users will very likely be able to use Lollipop in less than 1 or 2 months.

Along with platform SDK and emulator, Android 5.0 Lollipop has released for the first time “a preview version for developers” in its latest version. Thanks to this, developers were allowed to get an earlier taste of Android L and various features of the new version of Android. (See for reference: Let’s install Android L Preview – Manager Chunslmaro / T store technology development team ) 

Actually, the scope of Android 5.0 updates is quite large, as implied by the fact that the developer preview is distributed. From the material design which is the new UX to the new runtime ART, there are more changes than in any previous OS. As such, T store could not afford to just watch and do nothing any longer. The center has worked day and night to conduct rigorous tests to check numerous cases, such as whether customers using the new Android 5.0 platform have problems to use our developers’ products; or whether T store in-app payment or ARM is run properly on the new Android API 21-built app.

Here I’m sharing with you my conclusions drawn from the results. Hope you find this useful!

In-app development: All you need to do is change library and revise permission

As I posted in an announcement, Android 5.0 entails important security updates. Simply put, apps using user custom permission must use the same signing key. So far, many apps have created and used custom permission but it has been said to be vulnerable to risks including security problems, which is why Android 5.0 overhauled it.

Keeping these changes in mind, I sifted through problems and found that apps using earlier versions of T store in-app SDK that use customer permission were not being installed in terminals with Android 5.0. This is because some custom permission, such as T money (com.tmoney.vending.INBILLING), clashed.   

Keeping these changes in mind, I sifted through problems and found that apps using earlier versions of T store in-app SDK that use customer permission were not being installed in terminals with Android 5.0. This is because some custom permission, such as T money (com.tmoney.vending.INBILLING), clashed. 

[From November 13th, custom permission is being checked in advance when APK is uploaded ]

FAQs 

Q Will already-installed apps or games that are not updated be force removed when OS is updated? 

Nope! Overlapped custom permissions in existing apps will not be filtered out or force removed. Operation and in-app payment will not have problems, either. The only concern is that, due to clash of permissions, apps may not be installed when related products are updated.. 

Q Do I just need to remove the permission?

Yes. Just (1) change library, (2) remove permission from the manifest file and set API version and (3) build. And that’s it! Everything’s done :) 

Q I don’t want any further updates. Am I allowed to go without updates?

 Yes, you are. T store is configured to automatically support with OS 4.4 and earlier versions the products in which in-app updates are not installed. The center will always do our best to minimize your inconvenience. 

Q I’m currently developing target-SDK with 21 and having errors in using T money. 

I recommend you to use in-app SDK 14.01.01 (hotfix). 

As T money service can no longer use existing implicit intent, explicit intent has been introduced. The relevant content will be distributed via hotfix and you won’t have any trouble after you change library. 

For those who have not yet updated in-app SDK, I strongly recommend you to adopt 14.01.01 (hotfix). And for those who have already adopted v14.01.00, you won’t have any disadvantages such as examination or rejection so please adopt next version when it’s applied..  

Q During self-test process, when the value is set to OK Cashbag, I see a pop-up that reads “unavailable”. 

I sincerely thank you for using the self-test so well T.T 

From now on, OK Cashbag will only allow “saving”. From November 8th, in accordance with changes made to SK Planet’s internal policies, OK Cashbag, which has been the T store in-app payment tool, allows users to save only. Accordingly, OK Cashbag is blocked on self-test and live server. Please refer to the following announcement. 

■ Content: Upon using T store in-app payment (pay within app), payment using OK Cashbag will not be available

■ Schedule: Starting from 00:00 November 8th, 2014

■ Announcement: http://goo.gl/5jN736 

On that note, this is the end of today’s post. 
The T store technological support will always be the fastest and do the best. 
Thank you as always. 

Best regards, 

the T store developer center