Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A single Account constantly loses its Account NUmber / IBAN #8858

Closed
4 tasks done
ypsilonkah opened this issue May 4, 2024 · 5 comments
Closed
4 tasks done

A single Account constantly loses its Account NUmber / IBAN #8858

ypsilonkah opened this issue May 4, 2024 · 5 comments

Comments

@ypsilonkah
Copy link

Support guidelines

I've found a bug and checked that ...

Description

I have four accounts set up in Firefly. All are filled in with IBAN and BIC with different roles:

  1. Default asset account
  2. Savings account
  3. Shared asset account
  4. Savings account

Account No. 3 however keeps "forgetting" its IBAN every now and then (sometimes within a day). I reenter the IBAN and save the changes. Some time later, it's gone again.
How can I provide logs or debug output? Thanks!

Debug information

Debug information generated at 2024-05-04 16:19:52 for Firefly III version v6.1.15.

System information
ItemValue
Firefly III6.1.15 / v2.0.14 / 24 (exp. 24)
PHP version8.3.6 (64bits) / apache2handler / Linux x86_64
BCscale12
Error reportingDisplay: Off, reporting: ALL errors
Max upload67108864 (64 MB)
Database drivers*mysql*, pgsql, sqlite,
Docker build#1074, base #83
Firefly III information
ItemValue
TimezoneEurope/Berlin + Europe/Berlin
App environmentlocal, debug: false
Layoutv1
Loggingnotice, stack / (empty)
Cache driverfile
Default language and localede_DE + equal
Trusted proxies**
Login provider & user guardeloquent / web
Login headersN/A + N/A
Stateful domains
Last cron job2024-05-03 22:00:00 (16 hours ago)
Mailersmtp
User-specific information
ItemValue
User#1 of 1
User flags🔧 📑 📧
Session start2024-05-01 00:00:00
Session end2024-05-31 23:59:59
View range1M
User languageen_US
User localeen_US
Locale(s) supporteden_US.utf8: ✅
en_US.UTF-8: ✅
User agentMozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0

Expected behaviour

Once set up, the account should keep the assigned IBAN and not remove it.

Steps to reproduce

  1. Create account (shared savings, if it matters)
  2. Enter IBAN
  3. Wait
  4. IBAN is gone

Additional info

No response

@JC5
Copy link
Member

JC5 commented May 4, 2024

Thanks for opening an issue!

I've never heard about something like this. This is impossible to debug unless you know what happens when you "wait".

Can you replicate this in a consistent way?

@ypsilonkah
Copy link
Author

ypsilonkah commented May 14, 2024

It just happened again. While I can't yet figure out what triggers the loss of the account's IBAN, It found out that the IBAN is currently in use somewhere in firefly. When I reenter the IBAN, I used to note it with spaces (i.e. DE01 2345 6789 ...). This way I can update the assett account. However, when I try to enter the IBAN without spaces, firefly complains that the IBAN is already in use.

When searching for that IBAN, I find some transactions associated with the assett account.

edit://
When checking expense accounts, I found an account without any transactions for the IBAN in question. It must have been created from an import at a time I had not created the account in Firefly.

@JC5
Copy link
Member

JC5 commented May 15, 2024

Ah, now we're getting closer. The spaces / no spaces thing may be a hint, I'll check it out for sure.

@JC5
Copy link
Member

JC5 commented May 18, 2024

Alright, so the next release of Firefly III will be way more strict with spaces. You may still lose IBANs when you update Firefly III, because it will filter out any duplicates it may find, spaces or not. Your logs will reflect this.

Either way, it should not be an issue going forward, but I would appreciate your feedback.

@JC5 JC5 closed this as completed May 19, 2024
Copy link
Contributor

Hi there! This is an automatic reply. Share and enjoy

This issue is now 🔒 closed. Please be aware that closed issues are not monitored by the developer of Firefly III.

  • If the original bug is not actually fixed, please open a new issue. Refer to this issue for clarity.
  • Follow-up questions must be posted in a new discussion
  • Further replies to this issue may get no response.

If there is more to discuss, please open a new issue or discussion.

Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants