#Durrell
torn glacier
wise dune
whole aspen
Hello! I'm taking over and catching up...
If you add --log-level debug to your stripe listen command and then trigger one of these Events do you see any output on the command line related to it?
scarlet kiln
the logs are definitely more verbose this way.
whole aspen
Also can you tell me what stripe -v says about the version of Stripe CLI you're using?
Yeah, there's a lot of info in there. 😅
scarlet kiln
stripe version 1.13.0
I searched the terminal for issuing_authorization. and only found results for issuing_authorization.updated and issuing_authorization.created
whole aspen
Hm, interesting. Okay, one more thing to try: remove the --log-level debug part and add --latest then try triggering an Event again.
scarlet kiln
same thing. just the created and the updated.
whole aspen
And you're using stripe trigger issuing_authorization.request to trigger the Event, correct?
scarlet kiln
to be exact: stripe trigger issuing_authorization.request --stripe-account=acct_1LsqXMR8qpTsTbw8
whole aspen
Give me a few minutes to check some things...
whole aspen
It looks like this is an issue we're going to need more time to investigate. As a workaround, you can use a tool like ngrok to set up a public URL that forwards to your local environment, then create a Connect Webhook Endpoint in your Dashboard that points to that URL. Let me get some links to things...
https://dashboard.stripe.com/test/webhooks/create (make sure you choose to listen for Events on Connected accounts)
scarlet kiln
ok. Would I still be able to use the CLI to trigger the event or would I have to use code to trigger it as explained here: https://stripe.com/docs/issuing/testing?testing-method=with-code