Trying to fix an urgent issue with our Xamarin iOS app and a known bug in Xamarin "IOException: Sharing violation on path /Assets.xcassets/AppIcon.appiconset/Icon-1024.png" is blocking me.

Luckily I still have my old laptop from my last upgrade on standby, boot it up and it's not using the affected version of Xamarin. 😃

Instead this one has the also know "/ios/release/mono/mini/mini-arm64.c:5439, condition `native_offset % 4 == 0' not met" blocking issue when debugging. 🤦‍♂️

I just want to do some work. ☹

  • 1
    Your company uses xamarin for their app? First time I've heard this
  • 1
    @ArtOfBBQ we actually inherited the project from another company who used Xamarin because their main language is C# and they needed a cross-platform Android/iOS app.

    The app itself is very robustly built, to be honest. Just tired of the development tools shitting themselves.

    I am just praying MAUI isn't trash.
  • 0
    Yeah I used it to make some apps and it was nice in some ways but whenever apple changed something microsoft engineers have to scramble to make some buggy emergency patch and then you autodownload and get fucked

    I eventually got more productive by blocking all autoupdates and making sure to do it only before deploying in 1 big orgy of pain & suffering . You can even move outside of visual studio if the app is robust enough and you're working on some logic piece that doesn't need a UI
Add Comment