Having trouble with Webhook

Hello, it is now days (4-5 ?) that my macro doesn't trigger anymore by webhook... I did reset the data of Macrodroid but without more sucess...

Android 7.0
Not Rooted
Samsung Stock ROM

Ok, I did receive all my requests (in the same time of my YouTube notifications). And that it... It doesn't work anymore... What could I try to mitigate the problem?

MicroG? I know when I use it I receive all my YouTube notifications at once and because the webhook system works the same way that's probably the cause. Try using Google's native app instead.

@Sylv1_Durif Please use report a bug in the troubleshooting section and I can check the backend to see if your device id is uploaded correctly.

Bug report sent

New "wave"

I don't seem to be having problems with Macrodroid, but more with Firebase Cloud Messaging, as YouTube also seems to be affected (hence the fact that I received the YT notifications at the same time as my macro started up...).

Are you using Google app or a third-party modification of it?

No, I have fresh stock apps, everything from the store, nothing rooted. I can't do a factory reset because the phone is temporary (mine broke ). But I have no idea what to do to solve the problem... I'll probably open a thread on XDA because in the end it's not a Macrodroid problem (I'm always open to suggestions). Do you know how to increase the logging level? I thought the option existed but I can't find it...

Having issues with it today as well. I can do a GET or POST and it'll return 200 which is good. I can also see "OK" if I enter the webhook URL into my browser. But nothing is triggered on my phone, nothing showing in the logs at all. I've got no constraint configured, it's just a very simple webhook trigger. It was working fine last night and I can't get it to work atm.

UPDATE:

I just tested on another device and it's working fine. So it seems something is broken on my first device. However, I haven't made any changes to MacroDroid. But my device did get a ROM update last night though, although it was a minor update and not a major one.

What does MacroDroid rely on in order to process incoming webhook calls? Like, what external app does it require? My Google Play Services is running just fine and is enabled, which is apparently all that is required here. My Google Play Services version is 23.49.14 (190400-590296185).

UPDATE 2:

I just tested Slack by getting my friend to send a message to me. Slack apparently uses FCM and I was able to receive notifications for the Slack messages. Slack was not auto-started and is running in the background, not foreground. This would suggest that FCM is working fine for me.

I also tried *#*#426#*#* to get to the FCM diagnostic page and it all seems OK, says connected and if I look at events, I can see "Successful broadcast to com.Slack....." just fine. I used this guide for reference btw:


Whereas when I do a webhook call, I don't see it in the FCM events.

I've tried reinstalling MacroDroid, also tried generating a new device ID for the webhook, same issue.

I'm not sure why MacroDroid webhook is broken here and at this point I don't know how else to troubleshoot it.

That's weird. If fcm works, the server works and reinstalling doesn't fix the only thing I can consider is you have a modified version of the app. If that's not the case contact the developer at support@macrodroid.com for further troubleshooting.

Nah I'm using a paid version of the app. It's so worth it.

@MacroDroidDev - any ideas about this one?

After some more digging, I believe I found the issue, although I have yet to confirm the fix.

After upgrading my ROM last night, I also applied the PlayIntegrityFix, which is needed if you want to pass root detection checks (my phone is rooted). Well, I came across this today:

I believe it's related. I have no idea why Slack FCM broadcast works, but it doesn't work for MacroDroid, Teams and Phone Link and all of those use Google Play Services to an extent I believe. I'm just doing a TWRP restore atm and will test it out later.


UPDATE:

OK, I fixed it. Turns out that it was indeed related to the PlayIntegrityFix.......had to reset the GCM token thing as per the guide above.