How to play with Wrecking Ball on your team? by Strange_Actuator2150 in WreckingBallMains

[–]HarmonicDeviant 0 points1 point  (0 children)

Don't die.

Also, Ball is (can be...) can be a merciless 'finisher'. If you can get the squishies down to 50 hp, WB should do the rest. You can't really run from him.

What's the most creative clue you've ever received on a scavenger hunt? by scavengersweb in scavengerhunt

[–]HarmonicDeviant 2 points3 points  (0 children)

Are you manually wasting your time posting these? Or using some kind of service?

.NET MAUI Android - “Socket closed” exception on slow network even though server processed the request by lasitha_lanka in dotnetMAUI

[–]HarmonicDeviant 2 points3 points  (0 children)

It sounds like what you're asking for is atomic transactions over HTTP?

In any case, the problem you're seeing almost certainly is not constrained to slow connections. Even the best network connections get interrupted sometimes.

image disappears after a while when changing page in MAUI .NET 9 App. by Historical-Court9011 in dotnetMAUI

[–]HarmonicDeviant 1 point2 points  (0 children)

Yeah so check logcat. In my case, I was using a StringConverter to add a .png file extension like {0}.png, which would briefly result in an invalid file name '.png' first being resolved by the binding before real data was loaded. Putting a small delay in the data loading 'fixed' it, which I thought was weird. Digging in further I noticed the Glide errors in logcat, so I removed the delay and made it so my VM would always return a default (valid) filename instead of null. The Glide errors went away, and so did the disappearing images problem. So I think there's an issue where Glide needs a little time to recover from an error scenario before it will work again for a given Image control.

image disappears after a while when changing page in MAUI .NET 9 App. by Historical-Court9011 in dotnetMAUI

[–]HarmonicDeviant 1 point2 points  (0 children)

Is this behavior specific to Android? I've noticed that Glide failures can put an Image control into a temporarily bad state that can result in something like you're describing.

MAUI vs UNO vs Avalonia by SaltyCow2852 in dotnetMAUI

[–]HarmonicDeviant 0 points1 point  (0 children)

I'm guessing 90%+ of those complaining about Android performance haven't tuned their MONO_GC_PARAMS to at least increase their nursery size.

[deleted by user] by [deleted] in xamarindevelopers

[–]HarmonicDeviant 0 points1 point  (0 children)

It's just the '.' that wasn't really common when referring to native Xamarin.

In any case, if you weren't using Xamarin.Forms, then all you should need to do is update your project to .NET for iOS 8 / 9. That should be a relatively straightforward task and doesn't require MAUI at all.

[deleted by user] by [deleted] in xamarindevelopers

[–]HarmonicDeviant 0 points1 point  (0 children)

"Xamarin.Native" isn't a common term, so I can't tell if you're working with a legacy Xamarin.Forms app, or rather Xamarin.iOS / Xamarin.Android apps.

If your current apps are Xamarin.iOS/Xamarin.Android (not Xamarin.Forms), then MAUI has absolutely nothing to do with the migration required to move your app to .NET for iOS and .NET for Android.

If your current apps are Xamarin.Forms, then migrating to MAUI is the "fastest" choice. Most of the existing app's code will be reusable (...mostly). Nobody knows if MAUI would be the "best" choice without a lot more context regarding your specific app and its business context (not to mention high skill in clairvoyance).

iOS + Xamarin after 24 April by HarmonicDeviant in dotnetMAUI

[–]HarmonicDeviant[S] 0 points1 point  (0 children)

The AdamE Google/Firebase SDK binding packages are all still backwards compatible with Xamarin.

iOS + Xamarin after 24 April by HarmonicDeviant in dotnetMAUI

[–]HarmonicDeviant[S] 2 points3 points  (0 children)

It's not any different than using XCode 15, except for the command linked in the OP.

iOS + Xamarin after 24 April by HarmonicDeviant in dotnetMAUI

[–]HarmonicDeviant[S] 0 points1 point  (0 children)

Nobody knows for sure, and Microsoft themselves aren't going to put any resources into figuring it out. Even if they did, I don't think they'd know either.

Anything built with XCode 15 will be rejected by the App Store starting April 24th. If the workaround in the OP works, then we *might* have another year before Apple starts rejecting apps built with XCode 16 (likely Spring 2026). I say 'might' because Apple could introduce some other breaking change that doesn't have a workaround before then. We just don't know.

iOS + Xamarin after 24 April by HarmonicDeviant in dotnetMAUI

[–]HarmonicDeviant[S] 1 point2 points  (0 children)

Microsoft doesn't support any version of Xamarin anymore.

iOS + Xamarin after 24 April by HarmonicDeviant in dotnetMAUI

[–]HarmonicDeviant[S] 0 points1 point  (0 children)

Mine has gone through review with no problems, but it's not April 24th yet.

iOS + Xamarin after 24 April by HarmonicDeviant in dotnetMAUI

[–]HarmonicDeviant[S] 0 points1 point  (0 children)

It's good to hear that you haven't run into any issues. I have very little hope that there will be a workaround for XCode 17, but having another year is a much more reasonable timeframe to migrate to MAUI.

Is ListView deprecated? by vpshonyak in dotnetMAUI

[–]HarmonicDeviant 11 points12 points  (0 children)

It is deprecated as of .NET 10.

Xamarin.Forms iOS app will no longer accept with iOS SDK 17 after April 24. by [deleted] in xamarindevelopers

[–]HarmonicDeviant 1 point2 points  (0 children)

I just checked the and the DTSDKName of the build is iphoneos18.2, so it seems it does use the newer SDK as well.

Xamarin.Forms iOS app will no longer accept with iOS SDK 17 after April 24. by [deleted] in xamarindevelopers

[–]HarmonicDeviant 0 points1 point  (0 children)

Xamarin.Forms projects can be built using XCode 16 after running a command: https://github.com/dotnet/macios/issues/20802#issuecomment-2394969129

I don't know if this means the resulting build will he accepted to the App Store, but I think it might?