Pushchut - Not receiving notification, Error: No devices found with push tokens

Hi There.

I have been a long time user of pushcut and never had an issue until recently when I switched phone (but the last 2 or 3 phone changes were without issues…).

I use a shortcut (with url and get content of url) to trigger when a motion sensor detects motions. I do get the home app notification that motion was detected but nothing from pushcut.
When I manually run that shortcut (with the url and get content of url) the result window shows:

{“error”:“No devices found with push tokens.”}

Any idea what is causing this and what I could do to fix it?

I am signed in to the same icloud and account in pushcut/ios, i have tried generating a new secret and updated my url, under “devices” i do see the “current device” being shown and no other devices are listed there.

Thanks!

Sorry, missed this topic when it was originally posted.

Are you sending the notification to a specific device or all your devices?
Could you send your account ID (Account → Button in the top left corner → About → Scroll down and tap “Account id”) to feedback@pushcut.io so we can take a look at this?

I’m having the exact same issue, and it seems to have started after I switched over to a new phone. Will send an email to the feedback@pushcut.io account. Thanks!

Hi,

Bumping this old topic as new year, new phone, and again, pushcut url in shortcuts are not working. Getting an error no device found with push token.

Is there a specific process when moving to a new phone as it seems that pushcut gets stuck. Any way to full reset the system? I tried several times to generate a new key but that makes no difference.

Thanks.

Ofc I post and decide to re-delete and re-add the app for the 10th time and now it works. But I was ok 5G.

I’m wondering if during initial setup, pushcut is trying to talk to some domains my dns is blocking.

Is there a list of needed domains that are needed for pushcut to work properly ?

Thanks

Sorry I missed this. Generally, force-quitting the app should resolve this but if that doesn’t work then re-installing the app—as you did—should fix it.

We’re working to improve this flow in future releases.

We don’t maintain a comprehensive list, but Pushcut uses Firebase for authentication, cloud functions, such as messaging and storage, analytics, and hosting. For those functions we hit the following routes:

  • *.googleapis.com
  • *.firebaseio.com
  • app-measurement.com
  • *.crashlytics.com

We do, of course, also hit the Pushcut API at api.pushcut.io

I’d recommend against blocking any of those.