upgrade com.google.mlkit:barcode-scanning version #698
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scarlac
approved these changes
Feb 11, 2025
Collaborator
|
Appreciate the contribution @aravind3566 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Motivation:
This pull request upgrades the ML Kit barcode scanning dependency from its current version to 17.3.0.
The upgrade provides performance improvements, enhanced QR code detection accuracy, and introduces new features like auto-zoom support through ZoomSuggestionOptions.
Problem Solved:
The current version lacks optimized QR code scanning capabilities, especially when dealing with small, blurry, or distant QR codes. The new version improves detection speed and accuracy.
How did you test this change?
Platform Testing:
✅ Tested on Android with various QR code sizes and distances to confirm improved scanning speed and accuracy.
✅ Verified functionality remains stable with no crashes or regressions.