HTTP Error 401: Unauthorized (Fixed in v71)

[nihil21]

Hi,
when pasting the authorization code into the plasmoid and clicking 'Submit', this message appears and obviously the calendar events from Google Calendar do not appear in the plasmoid.

I've installed the applet from KDE Plasma settings. My system information is the following:

• Manjaro Linux x86_64
• 5.8.18-1-MANJARO kernel
• Plasma 5.20.2

[Zren]

I'm currently trying to fix a quota limit in #171 caused by a few users who haven't upgraded in a year. I plan to ship an update by Friday at the latest which should re-enable Google Calendar sync.

[RickSlashee]

Same issue here, thank you @Zren

[nihil21]

Thanks @Zren

[TassieDevyl]

Same issue currently running version: 69.
Thanks for the update @Zren

[meronogbai]

Same issue here as well. Thanks @Zren

[Zren]

v71 with the updated API keys has been released. After updating, relog to restart plasmashell. It will then prompt you to login again to Google Calendar to sync the events. I'll be leaving this issue open as people will be googling this error for the near future.

[nihil21]

I can confirm it's working now. Thank you very much @Zren for your work!

[TassieDevyl]

Working again now.
Thank you @Zren

[JillSwift]

v71 working and so beautiful for it. Thanks, @Zren!

[david-cortes]

It's working correctly for me too, but I get a 0 error display at the bottom (HTTP Error 0: Could not connect. Will try again soon). The functionality is there though.

[shonnubaradee]

v. 71, worked yesterday, today I get HTTP Error 0: Could not connect. Will try again soon mistake, and no events from my Google calendar.

[decoherencer]

I am getting

Authorization Error 
Error 401: invalid_client
The OAuth client was not found.

when trying to login - while getting code from browser

[Zren]

Have you updated to v71 of EventCalendar then restarted plasma @decoherencer? All versions below v71 no longer work.

[decoherencer]

Thanks zren, restart seems to have fixed it.

[yuannan]

Thanks zren, restart seems to have fixed it.

For future reference and for other users.
You will have to update it via the GUI and restart plasmashell
sudo systemctl restart sddm
or as I prefer

sudo pkill plasmashell
plasmashell & disown

After this, right click on event calendar and reconfigure Google Calendar with a new key.
Worked for me. No reboot required.

[rocketraman]

Do I need a more recent version of KDE to install this version? On Fedora 32 with Plasma 5.18.5, and I just get "Install script failed".

[Zren]

@rocketraman What specifically says "Install script failed"? At you referring to the status bar of the "Get New Widgets" popup? I do remember a KDE bug that caused an issue with the "Get New Widgets" dialog in older versions of Plasma.

You can download the .plasmoid from the KDE Store directly then run:

• Upgrade: kpackagetool5 -t Plasma/Applet -u ~/Downloads/eventcalendar-v71.plasmoid
• Install for the first time: kpackagetool5 -t Plasma/Applet -i ~/Downloads/eventcalendar-v71.plasmoid

Or install from GitHub: https://github.com/Zren/plasma-applet-eventcalendar#b-install-via-github

The sh ./install script just detects if it's already installed and uses -u or -i appropriately.

[rocketraman]

Yes, it was the Get New Widgets dialog. Updating the .plasmoid using the download from the KDE store as per your instructions worked. Thanks!

[sirish-bajpai]

I downloaded v76 from KDE store and installed. But Google calender oauth link is still not working. I am getting Error 400: invalid_request. The auth link is:
https://accounts.google.com/o/oauth2/v2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Ftasks&response_type=code&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&client_id=391436299960-k0s16nm589meovhoblpcquqgbbrena17.apps.googleusercontent.com

[small-hamster]

I downloaded v76 from KDE store and installed. But Google calender oauth link is still not working. I am getting Error 400: invalid_request. The auth link is: https://accounts.google.com/o/oauth2/v2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Ftasks&response_type=code&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&client_id=391436299960-k0s16nm589meovhoblpcquqgbbrena17.apps.googleusercontent.com

Confirm issue, same version. My link: https://accounts.google.com/o/oauth2/v2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Ftasks&response_type=code&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&client_id=391436299960-k0s16nm589meovhoblpcquqgbbrena17.apps.googleusercontent.com

[chippyash]

Same problem: Additional info from Google:

Error 400: invalid_request
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob

https://developers.google.com/identity/protocols/oauth2/resources/oob-migration

[CamperSamu]

+1 on the issue

[jideogunmekan]

+1 on this

[VitoFe]

+1 on this, getting the out-of-band error message
https://developers.google.com/identity/protocols/oauth2/resources/oob-migration

[Super-T02]

+1 for me it doesn't work also. I get the out-of-band error message. :-/

[0verwritten]

+1, @Zren could you fix it please🥲

[lollilol]

yup, not working for me

[arthuresc]

@lollilol i'm having the same problem... i quite bored haha

[gleyconJ]

I'm also having this same problem, please help us! Your plasmoid is very good!

[NeoPrint3D]

any updates?

[IoSonoAndreaZ]

the project is dead?