This has been a problem for the last several days. When using the API to send push notifications, I almost always get back a 210 response from Push Woosh with the error "No valid devices in the list". Since these notifications can't be sent, they queue up on my end, sometimes resulting in tens of thousands that are still waiting to be sent. The only way that I've been able to get Push Woosh to actually send them is to log into the Push Woosh admin and enable Debug Mode for Push History. I can't imagine why this does anything, but within seconds of doing this, my push notifications begin sending.

This has happened 4 or 5 times over the past 3 days and is becoming a real hassle. I have a support ticket open, but the turnaround time of 12 hours is not nearly fast enough when there's an issue like this... I can cut over to a different push service in half that time.

Any thoughts on what could be causing this?

Edit: Push Woosh has lost me as a customer - if I had not found this manual workaround purely by chance, I would have been without notifications for nearly two days. Extremely unresponsive support for a paying customer. Bummer. I've requested that they update this thread with a solution so it might at least help others experiencing the same problem.

asked 02 Sep '16, 13:23
asanger's gravatar image

asanger
113

edited 02 Sep '16, 19:01

I FACE THIS PROBLEM TOO, JUST ANNOYING

permanent link
answered 02 Sep '16, 15:48
haja's gravatar image

haja
111

Glad I'm not the only one! How long has this been going on for you? Just started for us on August 31st.

(02 Sep '16, 16:14) asanger asanger's gravatar image

As far as I can see, there is a ticket from you in our Support system, and my colleague have provided an answer there.

permanent link
answered 05 Sep '16, 13:04
idedov's gravatar image

idedov
2363

The only thing in the ticket, which was responded to at 2am this morning, is that the information was passed on to the developers.

(05 Sep '16, 13:18) asanger asanger's gravatar image

Apparently, your API request is not processed correctly if it begins with the invalid token. Please make sure that you are using valid tokens in your request.

permanent link
answered 05 Sep '16, 13:38
idedov's gravatar image

idedov
2363

Do you know if this is a bug that will be fixed, or is this just now the way that the API will work going forward?. Is there a way to validate tokens so that I can purge any that are considered "invalid"? Do you know what constitutes an invalid token?

(05 Sep '16, 16:08) asanger asanger's gravatar image

@asanger yes, it was a malfunction which occurred in the query processing. I would like to inform you that it has been successfully fixed by our engineers this morning. From now on it should be back to normal. Please accept our apologies for the inconvenience!

Is there a way to validate tokens so that I can purge any that are considered "invalid"? Do you know what constitutes an invalid token?

Generally, our SDK keeps your user base up to date. If the push token of your device is returned by the APNs as invalid (due to sending push to the wrong gateway, for example), it's being cleared from our system.

permanent link
answered 06 Sep '16, 05:21
idedov's gravatar image

idedov
2363

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×444
×120
×91

question asked: 02 Sep '16, 13:23

question was seen: 632 times

last updated: 06 Sep '16, 05:21