Search Criteria
Package Details: todoist-nativefier 2024.02.17-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/todoist-nativefier.git (read-only, click to copy) |
---|---|
Package Base: | todoist-nativefier |
Description: | Todoist in shared Electron runtime |
Upstream URL: | https://todoist.com |
Licenses: | MIT |
Submitter: | alecmev |
Maintainer: | alecmev |
Last Packager: | alecmev |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2020-04-05 15:24 (UTC) |
Last Updated: | 2024-02-17 09:15 (UTC) |
Dependencies (3)
- electron28 (electron28-binAUR)
- gendesk (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
Latest Comments
alecmev commented on 2023-07-03 22:14 (UTC)
Nativefier is lagging behind Electron, unfortunately. Electron 19 is the last tested version, and Electron 21 is the last bug-free one. In 22+ there’s a problem with external links. Both 19 and 21 are EOL, so I’m choosing to stick to 19, for the least amount of surprises.
To avoid the problems with dynamic libraries I recommend installing electron19-bin.
corbin-zip commented on 2023-07-03 18:46 (UTC)
i'm not the most knowledgeable about this stuff but this is the problem i experienced and what i've observed.
this (
todoist-nativefier
) package still relies onelectron19
.electron19
relies on libicu version 72, but version 73.2-1 seems to be all that's available in the repos, so launchingtodoist-nativefier
fails with the error/usr/lib/electron19/electron: error while loading shared libraries: libicui18n.so.72: cannot open shared object file: No such file or directory
i have
electron25
installed, so i simply usedwhereis
to findtodoist-nativefier
(says it is located at/usr/bin/todoist-nativefier
), and then modified that bash script to readexec electron25 /usr/share/todoist-nativefier "$@"
(rather thanelectron19
)hope this helps someone!
slashformotion commented on 2022-02-17 14:26 (UTC)
It seems that google does not like the user agent you are using. It does not allow authentication with a google account
this comment seems to have a workaround
Technetium1 commented on 2022-01-17 03:25 (UTC)
switching the user agent to this allows logging in via Google as per this issue: https://github.com/nativefier/nativefier/issues/831