Development issue/problem:

I finally made one last keystroke for my application. Since my application uses Google Maps, I need to update all layouts to use the new API key from the application….. application.

I am now aware of the obligation to export a signed KPA for sharing, but what happens now? I think for further development and testing it would be easier to configure Eclipse to use my current keyboard instead of Debug…., but I haven’t found a way to do that? It allows me to set up an alternative debugging key, but I don’t think it’s the same.

I’m sorry if I misunderstood something.

How can I solve this problem?

Solution 1:

I was able to use the Google Play keyboard as my own debugger keyboard to help debug the purchase function of the application. The same is certainly true for Google Maps troubleshooting.

As Devonveld said, there are some reservations. But my solution was this:

  1. Copy your key somewhere.
  2. Change the password and alias of the key by following the instructions given here (as well as Devunwired’s recommendations to make it look like a debugging keystore).
  3. Change the settings in Eclipse > Android > Assembly > Custom Keyboard Configuration based on the path to the copy you made in step 1.
  4. Let’s go, let’s go, let’s go, let’s go!

Solution 2:

You can configure a custom keyboard menu to use in debugger builds (the ones that occur when you click Run…) in Eclipse by going to Preferences -> Android -> Build and entering the filename in the custom debugger keyboard menu option.

However, it must follow the same rules as a traditional keyboard debugging protocol:

  1. The keyboard password must be android.
  2. It must contain a key named androiddebugkey.
  3. The password on this key must be android.

So, if you can sign your applications in debug mode with the same storage key as in export mode, your production storage key should look like a debug key, which makes it less secure if someone has access to the file (it would be easier to check and guess the passwords).

HTH

Solution 3:

To automatically connect Eclipse for you during implementation, you need to configure a keyboard that behaves like a debugger’s keyboard store. This means that there must be an androiddebugkey and the key and keyboard password must be androids. So here’s what I recommend:

  1. Make a copy of your keystore, I copied mine to a file called iap.keystore.
  2. Open a terminal/commands window with keytool on the path (for me, the path is D:NVPACKjdk1.6.0_45binkeytool.exe) or use the full path of the keystore in the following commands
  3. Change the keyboard password to android :
    • important tool -storepasswd -keystore iap.keyystore
    • Follow the request to enter your old keyboard password
    • Follow the instructions to enter android as a new password.
    • Follow the instructions to confirm that the android is the password.
  4. Rename the key to androiddebugkey (replace Old_Key_Store_Name with the name of the current key in the next command).
    • key tool -changealias -keystore iap.keyystore -alias Old_Key_Store_Name -destalia’s androiddebugkey
    • Follow the request to enter the password for your keyboard (which is now Andoride).
    • Follow the request to enter your Old_Key_Store_Name password (this is the value you previously set for your password).
  5. Change the password of your androiddebugkey
    • key tool -keypasswd -keystore iap.keyystore -alias androiddebugkey
    • Follow the request to enter the password for your keyboard (which is now Andoride).
    • Follow the request to enter your androiddebuggy password (this is the password of the previous key).
    • Follow the instructions to enter android as a new keyword.
    • Follow the instructions to confirm that the android is the password for the key.
  6. You now have a (one-key) keyboard with which Eclipse can automatically sign assemblers.
  7. Shut up! Shut up! Shut up!
  8. Window -> Settings -> Android -> Building
  9. Follow the Custom debug keystore link and navigate to the iap.keyystore file we created earlier.
  10. OK

From now on, when you run / debug your project, it will use the keyboard we just set up to sign your project. It makes things like AIP work.

WARNING: It’s convenient, but of course, if someone gets their hands on your iap.keyystore, they can sign things like you using android as their keyboard/keyword password. Hopefully this comes from the steps above, but only a second to understand what this means for you (or your company). On this basis, decide whether the risks are acceptable and whether you need to take additional measures to secure this file.

Solution 4:

We have configured a custom keyboard menu to use for our debugger builds. Eclipse Go to Settings -> Android -> Create and enter the filename in the Custom Debugger Keyboard window.

This is important when configuring our keyboard memory for the eclipse inch

The keyboard password must be android
. It must contain a key named androiddebugkey
. The password for this key must be android
. For example, you can sign your applications in debug mode with the same keyboard you are exporting from, but your production keyboard should look like a debug keyboard, which makes it less secure if someone has obtained the file (it would be easier to check and guess passwords).

if we want to change the keyboard password: $
keytool -storepasswd -keystore my.keystore

if we want to change the password for the keyboard alias: $
keytool -keypasswd -keystore my.keystore -alias my_name

if we want to change the alias of the keyboard: $
keytool -changealias -keystore my.keystore -alias my_name -destalias my_new_name

Vkj
Fill in the image description in here

Solution No 5:

Here are the instructions for converting a normal keyboard unit to a debugging unit:
https://stackoverflow.com/a/15754187/917362.

Solution No 6:

You can both debug and share SHA1 for the same Google API key through the Google Developers Console (console.developers.google.com).

This way you have the same API key for both, and you don’t have to change it in AndroidManifest.xml.

Solution No 7:

We had the same problem in our office a while ago. Because we often needed it, we wrote a simple script to facilitate the conversion of share keys into debug keys.

The script is available at https://github.com/IntellexApps/key2debug.

We’ve been using it for a while, so it should be pretty stable.

Cheers!

Good luck!

eclipse keystore location,this version of the application is not configured for billing

You May Also Like

Video memory management internal error in Windows 10

Before you start troubleshooting, we recommend that you update Windows 10 with…

Solve [pii_email_84e9c709276f599ab1e7] Easily |

In our blog, we offer solutions to various types of problems you…

What is the Difference Between OTF and TTF Font Formats

RECOMMENDED: Click here to fix Windows errors and optimize system performance. Maybe…

How to Hard Reset Vivo Y11 (2019) Android Phone (If Forgot Password)

Here is the complete guide on how to hard reset your Vivo…