Package Details: google-calendar-nativefier 2024.02.17-3

Git Clone URL: https://aur.archlinux.org/google-calendar-nativefier.git (read-only, click to copy)
Package Base: google-calendar-nativefier
Description: Google Calendar in shared Electron runtime
Upstream URL: https://calendar.google.com
Licenses: MIT
Submitter: akaessens
Maintainer: alecmev
Last Packager: alecmev
Votes: 4
Popularity: 0.000000
First Submitted: 2019-05-21 15:06 (UTC)
Last Updated: 2024-02-19 10:34 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

alecmev commented on 2024-02-19 10:36 (UTC)

@SoBC Thanks for reporting, I just pushed an update that skips the checksum, not worth it for a PNG.

SoBC commented on 2024-02-19 08:58 (UTC)

The checksum of the icon mismatches:

diff --git a/PKGBUILD b/PKGBUILD
index b807bbd..0cc8f23 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,7 +16,7 @@ makedepends=(
   'yarn'
 )
 source=("${pkgname}.png::https://upload.wikimedia.org/wikipedia/commons/thumb/a/a5/Google_Calendar_icon_%282020%29.svg/512px-Google_Calendar_icon_%282020%29.svg.png")
-sha256sums=('9540319d363d87d6278218325136164ab5639d94bad152f988811697da630755')
+sha256sums=('7f82a67540628f9811f188a1fe174bc6dbb6bcefee1f5121ce51c7d450d5c5b7')

 _name='Google Calendar'

Atherth commented on 2023-08-13 00:46 (UTC)

Electron dependency dont match with pkgbuild

alecmev commented on 2021-04-01 17:35 (UTC)

Sorry for the delay, life got busy for a few weeks.

Glad you found a fix, @akaessens! I actually removed the custom User-Agent when I was doing the overhaul, since my testing didn't reveal any problems, sorry about that... Classic Chesterton's fence. It's odd that I couldn't reproduce this, perhaps my account has "less secure app access" enabled (can't find it in my settings), or it has something to do with both of my accounts being on Google Workspace. Will test with my old personal account from now on.

Nativefier has a relevant issue. It's a shame nobody has gone through the trouble of figuring out how Google knows that the default User-Agent is fake yet.

akaessens commented on 2021-03-12 20:51 (UTC) (edited on 2021-03-12 21:07 (UTC) by akaessens)

@alecmev any idea what is causing the login not working? I reproduce it, too with electron v11.3.0. EDIT: The issue is the user agent of electron. It needs to be set explicitly to something else or google forbids the login. This was an issue in previous releases but i forgot that this happened. Fixed now.

connorhodes commented on 2021-02-26 23:20 (UTC) (edited on 2021-02-26 23:28 (UTC) by connorhodes)

@alecmev. I have an up-to-date system with Electron 11.3.0-1 installed. I tried the app in a fresh Arch VM that never had any software installed, and it had the same issue. I ran both versions from the terminal, and the non-dark version throws this error:

WARNING: Ignored nativefier.json rewrital (Error: EACCES: permission denied, open '/usr/share/google-calendar-nativefier/nativefier.json')

I have screenshots of all of this here.

I tried a quick change of permissions and ownership to see if that affected the error, and it didn't. I don't think this permission error is related to my login issue.

I also tried with a different Google account. No change.

alecmev commented on 2021-02-26 21:50 (UTC)

@connorhodes Thanks for reporting. I've nuked my app data directory (so it's like a fresh install) and went through the login procedure, without issues, including 2FA. Not sure where to even begin, to be honest... Is your system up-to-date, specifically Electron? Can you make a screenshot of the error, please?

connorhodes commented on 2021-02-26 21:45 (UTC)

I can't login with this package. I get a "This browser or app may not be secure" message. Strangely, I don't get this message with the "google-calendar-nativefier-dark" package. That one works without issues.

akaessens commented on 2021-02-22 12:43 (UTC)

Yes please! I haven't thought about this before but I like that. Resource usage is one of the main problems of electron-based applications.

alecmev commented on 2021-02-21 16:31 (UTC)

Is there any advantage over official todist-appimage and todoist-electron which was officially recommended before?

The main advantage is the shared runtime, which hopefully saves some RAM and CPU cycles, at the expense of a slightly higher chance of breaking between major releases of Electron (unlikely, since, AFAIK, Electron never introduces breaking changes without putting them behind a flag first and asking everybody to adjust their code). Todoist's official app doesn't appear to do anything special, so there's no sacrifice.

Speaking of, do you mind if I switch this package to the same style of PKGBUILD as todoist-nativefier, i.e. use shared Electron?