Closed AntunTkalcec closed 5 months ago
Describe the bug The bug is caused by version 2.1.1 and crashes the app at startup.
To Reproduce Steps to reproduce the behavior:
- Install version 2.1.1
- Build and deploy the app to an Android smartphone
- Start the app
- Crash during splash-screen
Expected behavior The app starts.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop and Smartphone (please complete the following information):
- OS: Android (OxygenOS 14.0)
- Version: Android 14
Additional context The problem is caused on version 2.1.1. 'adb logcat' had this to say: "Assertion at ..., condition 'is_ok (error)' not met, function: decode_path, module 'myapp.dll.so' is unusable (GUID of dependent assembly MauiIcons.FontAwesome.Solid doesn't match..."
The only fix is downgrading to 2.1.0.
Let me try to reproduce this issue
@AntunTkalcec I might need more information on this. Is this issue only happens on Font awesome Solid Icons? Had a chance to test it on different module?
Yes, I only tried the Solid module. Happened on multiple devices as soon as I updated to 2.1.1, and did not occur again after I downgraded to 2.1.0. Tried uninstalling and installing again (with 2.1.1) and the error still happened.
Clicked to complete the issue by accident.
Yes, I only tried the Solid module. Happened on multiple devices as soon as I updated to 2.1.1, and did not occur again after I downgraded to 2.1.0. Tried uninstalling and installing again (with 2.1.1) and the error still happened.
Thanks for the update on the issue, will patch this issue as soon as possible.
@AntunTkalcec Does this issue Happened on Dotnet 7 or 8? additionally does this issue only happens on Android?
Edit: I can't seem to reproduce this issue, I have tried Building and Deploying MauiIcons Sample App and Additionally Created a File New Maui Project and Added FontAwesome Solid to that New Project and Built that Project for Deployment and Tested on Android 14 with the Real Device
Net8. If you can't reproduce, maybe it happens due to an interaction with other NuGets? I don't see how that would be the case, but I don't know...
If you think it's possible, I'll provide you with what other packages I'm using.
Net8. If you can't reproduce, maybe it happens due to an interaction with other NuGets? I don't see how that would be the case, but I don't know...
If you think it's possible, I'll provide you with what other packages I'm using.
I don't think having other nugets would cause this issue, by the way can you try building MauiIcons sample app and try?
@AntunTkalcec Any update on this issue? Also released a new version of MauiIcons Tonight with Updated Maui Dependencies, Feel free to try whether the latest version fixes your issue.
Seems to be fine now, using AathifMahir.Maui.MauiIcons.FontAwesome.Solid 2.1.2 and Microsoft.Maui.Controls & Microsoft.Maui.Controls.Compatibility versions 8.0.10.
I'm pretty sure there was a mismatch between the Maui NuGets my app was using and the versions your NuGet was using. Though I can't be sure if that was what was causing the issue.
Seems to be fine now, using AathifMahir.Maui.MauiIcons.FontAwesome.Solid 2.1.2 and Microsoft.Maui.Controls & Microsoft.Maui.Controls.Compatibility versions 8.0.10.
I'm pretty sure there was a mismatch between the Maui NuGets my app was using and the versions your NuGet was using. Though I can't be sure if that was what was causing the issue.
I'll close this issue for now, feel free to reopen if you found facing this issue again
Describe the bug The bug is caused by version 2.1.1 and crashes the app at startup.
To Reproduce Steps to reproduce the behavior:
Expected behavior The app starts.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop and Smartphone (please complete the following information):
Additional context The problem is caused on version 2.1.1. 'adb logcat' had this to say: "Assertion at ..., condition 'is_ok (error)' not met, function: decode_path, module 'myapp.dll.so' is unusable (GUID of dependent assembly MauiIcons.FontAwesome.Solid doesn't match..."
The only fix is downgrading to 2.1.0.