Is this urgent?
No
What parts are affected
Android client / shopping list synchronization
What are the Server/Client versions of KitchenOwl
- Android client APK: package
com.tombursch.kitchenowl, versionCode 122 (semantic version unknown)
- Android OS: Android 16 (API 36)
- Test devices: two Android Emulator instances
- Server version: unknown
What's the problem?
Updates to a shared shopping list are synchronized asymmetrically between two members of the same household.
Changes made by the household/list creator (User A) are visible on the other member's device (User B). However, changes made by User B are not reflected on User A's device, so the two users can see different states for the same shopping list.
Steps to reproduce
- On Android device A, sign in as User A.
- Create a household and a shopping list.
- Invite User B to the household and accept the invitation on Android device B.
- Open the same shopping list on both devices.
- Add at least two items, for example
Milk and Bread.
- On device A, check or uncheck an item.
- Observe that the change is synchronized to device B.
- On device B, check or uncheck an item in the same list.
- Return to or keep observing the list on device A.
Expected behavior
Changes made by any household member should be synchronized to every device viewing the shared shopping list. Both devices should show the same item states.
Actual behavior
Changes from User A are synchronized to User B, but changes from User B are not synchronized back to User A. The shared list therefore becomes inconsistent between household members.
Impact
This can cause household members to buy duplicate items or miss needed items because they are working from different list states.
Additional information
The issue was observed while both Android clients were connected and using the same household. Screenshots from the reproduction are available if needed.
Is this urgent?
No
What parts are affected
Android client / shopping list synchronization
What are the Server/Client versions of KitchenOwl
com.tombursch.kitchenowl, versionCode 122 (semantic version unknown)What's the problem?
Updates to a shared shopping list are synchronized asymmetrically between two members of the same household.
Changes made by the household/list creator (User A) are visible on the other member's device (User B). However, changes made by User B are not reflected on User A's device, so the two users can see different states for the same shopping list.
Steps to reproduce
MilkandBread.Expected behavior
Changes made by any household member should be synchronized to every device viewing the shared shopping list. Both devices should show the same item states.
Actual behavior
Changes from User A are synchronized to User B, but changes from User B are not synchronized back to User A. The shared list therefore becomes inconsistent between household members.
Impact
This can cause household members to buy duplicate items or miss needed items because they are working from different list states.
Additional information
The issue was observed while both Android clients were connected and using the same household. Screenshots from the reproduction are available if needed.