Highlights

Posts

YAYYY!!!! I think there are issues still with the fast renderers, namely the Label. I will look into it when I have some time but the "." (hints) are back on the pickers as well. Also I wanted to point out for anyone with a heavy UI should enjoy the boost on the UWP side, we found it works amazing now!

Thanks again @DavidOrtinau and the whole Xamarin team, this is an amazing release! As a side note, what is the best way to start testing Forms on MacOS?

EDIT: Ohh about the fast renderers with the Label. We crash when we enable it, so we are currently using the old renderer. I will again try to look into it when I have the time, hopefully Saturday.

EDIT2: NM stupid me, I didnt see the blog post. Forget I asked about MacOS .

Thanks @BradChase.2654, keep the feedback coming. We continue to refactor those fast renderers and know there's work yet to do. Let us know how it breaks for you, in what situation. When you have time. Saturday.

Upgrade from 2.3.4 crashes hard during startup. It's probably once again that damn CarouselView. I know I sound like a broken record, but: When can we get our hands at an updated control, or at least some updated source code that allows us to tweak it ourselves?

Btw, there seems to be a lot of issues around the (as I read deprecated) ViewGroup. I removed the CarouselView to just have a look, then got a crash from HockeyApp with ViewGroup in the StackTrace, then removed HockeyApp, just to get yet another exception (see stack trace below). So basically, no matter what parts of the UI gets to render first, everything seems to trip over that. (Note: Didn't file a bug report on this one.)

@DavidOrtinau Well I cleaned up all of our old renderers and moved old code we had since before Effects out to effects and surprise surprise, everything runs great! A TON of refactoring but looks like the issue was on our end with the fast renderer side effects and our older renderers that for the most sake are not needed anymore because of new functionality.

Cannot report a bug as a cannot find the exact cause that makes my app launch-crash upon unhandled exception in the code of nowhere after i updated to this version.
Rolled back to 2.3.4.231 yay app works again. Just to warn people.

App that uses buttons experiencing crashes in Android 4.4. Its appears that ButtonRenderer.cs in Android platform is throwing a missing method exception on anything before API 21 when it sets StateListAnimator to null during initialization.

@DavidOrtinau , on the macOS, Once I have installed Xamarin.Mac, can I create a solution that I can share between Xamarin.Mac and vs2015/17 on my pc? Obviously I would not be able to compile the Mac part, but I could work on all the shared code from my pc laptop. Thx

@ThomasBurkhart I am getting the same issues with the other fast renderers. The problem is they are not checking the disposed field before doing work on them. I have a fix but its in my custom branch and I will try to get it PR'd this weekend. I have been working weekends on rebuilding the Grid as it is measuring way too many times.

Also there are other issues with the hint's again as I presume the fast renderers started before the code fix was in for them. I have those fixes as well.

@ThomasBurkhart haha thats what I thought initially too! No I made a boo boo in cleaning up old renderers we didnt need after updating to this version for testing and I forgot the old masterdetails renderer .

To be clear, the simulator found the new one and the iphone found the old one.

@BjornB That is the same error @ThomasBurkhart is getting as well as me. I was hoping to find time this past weekend to work on it but I want to finish up the performance work I have been doing on the Grid control. I will try to find some time this week to fix it.

EDIT: I can tell you what the fix is if you are running your own branch of Xamarin Forms...

@ToddKneib said:@DavidOrtinau , on the macOS, Once I have installed Xamarin.Mac, can I create a solution that I can share between Xamarin.Mac and vs2015/17 on my pc? Obviously I would not be able to compile the Mac part, but I could work on all the shared code from my pc laptop. Thx

Hi Todd, I don't have my VS17 up and running at the moment, but I suspect the macOS project wouldn't be recognized and loaded. Of course and shared project or PCL is editable. macOS SDKs probably aren't going to be recognized. That said, you should be able to compile it because we build macOS in our CI running on Windows.

Let us know what you've discovered and what other feedback you have. Thanks!