We have an application that has been running in production for several months that logs users in and then attempts to pull their email address via a call to /account/verify_credentials. Our application is whitelisted and all options are configured properly in the app’s settings.
For most users, this call returns their email address as it should and everything is OK. For other users, /account/verify_credentials does not return the email field; it is missing completely from the data returned by the API as if the application wasn’t whitelisted or set up correctly, which we know is not the case as other users work.
It seems like this issue began occurring sometime last week (Wednesday or Thursday) as that is when some of our automated tests began failing (the test user’s email disappeared from the API data; it had previously worked for months). In attempting to debug the issue, developers from our team tried running through the flow and it worked correctly for them (/account/verify_credentials returned their email addresses as it should).
Question: has anything with the API changed recently that could cause the email field to not appear for certain users? Is there any way to debug users that fail to determine why they fail? Has anything changed with account settings or anything like that which would prevent the API from returning the user’s email?