thudugala
Not working in release mode
Notification working well in debug but after release App not working ⚒
Android
- Device: every device's
there's an App on android
https://play.google.com/store/apps/details?id=com.x4My_robot.salyalamohamd
code:
in debug 👇 working well
In my case the first notification works (my app). The preceding notifications don´t get fired, but I can see them in pending notifications.
After a couple of days with a couple of testers I have to say... doesn´t work at all.
I´m sorry. But that's not a fix. To disable AOT and Trimming will decrease an apps performance and increase it´s size.
Yes Fixed it , Thanks , But please take care about App performance , Thanks a gain
Trimming and AOT disable do not work on my machine and giving me this bug https://github.com/dotnet/maui/issues/7284. Any other solutions?
Hello @thudugala -- thank you so much for all the work on Plugin.LocalNotification :). I have been experiencing this issue as well. The workaround does fix the issue. However, I unfortunately will need Trimming + AOT to improve performance of my application and this is blocking my app's release. Is there another solution besides disabling AOT + Trimming?
Hello @thudugala -- thank you so much for all the work on Plugin.LocalNotification :). I have been experiencing this issue as well. The workaround does fix the issue. However, I unfortunately will need Trimming + AOT to improve performance of my application and this is blocking my app's release. Is there another solution besides disabling AOT + Trimming?
Thought I would just give an update on my problem. AOT actually was working fine with this library. My main issue was that I had set AndroidLinkType to "Full" in my project. AOT works for me.
adding
<ItemGroup>
<TrimmerRootAssembly Include="Plugin.LocalNotification"/>
</ItemGroup>
to my .csproj fixed the bug for me: this still allows AOT and trimming but excludes the library from being trimmed.
I'm still having problems getting notifications working in release mode... tried all the solutions above, but they tend to lead to other errors. Anyone have an updated fix?
