Closed jonthysell closed 3 years ago
Let's look at this when we have the repro firmed up when the camera change has been merged.
Repo here in the new CameraDemo sample: https://github.com/microsoft/react-native-windows-samples/pull/186
Source: https://github.com/microsoft/react-native-windows-samples/tree/master/samples/CameraDemo
Running into this again as I work on #3278
Confirming today that this doesn't repro with a C# app consuming a C++ module + a C++ nuget.
Confirming today that this no longer repros with CameraDemo against the latest 0.63.
Closing as resolved for 63.
Summary
I'm writing a test app which tests https://github.com/react-native-community/react-native-camera/pull/2930, which adds barcode scanning to react-native-camera.
Barcode scanning is provided by a third-party winrt binary (ZXing.winrt, ZXing.dll) via nuget: https://www.nuget.org/packages/huycn.zxingcpp.winrt
When building and deploying in VS, the appx (release) / deploy from layout (debug) includes the binaries and the functionality works fine.
When using
run-windows --release
, the deployed appx includes the binaries and everything runs fine.When using
run-windows
(aka debug, our custom deploy from layout), the outputted folder does not contain the binaries. So when trying to scan for barcodes, we get a runtime exception:Callstack:
Environment
If you are using latest version:
react-native -v
:react-native run-windows --info
:reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModelUnlock"
Then, specify:
Steps to Reproduce
react-native run-windows
Expected Behavior
The binaries from the nuget package C should have been transitively included in the app layout for the RNW app A, since the app depends on B and B depends on C.
Actual Behavior
run-windows --release
work fine).Reproducible Demo
I can't publish my test app until my PR for barcode scanning gets merged into react-native-camera and released.