Databases
StackOverflow2013
Postsdbo
POApp Engine Connected Android Project Error
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POApp Engine Connected Android Project Error
    primarykey
    data
    text
    <p>Setup: Windows7, Eclipse 3.7.1, </p> <p>Steps: 1. read and done all the tutorial in AppEngine connected android page (google) </p> <ol> <li>copy all the files from <a href="http://code.google.com/p/cloud-tasks-io/source/browse/" rel="nofollow">http://code.google.com/p/cloud-tasks-io/source/browse/</a> with minor changes (my app-id wherever needed, my c2dm email..</li> <li>deploy to app-engine.</li> <li>test the GWT side: login succeed, add tasks works (I can see that tasks are added in the Google dashboard).</li> <li>For testing the android side I'm debug as "Remote app engine Connected ..." </li> <li>In the my android device (Sunsung Galaxy II, 2.3.5) I pressed Menu --> Accounts --> Connect (to my email account - same as above).</li> <li>I'm getting notification : "Registered my_mail@gmail.com for.."</li> <li><p>I pressed Menu --> refresh and get the following exception (logcat):</p> <p>02-13 00:55:09.015: E/AndroidRuntime(25572): FATAL EXCEPTION: AsyncTask #1 02-13 00:55:09.015: E/AndroidRuntime(25572): java.lang.RuntimeException: An error occured while executing doInBackground() 02-13 00:55:09.015: E/AndroidRuntime(25572): at android.os.AsyncTask$3.done(AsyncTask.java:200) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:274) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.FutureTask.setException(FutureTask.java:125) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:308) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.FutureTask.run(FutureTask.java:138) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.lang.Thread.run(Thread.java:1019) 02-13 00:55:09.015: E/AndroidRuntime(25572): Caused by: com.google.web.bindery.event.shared.UmbrellaException: One or more exceptions caught, see full set in UmbrellaException#getCauses 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$StandardPayloadDialect.processPayload(AbstractRequestContext.java:387) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$5.onTransportSuccess(AbstractRequestContext.java:1108) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.cloudtasks.AndroidRequestTransport.send(AndroidRequestTransport.java:68) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext.doFire(AbstractRequestContext.java:1102) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext.fire(AbstractRequestContext.java:569) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequest.fire(AbstractRequest.java:54) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequest.fire(AbstractRequest.java:59) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.cloudtasks.AsyncFetchTask.doInBackground(AsyncFetchTask.java:31) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.cloudtasks.AsyncFetchTask.doInBackground(AsyncFetchTask.java:1) 02-13 00:55:09.015: E/AndroidRuntime(25572): at android.os.AsyncTask$2.call(AsyncTask.java:185) 02-13 00:55:09.015: E/AndroidRuntime(25572): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306) 02-13 00:55:09.015: E/AndroidRuntime(25572): ... 4 more 02-13 00:55:09.015: E/AndroidRuntime(25572): Caused by: java.lang.RuntimeException: Server Error: null 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.Receiver.onFailure(Receiver.java:44) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequest.onFail(AbstractRequest.java:118) 02-13 00:55:09.015: E/AndroidRuntime(25572): at com.google.web.bindery.requestfactory.shared.impl.AbstractRequestContext$StandardPayloadDialect.processPayload(AbstractRequestContext.java:359) 02-13 00:55:09.015: E/AndroidRuntime(25572): ... 14 more</p></li> <li><p>when I try to run again, same process, except pressing Menu --> refresh I tried to add new task. This time I didn't see any exception in logcat but I see in Eclipse (see attached pic in <a href="http://code.google.com/p/cloud-tasks-io/issues/detail?id=8&amp;thanks=8&amp;ts=1329087868" rel="nofollow">original question</a>): source not found - ThreadPoolExecutor.java</p></li> </ol> <p>PLEASE HELP ME!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNikunj Patel
    1. USItayB
    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.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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