Support for lightning version
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reproducing camera startup in InfiRay Viewer with the Lightning P2 Pro, Pergear cable, MacBook Pro 2019, and macOS Sequoia 15.5, then trace the reported CMIO errors. Done means the Lightning camera stream starts without the reported factory, device, and property errors; the payload names no repository files or tests.
Written by the indexing model from the issue text.
Description
Hello!
Thank you for this software! Can you help me with my problem?
AddInstanceForFactory: No factory registered for id <CFUUID 0x600003bd9620> F8BB1C28-BAE8-11D6-9C31-00039315CD46
AddInstanceForFactory: No factory registered for id <CFUUID 0x600003bd3880> 30010C1C-93BF-11D8-8B5B-000A95AF9C6A
CMIO_DAL_CMIOExtension_Device.mm:355:Device legacy uuid isn't present, using new style uuid instead
CMIO_DAL_CMIOExtension_Device.mm:355:Device legacy uuid isn't present, using new style uuid instead
CMIO_DAL_CMIOExtension_Stream.mm:1863:GetPropertyData background replacement pixel buffer size invalid or not available
CMIOHardware.cpp:331:CMIOObjectGetPropertyData Error: 2003332927, failed
This errors after starting camera in InfiRay Viewer.
I'm trying to use the Lightning version of P2Pro, connected to a MacBook Pro 2019 (macOS Sequoia 15.5) with a Pergear Lightning to USB-C cable (this setup works fine, tested with an iPhone 16).
- Dominant language
- Swift
- Stars
- 25
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
[Request]: Improve robustness and path resolution in ensure-hawkeye.shPossibly taken @denizguney claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
steipete/CodexBar#4230 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
design
Difficulty 2/5 1-3 hours Newbie friendliness 84/100