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

[Bug]: [MOBILE] "Hold for next month" does nothing because default sign is wrong #4014

Open
1 task done
krolik92 opened this issue Dec 19, 2024 · 1 comment
Open
1 task done
Labels
bug Something isn't working

Comments

@krolik92
Copy link

krolik92 commented Dec 19, 2024

Screenshot_20241219-150859_Native Alpha

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

On mobile version "Hold for next month" option does nothing. When switch to desktop view everything works as expected.

Client version: v24.12.0
Server version: v24.12.0

Tested on Android apps:
Fennec F-droid 133.0.3 (Firefox Mobile fork)
Native Alpha 1.4.0 (app for use website as app)

Server installed on Proxmox as a container from tteck script.

How can we reproduce the issue?

When amount is chosen and click Hold button, it returns, and we can again choose options Move to a category/ Hold for next month but nothing changes, amount isn't set for next month budget.

To make the hold work the sign needs changed to positive. Positive should be the default sign on this option.

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Firefox

Operating System

Mobile Device

@krolik92 krolik92 added the bug Something isn't working label Dec 19, 2024
@youngcw
Copy link
Member

youngcw commented Dec 19, 2024

You need to flip the sign to positive. The real bug here is that the sign defaults to negative which is not what the hold value needs.

Im going to tweak this issue to call out the sign issue.

@youngcw youngcw changed the title [Bug]: [MOBILE] "Hold for next month" does nothing [Bug]: [MOBILE] "Hold for next month" does nothing because default sign is wrong Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants