Closed Shaws-WD closed 4 years ago
Hi @Shaws-WD, unfortunately, I'm not able to reproduce this. Getting an exception thrown for all types of 400 responses. Even went so far as expiring all passwords in my dev org to see what happens.
I'd suggest trying to upgrade from 2.6
Thanks SO much for trying to replicate.
I'd suggest trying to upgrade from 2.6
I'm intending to do that but have been limited by our Laravel version. Your comments raised my priority of working through the Laravel upgrades
(btw, thanks so much for forREST for use by our non-profit!)
Short version I am encountering a problem with Forrest v2.6.0 under Laravel 5.4 The problem occurs with the Forrest call
when the users password expired.
I have that Forrest call in a try/catch structure
However when encountering this error, Forrest does NOT return an exception (ie. nothing detected by 'catch') Instead the error is silent and subsequent code fails
I am able to see the error only when I remove the try/catch and find an error logged by Laravel (as shown below)