Maui receive event of EASessionController is lower than Xamarin. about maui HOT 7 OPEN

@rolfbjarne ?

from maui.

If I understand correctly, the problem is that your code is executing slower with MAUI than it did with Xamarin.Forms.

Do you see the same behavior with a Release build? Is it faster than a Debug build, or is it just as slow?

from maui.

If I understand correctly, the problem is that your code is executing slower with MAUI than it did with Xamarin.Forms.

Do you see the same behavior with a Release build? Is it faster than a Debug build, or is it just as slow?

Yes, understand correctly. The problem was found in our release version. Therefore the release build not works faster. The release mode could make mostly process faster besides the EA function. I have no idea to make it faster now. If you could found other solutions for us to try, we will appreciate very much.

from maui.

Can you try adding this to your csproj:

<PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <MtouchExtraArgs>--require-pinvoke-wrappers:true</MtouchExtraArgs>
    <UseInterpreter>false</UseInterpreter>
</PropertyGroup>

and see if it makes a difference?

from maui.

Can you try adding this to your csproj:

<PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <MtouchExtraArgs>--require-pinvoke-wrappers:true</MtouchExtraArgs>
    <UseInterpreter>false</UseInterpreter>
</PropertyGroup>

and see if it makes a difference?

Thanks for sharing this, however it makes the application crashes when tapping it to start.

There is a little difference in my project that MtouchExtraArgs already exists following configuration:

<MtouchExtraArgs>--require-pinvoke-wrappers:true --optimize=experimental-xforms-product-type -cxx -gcc_flags ...<MtouchExtraArgs>

I just put --require-pinvoke-wrappers:true in the front of my current configuration.

from maui.

Thanks for sharing this, however it makes the application crashes when tapping it to start.

It sounds like your app requires the interpreter for some reason. The interpreter is slower than AOT-compiled code, but it shouldn't make this much of a difference.

So we can try to enable the interpreter, but AOT-compile every assembly, which should hopefully make your app not crash at launch:

<PropertyGroup>
    <MtouchInterpreter>-all</MtouchInterpreter>
</PropertyGroup>

Can you see if that works / changes anything?

from maui.

Thanks for sharing this, however it makes the application crashes when tapping it to start.

It sounds like your app requires the interpreter for some reason. The interpreter is slower than AOT-compiled code, but it shouldn't make this much of a difference.

So we can try to enable the interpreter, but AOT-compile every assembly, which should hopefully make your app not crash at launch:

<PropertyGroup>
    <MtouchInterpreter>-all</MtouchInterpreter>
</PropertyGroup>

Can you see if that works / changes anything?

Unfortunatly, it also not works as the same phenomenon. In addition, it will need more time to finish the build process almost above 6 mins.

As you said that, our project need UseInterpreter, and it exists in .csproj:

<PropertyGroup>
     ...
     <TargetFramework>net7.0-ios</TargetFramework>
     <OutputType>Exe</OutputType>
     <RootNamespace>PalmUI</RootNamespace>
     <UseMaui>true</UseMaui>
     <SingleProject>true</SingleProject>
     <ImplicitUsings>enable</ImplicitUsings>
     <UseInterpreter>true</UseInterpreter>
    ...
</PropertyGroup>

from maui.