@JohnHardman how did you find out that it doesnt work any longer? are you testing on a real device?
@batmaci - Yes, testing on a physical Amazon Fire tablet
@JohnHardman I don't believe we're aware of such a thing. Is this using a specific version of Forms, or any of them? More details here would be appreciated.
@PaulDiPietro - I was probably still on 2.3.4.x when I previously tested on Amazon Fire, at which point it was working fine. I am currently using XF 220.127.116.11779, but am encountering "Java.Lang.IncompatibleClassChangeError: interface not implemented" when I start interacting with the app, for example clicking on a ListView item.
As part of the standard QA process for XF releases, are any UITests run on Amazon Fire to check that basic interactions complete successfully? If so, what Amazon Fire versions are checked?
For info, Xamarin stuff (including various @JamesMontemagno plugins) used is as follows:
@DavidOrtinau I see that Right-To-Left functionality has been moved to VNext+1, what does this mean for the release date? It really is the only thing holding me off from releasing my app.
@JohnHardman Just at a glance, it looks like the Xamarin.Android.Support.v7.CardView's package version is misaligned with the others. Perhaps this could have something to do with it? If it doesn't, it may be worth filing a bug for with a reproduction; we might have seen a report pop up at some point if all Fire devices were being affected like this, so if the package isn't the cause, there could be a certain scenario causing the crash and we'd just need to know more.
Take a look at https://www.xamboy.com/2018/03/08/adding-badge-to-toolbaritem-in-xamarin-forms
This discussion should be focused on the roadmap. To add new feature requests, use https://github.com/xamarin/Xamarin.Forms/issues
@PaulDiPietro - After much investigation, I managed to get things working on Amazon Fire again. The problem appears to have been (although I have not yet confirmed this 100% - will hopefully do that later today, or some time tomorrow) an unresolvable conflict between dependencies on versions of Microsoft.CSharp . Having spotted that, I removed all NuGets and references dependent on Microsoft.CSharp, then re-installed them again.
Having encountered issues before where upgrading or downgrading NuGet packages has left detritus behind (typically in project files), I'm normally pretty good at spotting these sorts of issues. This one with Microsoft.CSharp took quite a while though :-( Before releasing any app to production, I do recommend anybody uninstall all the NuGets they use, check the csproj files for things that shouldn't be there, then re-install the NuGets.
BTW - Do you have any info about how many XF developers are building for Amazon Fire? Whenever I have asked Amazon Fire related questions on the forum I have received zero response. Are XF releases tested on Amazon Fire?
@DavidOrtinau there are over 500 bugs listed on GitHub, and it is now Q2, I was just wondering if we could get an update to the roadmap. Thanks
@PaulBrenner yep, I'll have a roadmap update by Build. It accounts for F100 (the tag on GitHub) and clarifies a few things on the current roadmap.
Please note quite a few of those 500 are housekeeping items as we've been preparing 3.0 for stable release. And I acknowledge more are continuing to migrate from the old Bugzilla instance - such as several I believe you helped elevate (thanks!).
@DavidOrtinau 3.0 is released and there are now 600+ issues on github. Any chance are you guys going to implement a system that lets us prioritize issues? At this point I think it is really needed.
Also any update/ETA on the carousel view and title view PRs? Thanks
@DavidOrtinau I think 6 week release cycle is long time. For example I will wait 1.5 month for Frame shadow bug. I'm afraid update Xamarin Forms to 3.1 because of Bugs. I agree with @PaulBrenner lets us prioritize issues please.
@PaulBrenner @gkhanikisivri please use the reactions on the issues to register your votes. We are looking at those.
Hi all, just wanted to call attention to our sprint boards up on GitHub. In addition to the feature roadmap, these boards give everyone more visibility into the bug fixes we are working during each sprint.
Is a Xamarin XAML Designer ever going to be on the roadmap? We have such designers for XAML in Visual Studio, but for some reason we lack one in Xamarin. Having a designer is key to increasing productivity and time-to-market. From a business and developer-customer standpoint, I do not understand why this is not already present. We had a designer in Visual Basic 1.0 in the last century, for goodness sakes!
The viewer is OK, but does nothing to improve rapid application development (RAD) like a designer would. We have a Windows Forms designer, XAML designer (for Windows apps), even HTML designers - but no Xamarin XAML designer.
Microsoft already knows how - so why not make the designer a priority???
I am working on a cross-platform designer for Android and iOS using HTML. It works rather well with Android and is very accurate in converting HTML to Android XML. I was reading a Xamarin.Forms book at the time which gave me the idea to make one when I noticed there wasn't really a cross-platform designer made by anyone. It is available on GitHub under the project name "androme".
It is built using TypeScript and going all the way I probably would integrate it with Monaco and build a designer inside the browser. That would depend on my library being popular which it isn't since it is only 2.5 months old and nobody knows about it yet. iOS integration would take me no more than a few weeks although that is also based on popularity or demand.
@DavidOrtinau There are now over 800 issues on github for forms. Do you know if Microsoft has any plans to add developers for the project? I know it is open source but it is going to take you guys decades to get through even half of the issues. With the rapid growth of bugs it is impossible to recommend forms to anyone.
We have been patiently waiting for a working CarouselView for a very long time now. I just noticed that the PR for it was closed with a note saying the CollectionView will replace it. I cannot find the CollectionView on the road map. Do you have a realistic ETA for it being in a stable release?
@PaulBrenner we are hiring, yes.
At DotNetConf last week, I shared the plan for CarouselView. CollectionView is also now on the Roadmap, and is the basis for CarouselView. https://github.com/xamarin/Xamarin.Forms/wiki/Feature-Roadmap
I hope to be previewing both of those before the end of the year.
Re: the number of issues, for clarity they are not all confirmed, actionable bugs. Many are housekeeping and enhancements. That said, I would love to get the bug numbers down, but more importantly we are prioritizing to work them in the order of highest impact. If you have a blocking bug that is not being scheduled (see the project sprint board), shoot me a message and I'll be able to provide more details and discuss it specifically). [email protected]
@DavidOrtinau What about Livereload? is it a project to do it once and forget? we were so excited about it but it is not useful any longer. I have already reported 2 major issues. i was told that they are queued, even fixed but since more than 6 months no update. Those are
Now recently came out that livereload is using old rx libraries (version 3.0) and most of the useful packages like Prism, Akavache etc we are using updated to latest version 4.x. Installing both causes conflicts and whatever tried we cant fix it.
I am writing this here because livereload doent have any github for issues. I could fix most of myself even if it was open sourced which is also not. there is only gitter but i dont think that it is as efficient as github issues.
Xamarin Inc., as a wholly-owned Microsoft subsidiary acting as a separate legal entity, adheres to the Microsoft Privacy Statement: Privacy & cookies