Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It lookes like your AE setup is spot on. What I wouldn't expect is for the Remote Api to run on an Android handset. To connect via the Remote API, run it as a stand alone java process.</p> <p>Android java is just a subset of Java and so the remote API may use things not available on Android (though that doesn't seem the case here) So really aren't you better of <a href="https://developers.google.com/eclipse/docs/appengine_connected_android" rel="nofollow">setting up your Android project to connect to AE</a> in the way it was intended. I mean what are you going to do, ship your password to connect to your AE instance in your apk? There won't be any access control doing it that way and surely that isn't what you want, or do I misunderstand your purpose.</p> <p>EDIT:</p> <p>Why can't it run on Android? Maybe it can. The problems I see are:</p> <p>1) the <a href="https://developers.google.com/appengine/docs/java/jrewhitelist" rel="nofollow">Android Whitelist</a> may not contain all of the classes needed by the Remote API and even if it does now, there is no guarantee that future versions will work. </p> <p>2) you are hardcoding your password into your android application. this gives every user the credentials to do everything ... insert junk that you will have to pay for if billing is enabled, delete all your cherished data, etc. etc. OK so your users would have to be malicious and figure it out, but unless you can really trust your users and don't distribute your apk via the play store, I think it is a fact of life that apks get pirated and really question why you would give a pirate access to your datastore credentials. I am not saying you can't do it that way, but just pointing out hey in fact maybe you don't.</p> <p>If you use rpc calls (as linked above), you can limit what the client is able to do with the datastore. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload