Jonathan Peppers

Hi @jbielski, Let's just focus on one of them: ``` Function 'GetPlugin' was ignored due to ignored return decl ``` C# method: ```csharp public IPlugin GetPlugin(string name) ``` Looks like...

Yeah, @jbielski they are implemented differently. I'm thinking we _might_ have an item we need to post on the [limitations docs](https://docs.microsoft.com/en-us/xamarin/tools/dotnet-embedding/limitations).

At first I thought the `C` code generator might not support interfaces, but there is a test for it: https://github.com/mono/Embeddinator-4000/blob/d697cdfca5060c07e95063c30f4864bd0a36b0ca/tests/common/Tests.C.cpp#L380-L391 I think you are likely hitting a bug. The workaround...

@jbielski the above error likely means E4K can't find one of the following: - Android NDK - Android SDK - Java If you have all of these, we may need...

@emysa341 this is something we've been needing to do for a while now, I've been having to focus on Xamarin.Android itself lately. The problem with updating the version of Xamarin.Android,...

Hi @PluginIO, Can you make sure you have the latest Embeddinator 0.4.0 on NuGet? This looks like an issue with version 0.3.0.

We need to get latest master on NuGet, one of the things we are working on atm. For now, can you try building from source with what is on master?...

@kevinhowarddr the other part I see in your log: ``` MonoAndroidToolsPath path is not found and no default location is provided; skipping ``` Did the build script download `xamarin-android` to...

I found that `restore` is what causes this problem. So you can workaround by doing something like: ``` $ dotnet new maui $ dotnet restore $ dotnet build -f net6.0-ios...

@Mephisztoe I think you should be able to run `dotnet restore` first, then use `--no-restore` when you run `publish`.