This repository has been archived by the owner on Sep 27, 2024. It is now read-only.
[Android] Remove workaround for excessive calls to AndroidView
update
#866
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The
update
block of the composableAndroidView
is run on every key press, whereas it should only run when a variable used inside the block is changed.See #856 for more details.
Solution
There is currently a workaround in place for this bug but after some investigation using the Compose inspection tools available in AS Hedgehog, I found that the recomposition is triggered by the value of
onError
being detected as changed despite it being a static function reference.I don't know why this causes the recomposition but replacing the function reference with a lambda function fixes the problem.
update
block is run on every key press #856