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

Revert "[iOS] Clear BindingContext when cell is queued for reuse (#14… #21400

Closed
wants to merge 2 commits into from

Conversation

PureWeen
Copy link
Member

Description of Change

Revert #14619

It looks like this change caused the following "regression" #21374.

From testing I don't think this change directly caused the regression, but I think it exposed a flaw in the prototype code that now only surfaces because of that PR.

The prototype code inside ItemsViewLayout creates a prototype cell to measure with if no cells have been measured yet. This creates a phantom TemplatedCell that gets added to the logical children and causes there to be two TemplatedCells for the same View

I did a quick test just returning the results of the prototype cell without creating it and it no longer crashes. So, I think we need to rework the prototype cells a bit for SR4

image

)"

This reverts commit 170a7a9.

# Conflicts:
#	src/Controls/src/Core/Handlers/Items/iOS/ItemsViewDelegator.cs
#	src/Controls/tests/DeviceTests/Elements/CollectionView/CollectionViewTests.cs
@PureWeen PureWeen requested a review from a team as a code owner March 22, 2024 18:51
@PureWeen
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@PureWeen PureWeen marked this pull request as draft March 23, 2024 14:56
@PureWeen PureWeen closed this Mar 29, 2024
@mooola
Copy link

mooola commented Mar 29, 2024

@PureWeen Is there a reason this was closed and not merged?

@SonicScholar
Copy link

@PureWeen Is there a reason this was closed and not merged?

Agree with this question. We've been hosed on iOS trying to get a release out from this regression and waiting for a fix. The vibe here seemed promising until it was closed unexpectedly.

@PureWeen
Copy link
Member Author

PureWeen commented Mar 30, 2024

It's the same timeline for us to fix forward or revert.
If we're unable to fix forward, we'll revisit.

@SonicScholar if you have an additional repro you could add here #21374 that'd be helpful.

At this point it feels riskier to revert vs fix forward given the data we have. This change has been part of the code now for a good amount of time with no other issues logged and @mooola found workaround so it felt more disruptive to revert.

@PureWeen PureWeen deleted the revert_14619 branch April 2, 2024 15:44
@github-actions github-actions bot locked and limited conversation to collaborators May 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants