The app will crash due to an uncaught ObjectNotFound exception in `ParseUserProvider->retrieveById()`

[triztian]

Returns null when the retrieveById() function searches for an user that does not exist and the session has not been closed. It only handles the Object not found exception.

Refer to this code segment on the parse sdk to see where the exception is thrown:

• https://github.com/ParsePlatform/parse-php-sdk/blob/master/src/Parse/ParseQuery.php#L79,L97

[nicklee1990]

what are your through RE my comment regarding referential integrity (housekeeping) and allowing users of the repo to catch this exception themselves? Anyone using Parse should have something in their handler file for Parse Exceptions, as this aligns with Parse's documentation on Exceptions. I believe your code belongs there in your Laravel Handler.php class.

My concern is that this is a valid exception, and should be handled by app specific logic. By implementing this pull request, we're taking away the ability for users to 'cleanup' their data. Nosql DBs like Mongo (and therefore Parse) rely on applications to manage data integrity including referential integrity