Skip to main content
Samsung Developer Program

Troubleshooting Certification Failures

This section describes common issues that result in failing certification, their most probable cause, and their suggested resolution.

Functional Issues

Power Button
(Hold Key)

The current activity is not paused when the user presses the power button.

Probable Cause:  The onPause() callback was not properly invoked.

Suggested Resolution:  Make the power button call onPause() before making any other calls.

References:

Back Key

 

For Android 2.0 and above, the app screen does not return to the previous screen when the user presses the back key.

Probable Cause:  When the user presses the back key, several activities are running on a stack or on a background thread.

Suggested Resolution:  Rearrange the paths of activities. The default behavior of the Android back key is to return to the previous activity. Check the onBackPressed() verse.

References:

Test Information

Some application functions cannot be validated due to the lack of information provided during Seller Office registration.

Suggested Resolution:  

In the Seller Office UI, provide the following.

  • When your app requires a user ID and password for app login or to use additional app functions, provide a user ID and password to be used by validation testers.

  • When your app co-works with other devices, provide a video file that shows its functions working.

  • When your app uses its own in-app purchase module, provide a video file that shows a successful purchase.

Content Issues

Application Title and Description Language

In the Seller Office registration, your app title and description were not entered in the English language and your app is to be distributed to more than one country.

Suggested Resolution:  

Either:

  • Change your app distribution to one country, suitable for the title and description language.

  • Change your app title and description entries to English.

App Icon and Screenshots

 

Icon and/or screenshot images are not suitable for users of all ages, for example, they are too sexual, violent, and/or horrifying.

Suggested Resolution:  In the Seller Office UI, register new icon and/or screenshot images that are suitable for users of all ages.

References:

  • Seller Office Age Rating Guidelines

Samsung Brand Usage

Seller uses Samsung identifiers (including Samung brand name, logos, trademarks, and/or graphics) that are copyrighted or trademarked.

NOTE:  Samsung brand and relevant identifiers are not released to be used. However, you are allowed to use the terms 'Samsung' and 'Samsung Galaxy Apps' and 'Galaxy Apps' in text for descriptive purposes (for example, 'XYZ for Samsung').

Suggested Resolution:  In your app UI, follow the Samsung brand guidelines at http://www.samsung.com/us/common/legal.html

Security Issues

Android Debug Key

An Android debug key was used for signing your app.

Probable Cause:  One or more of your binary files registered via the Seller Office UI use an Android debug key to sign your app.

Example Android debug key:

  • Keystore name: "debug.keystore"

  • Keystore password: "android"

  • Key alias: "androiddebugkey"

  • Key password: "android"

  • CN: "CN=Android Debug,O=Android,C=US"

Suggested Resolution:  In your app code, sign your app using your private key.  Re-register your app binary file(s) via the Seller Office UI.

References: 

Debuggable Option

Your app registered via the Seller Office UI is a debuggable APK.

Probable Cause:  In your app manifest file, the debuggable attribute  is set to 'true' in the manifest file (android:debuggable="true")

Suggested Resolution:  In your app manifest file, set the debuggable attribute set to 'false' (android:debuggable="false") or remove the android:debuggable attribute from the <application> tag. Re-register any app binary files in the Seller Office UI.

References:

 

  • Was this article helpful?