Skip to content

GitLab

A
appinventor-sources
Commit e9f7d45c authored by ylwu's avatar ylwu
Browse files
Options

Merge branch 'master' of github.com:mit-cml/app-inventor-private into videocapture

parents 4d4da713 b1277d18
Hide whitespace changes
Inline Side-by-side
Showing with 83 additions and 6 deletions
appinventor/appengine/src/com/google/appinventor/client/OdeMessages.java
View file @ e9f7d45c
......@@ -773,6 +773,8 @@ public interface OdeMessages extends Messages {
@DefaultMessage("Do you want to overwrite your keystore file?\n\n" +
"If you agree, your old keystore file will be completely removed from the App Inventor " +
"server.\n\n" +
"If you have published applications to the Google Play Store using the keystore you are " +
"about to overwrite, you will lose the ability to update your applications.\n\n" +
"Any projects that you package in the future will be signed using your new keystore file. " +
"Changing the keystore affects the ability to reinstall previously installed apps. If you " +
"are not sure that you want to do this, please read the documentation about keystores by " +
......@@ -790,6 +792,8 @@ public interface OdeMessages extends Messages {
"If you agree, your old keystore file will be completely removed from the App Inventor " +
"server. A new, but different, keystore file will be created automatically the next time " +
"you package a project for the phone.\n\n" +
"If you have published applications to the Google Play Store using the keystore you are " +
"about to delete, you will lose the ability to update your applications.\n\n" +
"Any projects that you package in the future will be signed using your new keystore file. " +
"Changing the keystore affects the ability to reinstall previously installed apps. If you " +
"are not sure that you want to do this, please read the documentation about keystores by " +
......
appinventor/docs/learn/reference/other/appstoplay.html
View file @ e9f7d45c
......@@ -59,6 +59,11 @@
an initial <code>VersionName</code> could be 1.0 which can be updated to 1.1 after
a small change and 2.0 after a larger change.
</p>
<p>
You will need to increase the VersionCode and change the
VersionName of your application when you upload a new
version to the Play Store.
</p>
</dd>
<dt>
<h2>Download <code>.apk</code></h2>
......@@ -75,7 +80,7 @@
3. Click “Download to This Computer”<br />
</p>
<p>
This will prompt you to save the application somewhere. Once you have the .apk downloaded, you are ready to publish this app to Google Play.
This will prompt you to save the application somewhere. Once you have the .apk downloaded, you are ready to begin the publishing process.
</p>
</dd>
<dt>
......@@ -83,17 +88,85 @@
</dt>
<dd>
<p>
You can now go to <a href="https://play.google.com/apps/publish/Home">Google Play Publishing Home</a> and follow the steps to publish your app to Google Play.
You can now go
to <a href="https://play.google.com/apps/publish/Home" target="_blank">Google Play Publishing Home</a> and follow the steps to publish your app to Google Play.
</p>
<p>
For more details, you may want to start with <a href="http://developer.android.com/guide/publishing/publishing.html">Introduction to Publishing on Google Play</a>
For more details, you may want to start
with <a href="http://developer.android.com/guide/publishing/publishing.html"
target="_blank">Introduction to Publishing on Google Play</a>
and
<a href="https://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=113469&topic=2365624&ctx=topic">Google Support on Uploading to Google Play</a>.
<a href="https://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=113469&topic=2365624&ctx=topic"
target="_blank">Google Support on Uploading to Google Play</a>.
</p>
</dd>
<dt>
<h2>A Word about Backups</h2>
</dt>
<dd>
<p>
Once you publish your application in the Google Play
Store, other people will now be depending upon you to fix
bugs and otherwise maintain your application. It is
therefore very important that you backup your
application's source code.. Go to "My Projects", check the
box next to the name of your project and select
"More Options->Download Source." This will download a zip
file which contains your projects source code. Store it in
a safe place!
</p>
<p>
MIT and Google, which operates the App Engine service on
which MIT App Inventor relies, make best efforts to ensure
that MIT App Inventor does not lose projects. HOWEVER WE
CAN OFFER NO GUARANTEE THAT DATA (LIKE YOUR PROJECTS) WILL
NEVER BE LOST. IT IS IMPERATIVE THAT YOU MAKE YOUR OWN BACKUPS!
</p>
<h3>A Word about keystores</h3>
<p>
During the .apk building process your application
is <code>signed</code> with a digital private key which is
associated with your account. Whenever you build a new
version this same key is used to sign the new
version. When an android phone has an application
installed on it, it remembers the key that was used to
sign it. In order to install an updated version of an
application, the new application must be signed by the
same key. It is therefore important that you not lose this
key!
</p>
<p>
Your private digital key is stored in
a <code>keystore</code> file. Normally the MIT App
Inventor server will create this file when needed and
store it for you so you do not need to worry about
it. Although we do not anticipate losing your keystore
file, we recommend that you back it up. From the designer
under "My Projects", under the "More Options" menu there
is a choice labeled "Download Keystore". Select this
option. This will download your keystore file to your
local computer. Save it in a safe place. It
should <b>not</b> be publicly readable as your private
digital key is a secret which should not be shared.
</p>
<p>
If you move your project to another App Inventor server,
you will want to upload your keystore to that server (you
will see that under "More Options" there is a "Upload
Keystore" option as well). You only need to do this if you
are publishing .apk files to Google Play or if you intend
to share your application with other people in general.
</p>
<p>
IF YOUR keyfile IS LOST OR DELETED IT CANNOT BE RECOVERED. If you
were to lose your project's source code, you could always
re-enter it from scratch (this may be a lot of work, but
is something you can do). NEITHER YOU NOR MIT CAN RECOVER A
LOST keyfile. NO AMOUNT OF EFFORT WILL RECOVER IT, SO BE
SURE TO BACK IT UP!!!
</p>
</dd>
</dl>
</div>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment