Missing Wallets in Expense App Guidelines
Some users may experience missing or unsynced expenses in the Bookipi Expense App. This article explains the cause, who is affected, how data is impacted, and how to prevent the issue.
Q: Who is affected?
A: This issue primarily affects users who:
Have an unverified Expense app account, and
Use a third-party login (e.g., Google) in another Bookipi app.
Verified users are not expected to encounter this specific issue.
Q: What causes the issue?
The issue occurs when an unverified user logs in with a third-party account in another Bookipi app (Invoice, Bookipi AI, eSign).
Doing so invalidates the user's active session in the Expense app.
Once the Expense app session becomes invalid:
Previously synced expenses remain safely stored on the server.
New expenses can no longer sync to the server while the session is invalid.
Those new expenses remain only on the device until the session is restored.
Q: Can users use third-party login in the Expense app?
A: Yes. Using a third-party login within the Expense app itself is not the issue.
When a user logs in with a third-party account in the Expense app, they are first logged out of their existing session. At that point, there should be no pending transactions waiting to be sent to the server, so this scenario does not trigger the syncing issue described in this article.
The issue specifically occurs when a third-party login is used in another Bookipi app, which invalidates the active Expense app session.
Q: What happens to expenses that already synced?
A: If expenses successfully synced to the server before the session became invalid, they are safe.
These expenses remain on the server and can be restored even if the user later logs out or reinstalls the app.
Example:
January expenses synced
February expenses synced
User logs in to another Bookipi app using Google.
Expense app session becomes invalid.
January and February expenses remain available.
Q: What happens to expenses that have not synced?
Expenses created after the session becomes invalid cannot sync to the server.
These expenses remain stored only on the device.
If the user logs out before they are synced, those locally stored expenses may be lost.
Example:
Expense app session becomes invalid.
User creates April expenses.
April expenses remain pending because they cannot sync.
User logs out.
April expenses are no longer recoverable.
Q: Can the session become valid again?
Manually signing in may create a valid session again, although this has not been fully verified.
However, users should not log out if they have unsynced expenses, as those expenses may exist only on the device and could be lost.
Q: How can users avoid this issue?
A: To avoid this issue:
Create an Expense app account.
Verify the email address before entering expenses.
Avoid using a third-party login in another Bookipi app while the Expense app account is still unverified.
Summary
Scenario | Result
|
Verified account
| No known syncing issue related to this bug
|
Unverified account, no third-party login in another Bookipi app
| Syncing works normally
|
Unverified account uses third-party login in the Expense app
| Supported; not the cause of this issue
|
Unverified account uses third-party login in another Bookipi app
| Expense app session becomes invalid
|
Expenses already synced before session becomes invalid
| Safe on the server
|
Expenses created after session becomes invalid
| Cannot sync and remain only on the device
|
Logging out while unsynced expenses exist
| May result in loss of those unsynced expenses
|
Note: The guidance in this article is temporary and will apply until the development team implements a permanent fix. For more clarification and guidance please contact us at support@bookipi.com.
Discover more tutorials for Bookipi Expense mobile app
Discover more tips on how to get the most out of Bookipi Expense mobile app with our Bookipi Expense guides.
Need to send invoices with ease? Download the Bookipi Invoice mobile app and check out our Bookipi Invoice mobile app guides.