Jonathan Peppers
Jonathan Peppers
There is likely a build warning in the current binding; that's preventing this from being bound to C# as expected.
If someone could share a sample project showing the issue, that would help a lot. @moljac likely won't be spending much time on this project in the future.
@dimonovdd it looks like you are supposed to override: ```csharp protected virtual bool AllowFragmentRestore => false; ``` Did that not work for you? @PureWeen can maybe share details on why...
I think you override it and return `true`, will prevent `savedInstanceState` from being modified?
What is the error message?
Can you share an example on how you're using this? What is the error message when this breaks?
Are you able to update packages until `NU1608` goes away? You might be able to add an explicit `PackageReference` to `Xamarin.AndroidX.Lifecycle.LiveData.Core` to fix this.
There should be sufficient unit/integration tests for `dotnet run` device selection. Do you have a list of the conflicting file names? I didn't see it on the commit above.
For others reviewing: ``` CONFLICT (content): Merge conflict in src/Cli/dotnet/Commands/Run/RunCommand.cs CONFLICT (content): Merge conflict in src/Cli/dotnet/Commands/Run/RunCommandParser.cs ```
`net6.0-android` projects are building for me on a machine with a freshly installed VS 2022, so this must be an issue with upgrading. Is it possible you only hit this...