July 24, 2020

We are currently aware and dealing with issues affecting Pocket Informant iOS/Mac sync with Google Calendar, Google Tasks, and the “Sign In with Google”. This is also affecting Google Tasks on Pocket Informant Android. We are working with Google to resolve this ASAP.

Google has made changes to their OAuth approvals and it has been affecting many apps connecting with Oauth. We have submitted our app for review weeks ago and we are waiting for approval or responses from Google.

Google is requiring developers to request “least privileges” on API requests. Because Informant requests access to Calendar, Tasks, and Gmail (for purposes of converting emails to task), we are considered a “high risk” application and the review process goes slower.

We are making plans for multiple outcomes of this change from Google. One possible outcome is changes to the feature that converts emails to tasks. We may need to remove the option to delete an email.

We will keep you updated on progress.

[Update July 30, 2020: We updated our submission request yesterday to exclude the full permission for deleting emails. We are attempting to get this approved by Google & may or may not attempt to bring the feature back in the future. ]

[Update July 31, 2020 1:24 MDT, We have received a reply from Google. They are requesting us to remove the request to edit/delete mails items. We are complying with this. This will mean that Pocket Informant will NOT be able to delete an email after converting it to a task. We are re-submitting this change to Google for approval. Hopefully they will approve the Oauth consent screen this time]

[Update August 6, 2020 10:17 AM MDT: We’ve submitted the required changes that Google requested. At this time, we are still waiting for a reply.]

[Update August 13, 2020 12:17 AM MDT: Google approved our request and our account is now verified by Google. Our Google Task and Google Calendar features are up and running again. Despite being approved, we are still experiencing issues with our Gmail feature. We are looking into it and will release a fix as soon as possible.]