Migrate QR Scanner Away from Legacy Expo Camera API

[Lakes41]

Difficulty: Advanced

Type: Refactor

Summary

Update the QR scanner implementation to use the current Expo Camera API and remove the unresolved legacy import workaround.

Current Behaviour

app/access-scanner.tsx imports Camera, CameraType, and BarCodeScanningResult from expo-camera/legacy and includes an ESLint suppression for unresolved imports. This makes the scanner more fragile during Expo upgrades and hides a module resolution issue from linting.

Expected Behaviour

The scanner should use the supported Expo Camera API for the current Expo SDK version, without disabling lint rules for the import. QR scanning behaviour, permission handling, and navigation back to the access check screen should continue to work.

Suggested Implementation

Replace the legacy camera import with the current Expo Camera component and barcode scanning event types. Update scanner props to match the new API, keep QR-only scanning, and preserve the existing permission states. Add tests or documented manual verification for allowed, denied, and invalid QR payload scenarios.

Files or Areas Likely Affected

• app/access-scanner.tsx
• package.json
• app.json
• tests/
• .maestro/

Acceptance Criteria

• expo-camera/legacy is no longer imported.
• The ESLint suppression for the camera import is removed.
• QR scanning still accepts valid GuildPass access payloads.
• Invalid QR payloads still show a clear error and allow scanning again.
• Camera permission denied and permanently denied states remain usable.

Additional Notes

Keep the migration scoped to the scanner implementation. Do not redesign the QR payload format in this issue.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 10 hours

[GBOYEE]

Hey! I can work on this. I will update the QR scanner to use the current Expo Camera API, replace the legacy imports, and remove the ESLint suppression. Clean PR incoming shortly.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[Phantomcall]

Hello maintainers,

I'd like to work on this issue.

I have experience with React Native, Expo, TypeScript, and camera/barcode scanning APIs, and I'm comfortable migrating applications between Expo SDK versions while maintaining backward-compatible behavior.

My implementation plan
Replace the legacy expo-camera/legacy import with the current supported expo-camera API.
Remove the ESLint suppression for the unresolved camera import.
Update app/access-scanner.tsx to use the current camera component and barcode scanning event types.
Preserve:
QR-only scanning
Existing permission flow
Navigation back to the access check screen
Existing valid access payload behavior
Ensure invalid QR payloads continue to display a clear error and allow users to scan again.
Verify camera permission denied and permanently denied states continue to behave correctly.
Update dependencies/configuration if required for the current Expo SDK.
Add tests where practical or provide documented manual verification covering:
Valid GuildPass QR
Invalid QR payload
Permission denied
Permanently denied permission
Validation

Before opening the PR I'll run:

npm run lint
npm run typecheck
npm test

I'll also perform manual testing on an Expo development build to verify camera permissions and QR scanning behavior.

The implementation will stay scoped to the camera API migration only and will not modify the existing QR payload format or application flow.

Looking forward to contributing!

[grantfox-oss]

🦊 GrantFox — @Phantomcall has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #48)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Phantomcall's PR #58 was approved and merged by @Lakes41.

🏆 @Phantomcall: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (891 total points). Track your full progress on GrantFox.

👏 Great work, @Phantomcall! Keep contributing to Adamantine-guild.