[Bug] CameraView doesn't work well with Linker

[john-technegol]

Description

xct CameraView works when testing with Debug Build (Visual Studio 2019) when 'Release Build' CameraView page won't load. Narrowed it down to Release config having Linker properties set to 'SDK Assemblies Only' when changed to 'None' the Camera works as expected.

It Appears the linker is removing the code required to use CameraView.

Expected Behavior

Page to open with CameraView

Actual Behavior

Page just doesn't open

Basic Information

Xamarin Community Toolkit 1.2.0

• Version with issue:
• Last known good version:
• IDE: Visual Studio 2019
• Platform Target Frameworks:
  • Android: API 30

Workaround

Set Linker Properties to None

[Rardd1997]

Try to add

<linker>
<assembly fullname="Xamarin.CommunityToolkit" />
</linker>

in LinkerSettings.xml file

[AndreiMisiukevich]

@Rardd1997 small typo, should be assembly I think :)

[Rardd1997]

@Rardd1997 small typo, should be assembly I think :)

Yep, updated. Thanks

[john-technegol]

Thanks for the I info. I’m on a different project at the moment but will give it a try when I can. Thanks

…

Sent from my iPhone

On 4 Oct 2021, at 09:16, Dmytriy Obrusnik ***@***.***> wrote:  @Rardd1997 small typo, should be assembly I think :) Yep, updated. Thanks — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[GUOLDEV]

@john-technegol it would be good to know the property that Linker is removing for your case. A simple sample could help as well 👍

[john-technegol]

Hi @GUOLDEV I have since left the company where I was working on this and no longer have access to the code also returned all my laptops etc.
I will try and create a simple project and re-create the issue on an old laptop I have here. Not sure how it will run Visual Studio but I'll give it a go 👍

[john-technegol]

I have created a sample project and all works as expected, Debug & Release.

The main differences are this time I used the shell template and added the view in there (all in one project). When I was having the issue I was using Prism and the Camera View was in a separate Module/Project. The issue was probably to do with my setup/solution rather than an issue with the control.