February 27, 2012 3:12 AM
Figgered it out, seems to be a documentation bug: I remembered that the parameter had another name a couple of days ago: it's not "to_ids", but "user_ids[]".Everything works fine with user_ids[] ...Question: will the documentation be changed, or will the parameter name change?Cheers,Thomas
On Monday, February 27, 2012 12:04:51 PM UTC+1, Thomas Huhn wrote:
February 27, 2012 3:04 AM
March 23, 2012 3:41 AM
Hi Wei,sorry that I have to get back to this problem. After doing some thorough testing on different devices, I still face the strange behaviour that notifications are send to ALL devices subscribed to a channel, whatever you put into the "user_ids" parameter.Examples:I login ascurl -b cookies.txt -c cookies.txt -F "login=gya4f_34897676-c86d-4c5e-b465-6e270572a984" -F "password=PASSWORD" http://api.cocoafish.com/v1/users/login.json?key=KEYand send to another usercurl -b cookies.txt -c cookies.txt -F "channel=com.solutionmedia.getyourapp4free" -F "user_ids=4f6c4931356f4e53dc002a44" -F "payload=test to admin" http://api.cocoafish.com/v1/push_notification/notify.json?key= KEYbut ALL users receive the message, even the one who was sending.I've tried different parameters too:user_ids : status ok, sends to all usersuser_ids[] : status ok, sends to all usersto_ids : status ok, but no notification receivedto_ids[] : error "wrong parameter format"Could you please have a look? I think to have this functionality running in a stable manor is really mission critical for many apps.Thanks,Thomas
On Monday, February 27, 2012 11:58:35 PM UTC+1, Wei Kong wrote:
February 27, 2012 2:58 PM