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

[camera][ios] Make sure barcode bounds match barcode scanner #27207

Merged
merged 2 commits into from
Feb 22, 2024
Merged

[camera][ios] Make sure barcode bounds match barcode scanner #27207

merged 2 commits into from
Feb 22, 2024

Conversation

tamagokun
Copy link
Contributor

@tamagokun tamagokun commented Feb 21, 2024

Why

Fixes #24540.

Set the preview layer for the barcode scanner so the bounds of the scanned frame are correct

Currently expo-camera gives you different bounds and corners data after scanning a barcode. The bug is outlined in this issue: #24540

Note: this is an update from #24663 which provided this fix for the old expo-camera module.

How

Test Plan

Checklist

set the preview layer for the barcode scanner so the bounds of the scanned frame are correct
@expo-bot expo-bot added the bot: suggestions ExpoBot has some suggestions label Feb 21, 2024
@expo-bot expo-bot added bot: passed checks ExpoBot has nothing to complain about and removed bot: suggestions ExpoBot has some suggestions labels Feb 21, 2024
Copy link
Contributor

@lukmccall lukmccall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ✅
Thanks for your contribution!

@lukmccall lukmccall changed the title expo-camera: Make sure barcode bounds match barcode scanner [camera][ios] Make sure barcode bounds match barcode scanner Feb 22, 2024
@lukmccall lukmccall merged commit b11029d into expo:main Feb 22, 2024
8 of 9 checks passed
aleqsio pushed a commit that referenced this pull request Feb 22, 2024
# Why

Fixes #24540.

Set the preview layer for the barcode scanner so the bounds of the scanned frame are correct

Currently expo-camera gives you different bounds and corners data after scanning a barcode. The bug is outlined in this issue: #24540

> Note: this is an update from #24663 which provided this fix for the old expo-camera module.

# How

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

<!--
Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
@brentvatne brentvatne added the published Changes from the PR have been published to npm label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: passed checks ExpoBot has nothing to complain about published Changes from the PR have been published to npm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Camera vs BarCodeScanner] - Difference in X and Y return values.
4 participants