- Go to File > Project Structure
- Select your project then go to Signing Tab
- Under Store File, click the + button and select your custom keystore file
- Enter the key alias, password and the store password
Make sure you have OpenSSL installed. If not, download and install it to your desktop according to either 32 or 64 version.
Once installed, make sure that it is part of the system path so you can execute OpenSSL anywhere.
To get the key hash of your Android app, go to where your keystore file is located and type the following.
keytool -list -alias [ALIAS_NAME] -keystore [KEYSTORE_FILE] | openssl sha1 -binary | openssl base64
GWT‘s Same Origin Policy (SOP) problem is common especially for newbies. This happens if your GWT front end client accesses a remote service that is hosted in the same local domain in your PC but having a different port.
Browsers still considers this a violation of the SOP policy. I have read that Internet Explorer has a lax web security policy so you may be able to use that without encountering this restriction. However, Internet Explorer sucks and Firefox is just too damn heavy to load even with just one tab.
So I am left with Google Chrome. You can run Google Chrome with web security disabled but I would advise you to create it as a shortcut in Windows and create an alias in Mac OS. Here is how I did them.
Note: you can rename it any name you want. I just used chromegwt so I would know that this Chrome is used only for GWT purposes.
Remember not to use this same browser when browsing the web as it can lead to disastrous results.