mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #229] Unable to sync on Chrome with extension: EDIT: Possible scam extension? #220
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#220
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jcklpe on GitHub (Feb 13, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/229
Software versions
Steps to reproduce
Expected outcome
I expected it to work. I've already got it working on two different machines with firefox but it's not working on chrome for some reason.
Actual outcome
error
...
Debug log
There does not appear to be a debug log in the chrome extension.
Also this does not seem to be just my problem.
EDIT:
Ooooh whoops. Looks like I wasn't using the official app. This app doesn't work, and I don't know who made it. Maybe it's a scam? Guess I should have known better to double check this info before installing it: https://chrome.google.com/webstore/detail/floccus-nextcloud-sync/behlkinclcpoiijckdfjmibdpnfocefg/related?hl=en
@marcelklehr commented on GitHub (Feb 13, 2019):
Ah yes. It's not a scam. Initial versions of floccus were not available in the webstore so someone put them up there, but since then the person has neglected the undertaking.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.