-
Notifications
You must be signed in to change notification settings - Fork 133
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
Read properties undefined (reading 'scheduled') #249
Comments
After removing a few entries within the editor/database I get my dashboard to load. However, if I attempt to insert any more transactions in the month of June I start to get the errors above. If I start to put transactions in July the program operates as expected. |
Looks like a scheduled Recurring entry was conflicting with a configuration for a credit card under More -> Configuration -> Credit Cards I had
Which had an entry under configurations. My guess was the period of |
After more tinkering it seems the conflict arises when I have the above in my ledger but then I am using that exact Account of
At least if you want something to show up under the Recurring section. If not you don't need this. |
Thanks for the above findings. It did resolve the issue I faced. The common pattern between our cases is about the recurring tag. I had the following that caused the error. = Assets:Debt:Deposits:PO SCSS |
Thanks for debugging, I would like to keep this open. I understand you found some workaround, but app shouldn't crash in any cases. I am a bit tight with no free time nowadays, but keeping this open would help me or someone else to fix this. |
OS: Windows 10 Professional
App Variant: Desktop
Describe the bug
The following error pops up upon opening Paisa and it automatically loading my "Dashboard"
and
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expecting the dashboard to open as it normally does and be able to use Paisa
Screenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: