I as well am having this problem, however not with fetchWavelet. I'm
using the code:
Wavelet newwave = MyRobot.newWave(domain, participants);
JsonRpcResponse response = MyRobot.submit(newwave,
RPC_SERVER_URL).get(0);
This, like all of your comments, was working for me before the
weekend. Now I'm getting the same error:
com.google.gson.JsonParseException: The JsonDeserializer
StringTypeAdapter failed to deserialized json object {} given the type
class java.lang.String
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:
63)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:
88)
at
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:
76)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:98)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:
73)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:
51)
at
com.google.wave.api.impl.JsonRpcResponseGsonAdaptor.deserialize(JsonRpcResponseGsonAdaptor.java:
74)
at
com.google.wave.api.impl.JsonRpcResponseGsonAdaptor.deserialize(JsonRpcResponseGsonAdaptor.java:
42)
at
com.google.gson.JsonDeserializerExceptionWrapper.deserialize(JsonDeserializerExceptionWrapper.java:
50)
at
com.google.gson.JsonDeserializationVisitor.invokeCustomDeserializer(JsonDeserializationVisitor.java:
88)
at
com.google.gson.JsonDeserializationVisitor.visitUsingCustomHandler(JsonDeserializationVisitor.java:
76)
at com.google.gson.ObjectNavigator.accept(ObjectNavigator.java:98)
at
com.google.gson.JsonDeserializationContextDefault.fromJsonObject(JsonDeserializationContextDefault.java:
73)
at
com.google.gson.JsonDeserializationContextDefault.deserialize(JsonDeserializationContextDefault.java:
51)
... etc.
Pamela, I noticed that there was a new version of the Wave Preview and
Sandbox rolled out (as updated today in the Google Wave Server
Changelog found at the waveid: googlewave.com!w+AU-ZLT_uA). Is it
possible some change in the build over the weekend broke the JSON/GSON
parser? I tried downloading the new API jars and republished my robot,
but to no avail. This breaks my robot. Any insight?
Thanks,
Taylor Ralston
--
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en.
