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

Add/edit transaction on mobile ► site doesn't show transaction until re-saved with desktop program #2

Open
benspaul opened this issue Aug 17, 2014 · 0 comments

Comments

@benspaul
Copy link

Summary: When you add or edit a transaction on a mobile device, you will not see that transaction on YNAB until you open a desktop YNAB and Save there.

Steps to reproduce:

  1. In the YNAB mobile app (tested on iOS 7) create a transaction.

  2. On YNAB web (i.e., this repo), log in and find that transaction

Expected: I see that transaction listed (as occurs in YNAB for desktop)

Actual: I don't see that transaction listed

Note:

  • This problem also occurs if you try to edit an existing transaction from a mobile device (tested on iOS 7)
  • If you open YNAB desktop, you will see the transaction there. If you hit Save from the desktop program, then YNAB web (i.e., this repo) will show the transaction.
  • I think this is caused from two issues:

(1) The program relies on "hasFullKnowledge" to determine which device is most up to date, but that field is not set for mobile devices (https://github.com/elaske/pynab/wiki/1.1.-Device-Files#hasfullknowledge). One can work around this by inspecting version numbers given in the "knowledge" property and finding the device with the highest version numbers.

(2) Even if the code figures out that my iPhone has the most updated information, unfortunately you can't just go to the iPhone's folder and read its budget file. There is no Budget.yfull saved within my iPhone's device directory on Dropbox. Instead, there are only ydiff files. I'm not sure if you would have to merge the new changes from ydiff files into the old Budget.yfull file, or if there is some way around this. This is tricky.

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

1 participant