github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[Bug]: Sync Problem #2351

New Issue
Closed
opened 2026-02-28 20:11:35 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 20:11:35 -06:00
Owner
Copy Link

Originally created by @rlust on GitHub (Aug 4, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

We had a problem syncing! Open a Github issue!
Migrations: DONE
Running in production mode - Serving static React app
Listening on :::5006...
2025-08-04T13:05:19.160Z info: GET 304 /account/validate
2025-08-04T13:05:21.808Z info: GET 304 /account/validate
2025-08-04T13:05:21.812Z info: GET 200 /account/needs-bootstrap
2025-08-04T13:05:21.840Z info: GET 200 /sync/list-user-files
2025-08-04T13:05:23.233Z info: GET 304 /account/validate
2025-08-04T13:05:23.240Z info: GET 304 /sync/list-user-files
2025-08-04T13:05:23.358Z info: POST 200 /sync/sync
2025-08-04T13:05:25.015Z info: POST 200 /sync/sync
2025-08-04T13:06:45.491Z info: GET 304 /account/validate
2025-08-04T13:06:45.494Z info: GET 304 /account/validate
2025-08-04T13:06:54.796Z info: GET 304 /account/validate
2025-08-04T13:06:58.279Z info: GET 304 /account/validate
2025-08-04T13:29:31.741Z info: GET 304 /account/needs-bootstrap
2025-08-04T13:29:31.744Z info: GET 304 /account/validate
2025-08-04T13:29:31.775Z info: GET 304 /sync/list-user-files
2025-08-04T13:29:32.891Z info: GET 304 /account/validate
2025-08-04T13:29:32.897Z info: GET 304 /sync/list-user-files
2025-08-04T13:29:32.949Z info: POST 200 /sync/sync
2025-08-04T13:29:34.488Z info: POST 200 /sync/sync
2025-08-04T13:31:02.144Z info: GET 304 /account/validate
2025-08-04T13:31:02.147Z info: GET 304 /account/validate
2025-08-04T13:34:59.159Z info: GET 304 /account/validate
2025-08-04T13:43:02.822Z info: GET 304 /account/validate
2025-08-04T13:43:09.318Z info: GET 304 /account/validate
2025-08-04T13:43:42.466Z info: GET 304 /account/validate
2025-08-04T13:45:24.679Z info: GET 304 /account/validate

How can we reproduce the issue?

Every time I open Actual I get sync error.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Safari

Operating System

None

Originally created by @rlust on GitHub (Aug 4, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? We had a problem syncing! Open a Github issue! Migrations: DONE Running in production mode - Serving static React app Listening on :::5006... 2025-08-04T13:05:19.160Z info: GET 304 /account/validate 2025-08-04T13:05:21.808Z info: GET 304 /account/validate 2025-08-04T13:05:21.812Z info: GET 200 /account/needs-bootstrap 2025-08-04T13:05:21.840Z info: GET 200 /sync/list-user-files 2025-08-04T13:05:23.233Z info: GET 304 /account/validate 2025-08-04T13:05:23.240Z info: GET 304 /sync/list-user-files 2025-08-04T13:05:23.358Z info: POST 200 /sync/sync 2025-08-04T13:05:25.015Z info: POST 200 /sync/sync 2025-08-04T13:06:45.491Z info: GET 304 /account/validate 2025-08-04T13:06:45.494Z info: GET 304 /account/validate 2025-08-04T13:06:54.796Z info: GET 304 /account/validate 2025-08-04T13:06:58.279Z info: GET 304 /account/validate 2025-08-04T13:29:31.741Z info: GET 304 /account/needs-bootstrap 2025-08-04T13:29:31.744Z info: GET 304 /account/validate 2025-08-04T13:29:31.775Z info: GET 304 /sync/list-user-files 2025-08-04T13:29:32.891Z info: GET 304 /account/validate 2025-08-04T13:29:32.897Z info: GET 304 /sync/list-user-files 2025-08-04T13:29:32.949Z info: POST 200 /sync/sync 2025-08-04T13:29:34.488Z info: POST 200 /sync/sync 2025-08-04T13:31:02.144Z info: GET 304 /account/validate 2025-08-04T13:31:02.147Z info: GET 304 /account/validate 2025-08-04T13:34:59.159Z info: GET 304 /account/validate 2025-08-04T13:43:02.822Z info: GET 304 /account/validate 2025-08-04T13:43:09.318Z info: GET 304 /account/validate 2025-08-04T13:43:42.466Z info: GET 304 /account/validate 2025-08-04T13:45:24.679Z info: GET 304 /account/validate ### How can we reproduce the issue? Every time I open Actual I get sync error. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Safari ### Operating System None
GiteaMirror added the bugneeds info labels 2026-02-28 20:11:35 -06:00
GiteaMirror commented 2026-02-28 20:11:36 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Aug 4, 2025):

What does the browser console say?

@youngcw commented on GitHub (Aug 4, 2025): What does the browser console say?
GiteaMirror commented 2026-02-28 20:11:36 -06:00
Author
Owner
Copy Link

@kennylarsen commented on GitHub (Aug 30, 2025):

I seem to have the same error, console says:

Syncing since 2025-08-30T14:41:08.869Z-0002-8555242bf105b919 510 (attempt: 0)
index.ts:563 PostError: PostError: internal
at throwIfNot200 (post.ts:10:13)
at postBinary (post.ts:211:3)
at async _fullSync (index.ts:662:21)
at async index.ts:561:16
at async app_sync (app.ts:20:10)
index.ts:593 PostError: PostError: internal
at throwIfNot200 (post.ts:10:13)
at postBinary (post.ts:211:3)
at async _fullSync (index.ts:662:21)
at async index.ts:561:16
at async app_sync (app.ts:20:10)
sync-events.ts:357 unknown error {type: 'error', subtype: 'internal'}
(anonymous) @ sync-events.ts:357
Q4e @ index.browser.ts:70
J4e.e.onmessage @ index.browser.ts:137
746a22c52-eb59-453b-9cda-697ffc99ea9c:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received

@kennylarsen commented on GitHub (Aug 30, 2025): I seem to have the same error, console says: Syncing since 2025-08-30T14:41:08.869Z-0002-8555242bf105b919 510 (attempt: 0) index.ts:563 PostError: PostError: internal at throwIfNot200 (post.ts:10:13) at postBinary (post.ts:211:3) at async _fullSync (index.ts:662:21) at async index.ts:561:16 at async app_sync (app.ts:20:10) index.ts:593 PostError: PostError: internal at throwIfNot200 (post.ts:10:13) at postBinary (post.ts:211:3) at async _fullSync (index.ts:662:21) at async index.ts:561:16 at async app_sync (app.ts:20:10) sync-events.ts:357 unknown error {type: 'error', subtype: 'internal'} (anonymous) @ sync-events.ts:357 Q4e @ index.browser.ts:70 J4e.e.onmessage @ index.browser.ts:137 746a22c52-eb59-453b-9cda-697ffc99ea9c:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
GiteaMirror commented 2026-02-28 20:11:36 -06:00
Author
Owner
Copy Link

@kennylarsen commented on GitHub (Aug 30, 2025):

To add to this, I just re-updated and the error seems to have resolved itself.

@kennylarsen commented on GitHub (Aug 30, 2025): To add to this, I just re-updated and the error seems to have resolved itself.
GiteaMirror commented 2026-02-28 20:11:36 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Aug 30, 2025):

Lacking info on original post. Closing

@youngcw commented on GitHub (Aug 30, 2025): Lacking info on original post. Closing
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug needs info
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2351
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?