Webhook - Not Receiving Activity Events

Hi, can you tell me what you mean by reauthenticate the app?   I’ve done the client oauth login again and authorised app permissions for read-all and so on, but still not getting any post events from Strava when I update, modify or create activities.  Wonder what else I might be missing.  I have verified that the access token I get back has the following scope:

read,activity:read_all,profile:read_all,read_all

And I can use it to query all the profile and activity data for my user.  The Strava developer page for my API shows I have 1 user connected.   When I de-authorize, I get the POST message at the right endpoint for my subscription, and behaves as I’d expect.  I just dont get anything when Im creating or updating activities as that user.  

One strange thing I notice is the strava my API page shows you your client secret and so on - but also shows an access token and refresh token, with scope “read”.  Why does it show these tokens here, what uses them?  And why are they only set to read?  Did I mess up when I generated the client secret?  Do I get a chance to set the scope when I generate a new one?

Same problem here as ​@russell.young . Does anyone knows how to solve it? 

The problem for me was my end - my endpoint wasn’t being called because some of the id fields in the post message were long ints, but my code was expecting just ints - so it couldn’t map them to the expected argument of my call, so I didn’t get to see the call even being started.  I figured it out by changing the post call just to not try and be clever and pre parse the body into an object, and instead did the json parsing within my code.  Hope this helps you out.  

For me, I needed to re-authenticate my app by deleting and re-creating the push subscription as shown in the webhooks documentation. Before I could recreate the subscription, I also needed to rename my callback URL.

For whatever reason, Strava kept reporting that it wasn’t getting a 200 response code from my webhook despite all tests showing that it was reachable and returning the proper code. Maybe there was some temporary problem and it was marked as unresponsive in Strava’s system, preventing all webhook calls or subscription requests from working. anyhow, once I renamed the callback URL, I was able to create a new subscription and the webhook calls started working again.