github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-11 11:59:55 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #2423] [Bug]: #7902

New Issue
Closed
opened 2026-04-10 18:01:53 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-10 18:01:53 -05:00
Owner
Copy Link

Originally created by @tempusthales on GitHub (Mar 4, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2423

Verified issue does not already exist?

  • I have searched and found no existing issue

Is this related to GoCardless, Simplefin or another bank-sync provider?

  • I have checked my server logs and could not see any errors there
  • I will be attaching my server logs to this issue
  • I will be attaching my client-side (browser) logs to this issue
  • I understand that this issue will be automatically closed if insufficient information is provided

What happened?

I got a red advisory that there were problems with syncing, and I should open a bug report.

What error did you receive?

A red notification on the bottom right of the browser indicating: We had problems syncing your changes. Please report this as a bug by opening a Github issue.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Chrome

Operating System

Linux

Originally created by @tempusthales on GitHub (Mar 4, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2423 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### Is this related to GoCardless, Simplefin or another bank-sync provider? - [X] I have checked my server logs and could not see any errors there - [X] I will be attaching my server logs to this issue - [X] I will be attaching my client-side (browser) logs to this issue - [X] I understand that this issue will be automatically closed if insufficient information is provided ### What happened? I got a red advisory that there were problems with syncing, and I should open a bug report. ### What error did you receive? A red notification on the bottom right of the browser indicating: We had problems syncing your changes. Please report this as a bug by [opening a Github issue](https://github.com/actualbudget/actual/issues/new?assignees=&labels=bug&template=bug-report.yml&title=%5BBug%5D%3A+). ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox, Chrome ### Operating System Linux
GiteaMirror added the bug label 2026-04-10 18:01:53 -05:00
GiteaMirror commented 2026-04-10 18:01:54 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 4, 2024):

Any more info than this? Like the error details or what sync you use?

<!-- gh-comment-id:1977596296 --> @youngcw commented on GitHub (Mar 4, 2024): Any more info than this? Like the error details or what sync you use?
GiteaMirror commented 2026-04-10 18:01:55 -05:00
Author
Owner
Copy Link

@tempusthales commented on GitHub (Mar 4, 2024):

Honestly I started using Actual yesterday, and this showed up on the
browser when I went into it this morning. I reloaded the page and it
showed up one more time. I closed the browser and then reloaded the page,
and it then went away.

The only reason I opened a bug report was because the notification insisted
this was a bug. If you want to close the report for now and if it repeats
I will find more information on it that I can provide you with.

On Mon, Mar 4, 2024 at 4:42 PM youngcw @.***> wrote:

Any more info than this? Like the error details or what sync you use?

—
Reply to this email directly, view it on GitHub
https://github.com/actualbudget/actual/issues/2423#issuecomment-1977596296,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASVPR3W246DDIOBYJDE5EDYWT2FDAVCNFSM6AAAAABEGAE3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGU4TMMRZGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Gilbert J. Palau
@.***
http://gilbertpalau.com

<!-- gh-comment-id:1977691579 --> @tempusthales commented on GitHub (Mar 4, 2024): Honestly I started using Actual yesterday, and this showed up on the browser when I went into it this morning. I reloaded the page and it showed up one more time. I closed the browser and then reloaded the page, and it then went away. The only reason I opened a bug report was because the notification insisted this was a bug. If you want to close the report for now and if it repeats I will find more information on it that I can provide you with. On Mon, Mar 4, 2024 at 4:42 PM youngcw ***@***.***> wrote: > Any more info than this? Like the error details or what sync you use? > > — > Reply to this email directly, view it on GitHub > <https://github.com/actualbudget/actual/issues/2423#issuecomment-1977596296>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AASVPR3W246DDIOBYJDE5EDYWT2FDAVCNFSM6AAAAABEGAE3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGU4TMMRZGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Gilbert J. Palau ***@***.*** http://gilbertpalau.com
GiteaMirror commented 2026-04-10 18:01:56 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Mar 5, 2024):

If things have cleared up Ill close this. If it happens again try to get the extended error message from the popup.

<!-- gh-comment-id:1979007403 --> @youngcw commented on GitHub (Mar 5, 2024): If things have cleared up Ill close this. If it happens again try to get the extended error message from the popup.
GiteaMirror commented 2026-04-10 18:01:57 -05:00
Author
Owner
Copy Link

@tempusthales commented on GitHub (Mar 5, 2024):

There was no extended error message, what I sent you is what the
notification set. I will grab other logs next time...

On Tue, Mar 5, 2024 at 9:16 AM youngcw @.***> wrote:

If things have cleared up Ill close this. If it happens again try to get
the extended error message from the popup.

—
Reply to this email directly, view it on GitHub
https://github.com/actualbudget/actual/issues/2423#issuecomment-1979007403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASVPRZT6I6HGTHBBYR2DU3YWXOTRAVCNFSM6AAAAABEGAE3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZZGAYDONBQGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Gilbert J. Palau
@.***
http://gilbertpalau.com

<!-- gh-comment-id:1979338556 --> @tempusthales commented on GitHub (Mar 5, 2024): There was no extended error message, what I sent you is what the notification set. I will grab other logs next time... On Tue, Mar 5, 2024 at 9:16 AM youngcw ***@***.***> wrote: > If things have cleared up Ill close this. If it happens again try to get > the extended error message from the popup. > > — > Reply to this email directly, view it on GitHub > <https://github.com/actualbudget/actual/issues/2423#issuecomment-1979007403>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AASVPRZT6I6HGTHBBYR2DU3YWXOTRAVCNFSM6AAAAABEGAE3NWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZZGAYDONBQGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Gilbert J. Palau ***@***.*** http://gilbertpalau.com
GiteaMirror commented 2026-04-10 18:01:58 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Mar 5, 2024):

I had a similar thing (and message) on a couple of iOS devices a few hours after my update to 2024-03 and also the sync initially not updating all transactions from desktop to mobile.

This eventually resolved itself following a refresh of the page.

<!-- gh-comment-id:1979419740 --> @Kidglove57 commented on GitHub (Mar 5, 2024): I had a similar thing (and message) on a couple of iOS devices a few hours after my update to 2024-03 and also the sync initially not updating all transactions from desktop to mobile. This eventually resolved itself following a refresh of the page.
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
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#7902
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?