Closed GoogleCodeExporter closed 8 years ago
Hmm, we're looking into this.
It may be possible that you registered your consumer key for
one-360@appspot.com, so
the new wave will be created by that participant id, but then, the robot is
responding
to events for 9.latest.one-360@appspot.com, which can't modify the participant
role.
What app ID did you register the consumer key for?
Original comment by pamela.fox
on 7 May 2010 at 1:20
I did register the consumer key for one-360@appspot.com. If that explains the
failure
it doesn't appear to explain why it doesn't fail when creating the wavelet with
the
other newWave(...) methods?
Original comment by peter.o....@gmail.com
on 7 May 2010 at 7:37
I tested running robot with the version I registered the consumer key for. The
results
were the same. Included are the code I run and the log output.
Original comment by peter.o....@gmail.com
on 7 May 2010 at 8:26
Attachments:
I suddenly realized that it was an issue with my appengine application and not
with
wave. Terribly sorry for the hassle I caused. For some reason the wavelet
created with
newWave(domain, participants, msg, proxyForId, rpcServerUrl) got dispatched to
a
version of the robot which I had deleted!? I deployed to a fresh application id
and
everything worked as it should.
With apologies,
Peter
Original comment by peter.o....@gmail.com
on 7 May 2010 at 9:34
Okay, thanks for updating.
Original comment by pamela.fox
on 7 May 2010 at 10:08
Original issue reported on code.google.com by
peter.o....@gmail.com
on 6 May 2010 at 10:26Attachments: