Troubleshooting(Mobile Galaxy)

This document helps you check frequent failure issues. It summarizes some failure examples of functional, contents and security issues in sequence. For each failure issue, support links are provided for you.

1. Functional Defects

Functional Defects
Issue Type Troubleshooting
1-1. Power Button
(Hold Key)
1-2. Back Key
  • Problem:
    Application does not go back to the previous activity when user presses Back key.( Android 2.0 and above)
  • Probable Cause:
    There might several activities running on a stack or on a background thread when user presses back key.
  • Suggested Resolution:
    Rearrange the paths of activities.
    Default behavior of android back key is to go back to the previous activity. Check onBackPressed() verse.
  • References
1-3. Test Information
  • Problem:
    Some of application functions cannot be verified due to the lack of test information provided.
  • Suggested Resolution:
    Provide proper test information if needed.
    • Test ID and password: When application requires ID and password for log-in or to use additional functions.

    • Video file: When application co-works with other devices, video file should show its functions working.
      When application uses its own purchase module. Video file should show its successful purchase.

2. Contents Defects

Contents Defects
Issue Type Troubleshooting
2-1. Application Title and Description Language
  • Problem :
    Application title and description language is not in English.
  • Probable Cause:
    Seller puts application title and description in some language other than English even s/he selects sales country more than 2.
    Seller selects incorrect sales country; s/he should have selected one local country to use local language.
  • Suggested Resolution:
    Use English when seller wants to service application in 2 countries at least.
2-2. Icon and Screenshots
  • Problem:
    Icon and Screenshots are not appropriate for all ages.
  • Probable Cause:
    Icon and screenshot images are not proper for all ages because they are too sexual, violent or horrifying.
  • Suggested Resolution:
    Check Age Rating Guide
    Icon and Screenshots should be for all ages.
2-3. Samsung Brand Usage
  • Problem:
    Seller uses Samsung identifiers including brand, logos, trademarks and graphics which are copyrighted or trademarked.
  • Suggested Resolution:
    Samsung brand and relevant identifiers are not released to be used.
    Brand Guidelines :
    If Samsung or Samsung Galaxy Store is in text for descriptive purpose, it’s allowed. (e.g. XYZ for Samsung)

3. Security Defects

Security Defects
Issue Type Troubleshooting
3-1. Android Debug Key
  • Problem :
    The android debug key is used for signing APK.
  • Probable Cause:
    This error is common if developer submitted your application on Samsung Galaxy Store seller office without changing of android debug key for signing apk.
    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:
    Developer needs to sign your application with your private key. For more details, refer to below guideline from Android.
3-2. Debuggable Option
  • Problem :
    Registered application is a debuggable APK.
  • Probable Cause:
    The debuggable attribute set to 'True' in the manifest file(android:debuggable="true").
  • Suggested Resolution:
    Disable the debugging option by setting the android:debuggable attribute to 'false' or removing the android:debuggable attribute from the tag in manifest file. For more details, refer to below guideline from Google.
    /tools/publishing/preparing.html [Turn off logging and debugging]