Drag & drop drag state resets after an incorrect answer

[BenHenning]

Describe the bug
When using the drag & drop interaction, an incorrect answer results in the same drag state being shown.

To Reproduce
Steps to reproduce the behavior:

1. Start the Prototype Exploration on a dev build of the app
2. Play through it until the first drag & drop state
3. Drag the items to produce an incorrect answer
4. Submit the answer
5. Observe that the drag & drop order resets back to the original state

Expected behavior
The drag & drop order should stay the same after the incorrect answer.

Screenshot

Device

• Device: Pixel XL
• SDK: 29

Additional Information

Comment #1468 (comment) was addressed in #5478.

[BenHenning]

As discussed, since this needs to apply to all interactions we're not blocking M2 on this work item.

[BenHenning]

This probably also happens during configuration changes.

[anandwana001]

@aggarwalpulkit596 still working on this?

[aggarwalpulkit596]

This was something a bit out of scope with the current implementation of interactions and viewmodels. It won't be possible unless we move to hilt or something better.

[BenHenning]

I think we're solving this for the other interactions using a singleton that retrieves state from the assembler. See #2514 for specifics. @FareesHussain do you think that approach could work here?

[BenHenning]

Deassigning you @aggarwalpulkit596 since it seems that you're not actively working on this.

[FareesHussain]

I think we're solving this for the other interactions using a singleton that retrieves state from the assembler. See #2514 for specifics. @FareesHussain do you think that approach could work here?

I'm not sure here, so far my implementation didn't give any desired result. I've completely forgotten my singleton pr. I will try once again using the setState similar to #2557

[aggarwalpulkit596]

@FareesHussain let me know if i can be of any help.

[adhiamboperes]

@TanishMoral11, PTAL.

[Rd4dev]

Just adding for reference (not working and not approved):

I tried to get the previous pendingState.wrongAnswerList to pass for computing the strings - Code sample. However, I haven't yet figured a way to update the adapter with the same:

1. It always instantly fell back to the empty list, providing the default list since LiveData was gathered asynchronously.
2. To obtain and update the adapter into the content view model.

I’m adding this for future reference as I’m currently considering moving on to another issue.