Fix MD5 hash check fallback for devices without toybox #1146
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.


During initialization, uiautomator2 unnecessarily re-pushes
u2.jarto devices even when the file already exists with the correct hash. This occurs on devices lacking thetoyboxutility, causing MD5 verification to fail.Changes
Core Logic (
uiautomator2/core.py)toybox md5sumtomd5command when toybox is unavailableTests (
tests/test_core.py)Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.