Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt to Google requirements for syncing data after July 15th 2019 #1171

Closed
Flohack74 opened this issue Jun 30, 2019 · 10 comments

Comments

@Flohack74
Copy link
Member

commented Jun 30, 2019

Google gives us the kick

Since a few days users get strange warning emails from Google about the "Ubuntu" app being limited in functionality after July 15th 2019. Work out what needs to be done to prevent any loss of sync connectivity here.
see also this link

@Flohack74 Flohack74 added this to To do in OTA-10 via automation Jun 30, 2019

@Flohack74 Flohack74 moved this from To do to In progress in OTA-10 Jun 30, 2019

@dobey

This comment has been minimized.

Copy link
Member

commented Jul 2, 2019

I think "fixing" this, just means changing the Google accounts code to not request access to gmail stuff via OAuth 2 token.

@UniversalSuperBox

This comment has been minimized.

Copy link
Member

commented Jul 3, 2019

This is our current understanding of the situation:

After the July 15th deadline is reached, users should not lose access to any Google account data stored on their Ubuntu Touch device. Only GMail access is being denied, which the system does not use. Contacts and calendar sync should continue normally.

There has been confusion about the GMail webapp which may use these permissions, but it seems it will continue to work. If it does not, even creating a new key will not help since we will need special permission from Google to continue using this data.

We are in the process of creating a new OAUTH token for Ubuntu Touch. This token will request access to the data that Ubuntu Touch needs, which does NOT include GMail. Having this token created for ourselves is to allow us to have control over our Google integration.

We are currently waiting for Google to approve our request for these credentials.

We are unsure if users will need to log in to their Google account again when the new token is put into place.

This issue does NOT need to be fixed before OTA-10 may be shipped. The key we inherited from Canonical will continue to work, albeit without access to GMail data.

@mardy

This comment has been minimized.

Copy link
Member

commented Jul 4, 2019

I confirm that this does not affect the Gmail Webapp at all: it would affect the old GMail webapp by Canonical (that one had some sort of integration with Online Accounts), but the "GMail UT" application -- which is the only gmail application I can find in the OpenStore -- does not use Online Accounts.

@Flohack74

This comment has been minimized.

Copy link
Member Author

commented Jul 4, 2019

Ok so we can close here? Or remove this one from OTA-10 but leave it open for changing the API key what we should do anyways.

@mardy

This comment has been minimized.

Copy link
Member

commented Jul 4, 2019

I suggest removing the OTA-10 tag, but keep this open.

@UniversalSuperBox UniversalSuperBox added this to To do in OTA-11 via automation Jul 5, 2019

@UniversalSuperBox UniversalSuperBox removed this from In progress in OTA-10 Jul 5, 2019

@UniversalSuperBox UniversalSuperBox added this to To do in OTA-10 via automation Jul 19, 2019

@UniversalSuperBox UniversalSuperBox removed this from To do in OTA-11 Jul 19, 2019

@UniversalSuperBox

This comment has been minimized.

Copy link
Member

commented Jul 19, 2019

Will be fixed by ubports/account-plugins#33

@UniversalSuperBox

This comment has been minimized.

Copy link
Member

commented Jul 31, 2019

OTA-10 automation moved this from To do to QA Jul 31, 2019

@jezek

This comment has been minimized.

Copy link

commented Aug 8, 2019

There is OTA10 call for testing in progress. How can we test this?

@UniversalSuperBox

This comment has been minimized.

Copy link
Member

commented Aug 13, 2019

This can be tested by adding a Google account to your device.

@jezek

This comment has been minimized.

Copy link

commented Aug 13, 2019

FP2 (2019-W32) - Fixed

Note: After update, calendar won't synchronize. I had to remove google account and add new one from scratch. Any changes between update & setting new account are lost.

@UniversalSuperBox UniversalSuperBox moved this from QA to Done in OTA-10 Aug 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
5 participants
You can’t perform that action at this time.