Webhook showing as unregistered.

C

CDA

Member
Webhook that worked perfectly yesterday is now showing this.
Anything I can do without generating a new one and changing all my macros?
1727895105094.png
 
C

CDA

Member
Bit the bullet and generated a new ID, same problem. Tried again, same problem.

Now totally stuck as to what to do.

Generating the new ID's did connect to something as the old ID's now show as Invalid. New ID still showing unregistered though.
 
C

CDA

Member
Took a few attempts to refresh the token (said upload failed about 3 times) but then it worked.

Thank you.
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
Thanks for trying and updating me. I'm trying to get fully to grips with this occassional problem (which I can't easily recreate myself). The refresh token stuff should hopefully help and I'm going to try and make all this stuff happen automatically to hopefully avoid users ever getting in this state.
 
  • Like
Reactions: CDA
C

CDA

Member
MacroDroidDev said:
Thanks for trying and updating me. I'm trying to get fully to grips with this occassional problem (which I can't easily recreate myself). The refresh token stuff should hopefully help and I'm going to try and make all this stuff happen automatically to hopefully avoid users ever getting in this state.
Click to expand...
It's very odd as I created two webhooks the same day, one on my device and one on my partners device (for communication between the two device in a macro). Their webhook continues to work fine, but mine stopped after only a day or so.

Good excuse for me to create a new macro that tests both webhooks each day for errors.

Hope you find your gremlin.
 
C

CDA

Member
Back to having problems again unfortunately.

Again it's just my webhook that is showing as unregistered. Partners webhook is still fine and has had no problems since creating it.

I have refreshed the cloud token multiple times to no avail.
 
MacroDroidDev

MacroDroidDev

Administrator
Staff member
Thanks, I have received it. I have verified the details were correctly received by my server and that is working server side. However when the server tries to send the Firebase Cloud Message the Firebase server is complaining that your token does not exist. In all honesty I don't know how it's possible that Firebase on Android sends a token to my server that it thinks it does not exist.
 
  • Like
Reactions: CDA
C

CDA

Member
That's very weird. Exact same issue I had before. Even weirder that the webhook I created for my partner has worked flawlessly from day 1 yet I am on my 3rd webhook now. It must be something on my device surely?
 
C

CDA

Member
Update, I have tried generating a new ID 3 times now and each time it has failed in the same way.

I updated the app to the latest version. Didn't help.

EDIT: Finally after several attempts got a new ID working. We'll see how long this one lasts.
 
Last edited:
C

CDA

Member
Webhook gremlins are back again, once again only on my device. I think this is my 4th webhook ID to fail while my partner is still on ID number 1.
 
Endercraft

Endercraft

Moderator
You really are out of luck...
Are you rooted/made any changes to the device? What device are you using? Maybe Google Play Services is messing up.
 
  • Like
Reactions: CDA
C

CDA

Member
Endercraft said:
You really are out of luck...
Are you rooted/made any changes to the device? What device are you using? Maybe Google Play Services is messing up.
Click to expand...
Yeah it's very weird.

Good job I have a webhook testing macro that runs everyday so I can spot problems early. Shame though because I means I can't rely on webhook based macros for anything important.

No I'm not rooted. Only changes made are those needed for MD such as ADB permissions etc.
 
M

md_sgf

Well-known member
Is there a way to test a basic HTTP Request (GET) webhook?. As they often don't work, or if do, are very delayed. I have increased the default value of HTTP Server Request Timeout from 10 to 20 seconds (will this help?). Could I use a webpage to check for webhook sent/received?
 
C

CDA

Member
md_sgf said:
Is there a way to test a basic HTTP Request (GET) webhook?. As they often don't work, or if do, are very delayed. I have increased the default value of HTTP Server Request Timeout from 10 to 20 seconds (will this help?). Could I use a webpage to check for webhook sent/received?
Click to expand...

Just put the webhook address into a browser like chrome, if it works then you will get an "OK" message on the webpage.
 
C

CDA

Member
Got it fixed by wiping MD, creating a new ID didn't work.
Jamie very helpful but also seems rather stuck as to why my device is causing this problem.
 
You must log in or register to reply here.
Top