No data is sent back to the previous fragment from DisplayTrueExpirationFragment
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
Summary
When in DisplayTrueExpirationFragment
if the user presses the back button, no information is sent back to the previous fragment. This results in no UPC being displayed in the previous fragments and causes issues with the fragment not having a reference to the food item.
Steps to reproduce
- Go to the 'Check Expiration Date' feature within the app.
- Scan or enter a barcode (not water).
- Fill in the required information (not water) if in
SelectItemFragment
, or press confirm if inConfirmItemFragment
. - Select a random date in this order (month->day->year), and press 'Accept'
- Now press the back button.
What is the current bug behavior?
You should see that no data was sent back to the current fragment and that it is not displaying a UPC.
What is the expected correct behavior?
When the user presses the back button it should send the item that was selected and the printed expiration date that was selected back to the previous fragment, which should result in the previous fragment correctly displaying the UPC.
Relevant logs and/or screenshots
This is a screenshot after pressing the back button. Notice how there is no UPC displayed or expiration date set:
Possible fixes
Set a onKeyListener in DisplayTrueExpirationFragment
that sends back the required data to the previous fragment in a result when the back button is pressed.
Labels
NEST
component:check-expiration-date
type::bug
status::doing
Weight Explanation
I'm giving this a weight of 1 since it should be a straight forward and easy fix, and is not critical since this backward-navigation behavior may be removed sometime in the future.