locked
Xamarin.Forms 2.2.0 RRS feed

  • Question

  • User173875 posted

    2.2.0 hotfix 1

    News

    In parallel to this 2.2.0 hotfix release, Nuget packages for Xamarin.Forms 2.3.0-pre3 and Xamarin.Forms.CarouselView 2.3.0-pre1 were also shipped. As the CarouselView's version suggests, it has a dependency on Xamarin.Forms 2.3.0 ("-pre3" or greater).

    Bug fixes

    36955 -[iOS] ViewCellRenderer.UpdateIsEnabled Object reference not set to an instance of an object . 40844 - [Android] Forms Android app gets stuck with GC bridge calls when using current beta branch of Xamarin.Android/Mono Runtime

    2.2.0

    News

    Open source

    With this release we open source Forms. The Xamarin.Forms GitHub repo is here. The source for 2.2.0 is here.

    CarouselView split into separate package

    CarouselView, which appeared in Xamarin.Forms 2.2.0-pre1 through pre4, has been been removed from the Xamarin.Forms package, and moved into its own Nuget package.

    Bug fixes

    40656 - iOS WebView Rotation, Sizing and Scaling issues

    2.2.0-pre4

    Bug fixes

    39821 - ViewExtension.TranslateTo cannot be invoked on Main thread(Android Marshmellow devices only). 40555 - App crashes when setting VisualElement.Scale to 0

    Other fixes

    Fixed "System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found"

    2.2.0-pre3

    Bug fixes ##

    39987 - MapView not working correctly on iOS 9.3 40209 - Getting exception after launching forms sample "BugSweeper" 40228 - Calling Task.Wait in on OnStateChanged on main thread hangs the app 40334 - CarouselView does not work on UWP Forms 2.2.0 Pre-2 40434 - CarouselView.Item throws a NullReferenceException 40435 - Entry on UWP crashing with nullreference exception Xamarin.Forms V2.2.0-pre2

    Other fixes ##

    [Android] Update android support packages to 23.3 [Core] CarouselView Fixes (CarouselView.Item, formatting, ItemsView.Count to IItemsViewController, Remove dead code, re-layout subviews on resize, add ItemTemplate to resources.xaml on UWP, Docs) [Android] Use style resources when calling SetTextAppearance [Android] Allow designer to disable asynchronicity in image loading. [UWP] Unhook Entry and Editor event handlers during Dispose [WinRT] Fix WebView.Eval [Android] Remove unneeded cast in ListViewRenderer [Android] Fix relaunch template app hangs; Port fix from OnStateChange in FormsAppCompatActivity to FormsApplicationActivity [UWP] Adjust bounds for ContentPage when by itself [iOS] Add iOS localized string resource assemblies to nuspec [Nuget] Remove Google Play Services dependency

    2.2.0-pre2

    Bug fixes

    39499 - CarouselView layout rendering issue on Android 40152 - ListView doesn't trigger item selection 40173 - Android Frame blocks ListView selection

    Other fixes

    [Android] Fix race condition in IsInvokeRequired [Android] Fix issue where API23 became required by mistake [Core] Cast to ICommand instead of Command inside SearchBar [Core] Automatically marshal all AnimationExtensions calls onto UI thread [Android] Ensure carouselView disposes correctly [Android, iOS] Other CarouselView bug fixes and behavior correction: No ItemSelected or PositionSelected event is fired upon start. PositionSelected precedes ItemSelected after movement. When setting the position causes pages to be skipped events are only raised for the target page.

    2.2.0-pre1

    New Features

    Updated Google Package Dependencies

    Xamarin.Forms on Android now depends on GooglePlayServices 29.0.0.1 for maps and Xamarin.Android.Support.v4 (and friends) at 23.1.1.1.

    Margins

    Adding margin support is intended to allow users to reduce the overall depth of their layout hierarchies by allowing more complex layouts with fewer wrapping views. public Thickness Margin { get; set; }

    UWP Maps

    UWP Maps are now supported, just like other platforms.

    CarouselView

    CarouselView is intended to fully replace CarouselPage. CarouselPage will be deprecated in a future release. CarouselView is superior in many ways, including its ability to be virtualized and nested within layouts.

    Nest platform controls to Forms layout

    Allows adding platform-specific controls (iOS, Android, and Windows) directly to a Forms layout. Note: this isn't available from PCL and requires #if defines to work from a shared project.

    2D ScrollView Support

    scrollView.Orientation = ScrollOrientation.Both

    AutomationId Support

    Xamarin.Forms now has first class support for setting automation identifiers for usage with Xamarin UITest or other testing frameworks. Simply setting the AutomationID property should allow the automation framework to find and interact with your controls.

    Bug Fixes

    21177 - Using a UICollectionView in a ViewRenderer results in issues with selection. 21699 - WebView does not propagate its BindingContext to its Source 23393 - [All platforms] PropertyChangedEventHandler causes 2 consecutive calls to changed property's getter 25234 – WP8 - Light theme status bar disappears after DisplayAlert 25662 - Setting IsEnabled does not disable SwitchCell in Forms listview 27350 - Binding throws Null Pointer Exception when Updating Tab 27417 - Button.Image behaviors differently on each platform and has extra padding even with no Text 28628 - Reuse of cell containing an Image that are async loaded will display the previous image. 28709 - Application.Properties saving crash 31670 - On WinRT, BackgroundColor of Button is used to paint outside the border of Buttons with rounded corners 32462 - Crash after a page disappeared if a ScrollView is in the HeaderTemplate property of a ListView 33181 - InitializeComponent() method call in XAML code behind page constructor "does not exist in current context" (IntelliSense error) 33240 - IOS ListViewRenderer.Dispose() should dispose header and footer 34055 - Listview with custom CellView render error on iOS9 landscape iPad 35407 - jobject muste not be IntPtr.Zero with Animation 36479 - [WP] Picker Is Not Disabled When IsEnabled is Set To False 36788 - [Forms] Truncation Issues with Relative Layouts 36850 - ProgressBar BackgroundColor not working in iOS 37113 - MasterDetailPage swipe gesture doesn't work after IsGestureEnabled is toggled 37625 - App crashes when quickly adding/removing Image views (Windows UWP) 37841 - [Forms Android] TableView EntryCell's and TextCell's cease to update after focus change 38112 - [Forms][Android] Switch disappearing from TableView ViewCell on Android only 38193 - OpenGLViewRenderer crashes when leaving the page. 38416 - ListView Sized Incorrectly After Containing Layout's Visibility is Toggled 38658 - Rotation causes app containing carousel page to freeze 38978 - Cell.ForceUpdateSize issues with row selection/deselection on Android 39039 - Toggling Grouping on Listview + ListViewCaching.RecycleElement Sometimes Doesnt Render Group Header 39104 - iOS Navigation.ModalStack not the same as Android and Windows 39239 - Xamarin.Forms.Platform.Android.FontExtensions.ToScaledPixel missing case for NamedSize.Default 39327 - Application.Current.Properties does not persist on Android 39331 - [Android] BoxView Is InputTransparent Even When Set to False 39342 - NullReference Exception when attempting to push a new page 39359 - Image View does cache failed HTTP responses 39377 - ListView.Footer not update iOS 39378 - Image binding with caching not operating as expected 39395 - SwitchCell does not take all available place inside ListView 39403 - [Android] Forms 2.1.0, Switching tabs that have NavigationPages throws: Java.Lang.IllegalStateException: Recursive entry to executePendingTransactions 39409 - SearchBar.SearchCommand does not respect CanExecute 39447 - [Windows Phone 8.1] Images not rendered in ListView unless explicit size set 39449 - UWP: Dependency attribute in 3rd party assemblies 39450 - [Forms] ListView item shrinks / resizes when removing then adding Context Action in ViewCell OnBindindContextChanged. 39451 - Unable to activate instance of type Xamarin.Forms.Platform.Android.ListViewAdapter from native handle 39458 - [UWP/WinRT] Cannot Set CarouselPage.CurrentPage Inside Constructor 39461 - UWP: Labels within a ScrollView are blurred 39463 - [WP8.0] Items not showing in ListView using DataTemplate when there are more items than can fit on screen. 39464 - [UWP Forms] Rounded Button Corners do not render in Forms (but do in native UWP 39476 - [Forms] Selecting item in ListView and scrolling with RecycleElement results in more items selected. 39483 - ListView Context Menu localization 39495 - MasterDetail missing Navigation Bar Windows RT 39506 - Effects.Clear does not detach the effect. 39509 - Setting Page Content doesn't work 39548 - CarouselPage does not work in UWP on Windows 10 Mobile 39566 - System.InvalidOperationException: Sequence contains more than one matching element 39624 - [UWP] CarouselPage.Children Appear Out of Order 39668 - Overriding ListView.CreateDefault Does Not Work on Windows 39702 – Cannot enter text when Entry is focus()'d from an editor completed event 39721 - "Failed to add reference to 'Xamarin.Forms.Core.Design'" when adding XF 2.1.0.6529 NuGet in Windows 81 project 39742 - OnAppearing not triggered if coming back after leaving Android app via home button 39815 - ScrollView is overlapping other content in StackLayout on Android 39829 - RowHeight of ListView is not working for UWP 39831 - MasterDetailPage showing back button instead of Icon in landscape mode (Tablet only) 39853 - BorderRadius ignored on UWP 39870 - Xamarin.Forms.Maps Geocoder GetPositionsForAddressAsync always returns an empty set on Android 39896 - StreamImageSource Streams Aren't Disposed

    Other Fixes

    • Resolve crash when serializing properties.
    • [Core] Resolve issue where binding to a bound property would invalidate the second binding
    • [Core] Resolve issue where template bindings resolve the the wrong templated parent in some nesting scenarios
    • [Android] Make sure not to update image bitmap in background thread
    • [Android] Fix potential crash in OnLayout after resume
    • [Android] Fix bug with ActivityIndicator default color on Lollipop+
    • [Android] Fix NRE in OnScroll method in android
    • [Android] Fix crash when pressing back to exit the app
    • [Android] Change Forms class to accept Context type arguments and upcast to Activity as necessary.
    • [iOS] Fix crash when visiting website with weird URL handling
    • [iOS] Fix crash in VisualElementPackager if re-used on same element
    • [RT] Make sure editor has wrapping enabled
    • [RT] Add missing binding for SearchBox text
    • [UWP] Invalidate Image when loaded in a way which Grid won't ignore
    • [UWP] Make sure Scrollview measures child inside of measure call
    • [UWP] Make sure we dont construct a negative value size
    • [UWP] Fix UWP bug where app bar icon color is ignored on modal NavigationPages
    • [UWP] Fix more instances of Layout Cycle detected
    • Many other minor bug fixes

    Known Issues

    • CarouselView can sometimes fail to display content on Android
    • CarouselView programmatic moving of index broken
    • SearchBar.SearchCommand will crash when set to non Xamarin.Forms.Command ICommand.
    • Tapping a BoxView or Frame in a ViewCell will not trigger selection

    Important notes

    • When upgrading Xamarin.Forms take care not to simply "update all" as that will update the Xamarin.Android.Support packages to an incompatible version. More info here: https://developer.xamarin.com/guides/xamarin-forms/troubleshooting/
    Tuesday, April 5, 2016 5:13 AM

All replies

  • User76916 posted

    Wow! Ok now I know why you were taking your time with this one :)

    Tuesday, April 5, 2016 5:29 AM
  • User76916 posted

    The Intellisense error still isn't resolved. I have a UWP app, Visual Studio 2015 Enterprise Update 2, latest Xamarin and the latest Nuget package 2.2.0. I even did a full machine reboot afterwards, rebuilds, deleting everything in the obj/bin directries and I also tried the latest Xamarin in the Alpha channel.

    33181 - InitializeComponent() method call in XAML code behind page constructor "does not exist in current context" (IntelliSense error)

    I still get the IntelliSense error.

    Tuesday, April 5, 2016 6:23 AM
  • User352 posted

    @AdamP can you please make sure your .targets file was updated properly?

    Tuesday, April 5, 2016 6:53 AM
  • User352 posted

    @AdamP also please be aware that the fix does require a fresh rebuild after deleting the obj/bin directories. Also are you using resharper or code rush?

    Tuesday, April 5, 2016 6:55 AM
  • User76916 posted

    @TheRealJasonSmith - yes the proj references the new .targets files. Im not using resharper or code rush or anything similar.

    Tuesday, April 5, 2016 7:48 AM
  • User76049 posted

    @BryanHunterXam

    Thanks for pushing #27417 up the priority list :smile:

    Tuesday, April 5, 2016 7:57 AM
  • User67129 posted

    Is there any documentation / blogposts on using the CarouselView?

    Also

    Xamarin.Android.Support.v4 (and friends) at 32.1.1.1.

    Is this a typo and actually means 23.1.1.1? Latest stable version of these packages is 23.2.1. I'm guessing we should only be updating to 23.1.1.1?

    Tuesday, April 5, 2016 8:07 AM
  • User76049 posted

    @BryanHunterXam

    Does this release given the ability to move ContentPage.ToolbarItems to the left? It's something we need to soon preferably without fragile custom renderer hacks.

    Tuesday, April 5, 2016 8:14 AM
  • User352 posted

    @JKay not a typo. We have not had time to run those packages with Forms through the QA ringer yet. We will likely be updating this release before final.

    Tuesday, April 5, 2016 8:29 AM
  • User166393 posted

    I tried to create a sample project using carouselview, It is showing some exception. Here is my sample project. As far as I know I have to use the same logic that I have used for carousel page.

    Tuesday, April 5, 2016 8:38 AM
  • User57869 posted

    I updated to 2.2.0.4-pre1, closed VS2015, deleted the old packages/Xamarin.Forms.* folder, deleted all bin+obj folders, checked all *.csproj and packages.config files if they really reference the correct version, restarted VS, removed the references to Xamarin.Forms.Core.Design and Xamarin.Forms.Xaml.Design from the PCL project, rebuilt and got 117 errors in the Android/Resources/Resource.designer.cs file. :-(

    Tuesday, April 5, 2016 12:20 PM
  • User58587 posted

    Had the same issue, did all the usual tricks cleaned, deleted bin/obj folders, deleted c:\users{username}\AppData\Local\Xamarin, updated Android SDK, forced complete reinstall of nuget packages. In the end I tracked it down to xamarin forms oxyplot package. In the end I pulled down the source for the xamarin forms version from github and recompiled it with 2.2pre, that seemed to fix the Resource.Id issues. The nuget package does use the 23.0.1.3 Xamarin.Android.Support so i guess it can't coexist with version 23.1.1.1.

    Tuesday, April 5, 2016 12:52 PM
  • User67129 posted

    same issue as @MichaelRumpler here..

    Some more information on how I upgraded. I just clicked Xamarin.Forms.Maps and hit upgrade for all my projects and let Xamarin.Forms.Maps sort out the dependencies.

    No interfering with Xamarin.Android etc...

    Tuesday, April 5, 2016 1:03 PM
  • User167259 posted

    Any chance of https://bugzilla.xamarin.com/show_bug.cgi?id=39310 being addressed. I know it's marked as minor but it's makes it so much easier to create custom check box controls and custom icons within an app without having to jump through hoops of redoing all your images each time you decide that you want to change the size a little. It's my number 1 irritation with Xamarin Forms.

    Tuesday, April 5, 2016 2:28 PM
  • User57869 posted

    @DavidDunscombeWrk I tried that. I have dependencies to XLabs and DevExpress.Grid.

    When I tried to update XF in XLabs, I got

    3>D:\Xamarin-Forms-Labs\packages\Xamarin.Forms.2.2.0.4-pre1\build\portable-win+net45+wp80+win81+wpa81+MonoAndroid10+MonoTouch10+Xamarin.iOS10\Xamarin.Forms.targets(62,3): error MSB4018: The "XamlCTask" task failed unexpectedly. System.IO.FileNotFoundException: Could not load file or assembly 'Mono.Cecil, Version=0.9.6.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' or one of its dependencies. The system cannot find the file specified. File name: 'Mono.Cecil, Version=0.9.6.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'

    I don't have the sources of the DevExpress.Grid. I tried rebuilding their GridDemo with the new XF and got the same errors in the Resource.designer.cs, which I got in my app. Just not so many. Only 78. There's already a ticket in DX support. DevExpress' support is very fast, so I'm confident that they will send a new version to Xamarin within 2 days. But then Xamarin has to release it to the component store ...

    So I'll revert and wait...

    Tuesday, April 5, 2016 2:56 PM
  • User352 posted

    Did you restart your IDE after updating? The target cant reload with the IDE open.

    Tuesday, April 5, 2016 6:22 PM
  • User173875 posted

    @NMackay said: @BryanHunterXam

    Does this release given the ability to move ContentPage.ToolbarItems to the left? It's something we need to soon preferably without fragile custom renderer hacks.

    No, that isn't part of this round.

    Tuesday, April 5, 2016 8:56 PM
  • User76049 posted

    @BryanHunterXam said:

    @NMackay said: @BryanHunterXam

    Does this release given the ability to move ContentPage.ToolbarItems to the left? It's something we need to soon preferably without fragile custom renderer hacks.

    No, that isn't part of this round.

    Oh well :neutral: fair enough. Thanks for responding.

    Tuesday, April 5, 2016 9:23 PM
  • User103333 posted

    CarouselView WTF!! (Well Thats Fantastic) Does the brand new CarouselView have a navigation-dot-like included? or is just like the CarouselPage but with the ability to be nested on the layouts?

    Wednesday, April 6, 2016 1:11 AM
  • User57869 posted

    DevExpress said that they won't build their Grid for XF pre-release versions. This effectively means that if you depend on the DevExpress.Grid, then you cannot use XF 2.2.0 until it was released and DevExpress made a new version with it.

    Wednesday, April 6, 2016 7:41 AM
  • User76049 posted

    @MichaelRumpler said: DevExpress said that they won't build their Grid for XF pre-release versions. This effectively means that if you depend on the DevExpress.Grid, then you cannot use XF 2.2.0 until it was released and DevExpress made a new version with it.

    Telerik are the same. You can't blame them as they have to QA test their controls against the official release before passing it on to customers. I'm sure they'll have a beta if you ask them nicely, ,Telerik ahve helped me in the past if I was on a time crunch and a bug fix was in the new beta build.

    Wednesday, April 6, 2016 8:03 AM
  • User58587 posted

    Just to be clear - the Resource.id issue is expected behavior for this release, until other 3rd party assemblies get updated?

    Wednesday, April 6, 2016 10:11 AM
  • User40173 posted

    @DavidDunscombeWrk if that's true we have to remove our nuget packages and manually checkout all sources and update them to 2.2.0. We depend on some packages which get rarely updated by the author...

    Wednesday, April 6, 2016 3:35 PM
  • User58587 posted

    It wasn't clear in my last post but i was asking Xamarin if that is the case.

    Wednesday, April 6, 2016 3:38 PM
  • User78996 posted

    @TheRealJasonSmith is there a reason why one of the GooglePlayServices libraries is now a requirement for Xamarin.Forms? We currently deploy to devices with and without Google Play Services and this could really impact us.

    Wednesday, April 6, 2016 3:54 PM
  • User352 posted

    @JMarcus that will be resolved before final, we need to add some code for some graceful degradation in some new features that are coming

    Wednesday, April 6, 2016 5:27 PM
  • User78996 posted

    @TheRealJasonSmith Thank you for the quick response. Good to know.

    Wednesday, April 6, 2016 5:28 PM
  • User179286 posted

    Any chance to have Commands for ListView Events added? It's annoying that we have to create our own ListView classes to properly use it in MVVM designs.

    Thursday, April 7, 2016 6:13 AM
  • User120969 posted

    Argh, can't build Android due to resource errors - Only one of the 3rd Party libraries being used works out-of-the-box.

    Thanks for fixing my Windows issue though (39495 - MasterDetail missing Navigation Bar Windows RT) everything seems to be good in the Windows RT project so far.

    Thursday, April 7, 2016 1:07 PM
  • User2593 posted

    After upgrading to XF 2.2.0-pre1 on Android, my app hangs if I navigate away (back-button or home), and then resume by pressing the App icon.

    Breaking in the debugger during the hang, I see the following stack trace: System.Threading.Monitor.Monitorwait() in System.Threading.Monitor.Wait(object obj, int millisecondsTimeout) in /Users/builder/data/lanes/3053/a94a03b5/source/mono/mcs/class/corlib/System.Threading/Monitor.cs:148 System.Threading.ManualResetEventSlim.Wait(int millisecondsTimeout, cancellationToken) in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/ManualResetEventSlim.cs:669 System.Threading.Tasks.Task.SpinThenBlockingWait(int millisecondsTimeout, cancellationToken) in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:3356 System.Threading.Tasks.Task.InternalWait(int millisecondsTimeout, cancellationToken) in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:3295 System.Threading.Tasks.Task.Wait(int millisecondsTimeout, cancellationToken) in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:3201 System.Threading.Tasks.Task.Wait() in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:3083 Xamarin.Forms.Platform.Android.FormsApplicationActivity.OnStateChanged() in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:300 Xamarin.Forms.Platform.Android.FormsApplicationActivity.OnStop() in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:215 Android.App.Activity.nOnStop(System.IntPtr jnienv, System.IntPtr native__this) in /Users/builder/data/lanes/3053/a94a03b5/source/monodroid/src/Mono.Android/platforms/android-23/src/generated/Android.App.Activity.cs:4925 object.70e2e675-bff2-4b3c-a10f-bcf6bd7ddefe( arg0, arg1) in

    So it is waiting for some Task in Android.FormsApplicationActivity.OnStateChanged(), never really having completed the n_OnStop, but what is it waiting for?

    The stack trace is devoid of any code I wrote, but is it possible for me as an application programmer to cause this hang?

    Thursday, April 7, 2016 1:37 PM
  • User105957 posted

    Is there any possibility that 37663 will be addressed in 2.2.0? The rendering problem with Android context actions means we've gone to an alternate solution, adding toolbar buttons of trash cans all over the app, which is not exactly an elegant solution.

    Thursday, April 7, 2016 6:53 PM
  • User203330 posted

    Any chance of Bug 39827 being fixed in final release? I really don't want to recreate my project as a PCL and/or change all my XAML code to c# just to be able to build in UWP

    Friday, April 8, 2016 7:07 AM
  • User2593 posted

    @KasperOvergrdNielsen said: After upgrading to XF 2.2.0-pre1 on Android, my app hangs if I navigate away (back-button or home), and then resume by pressing the App icon.

    I have raised a bugreport on this 40228, that includes a workaround if anybody else needs it.

    Friday, April 8, 2016 12:14 PM
  • User203068 posted

    @ThomasBurkhart said: Any chance to have Commands for ListView Events added? It's annoying that we have to create our own ListView classes to properly use it in MVVM designs.

    Why create your own ListView class ? Just create a generic behavior to convert any event into command and enjoy :)

    --> https://blog.xamarin.com/turn-events-into-commands-with-behaviors/

    You can even create a bindable Behavior to bind anything that you want on a control and not events only. You can find it on this post :smile:

    --> http://adventuresinxamarinforms.com/tag/xamarin-forms-maps/

    Friday, April 8, 2016 3:07 PM
  • User179286 posted

    @antonin.3432 Thanks for the suggestion. I prefer the extended ListView because it makes the Xaml more readable. Anyway, all Events should be available as Commands for the standard controls.

    Saturday, April 9, 2016 9:13 AM
  • User113114 posted

    @AdamNull , thats not a bug, and here is your solution <item name="windowActionModeOverlay">true</item>. Add that to your style, if youre using forms appcompat, add it in the base style (not v21).

    It would be nice if xamarin included this in their tutorial though :P, scratched my head a lot with this one @XamarinHQ

    Saturday, April 9, 2016 5:20 PM
  • User42408 posted

    CarouselView throws System.InvalidCastException. (Xamarin.Forms 2.2.0.5-pre2 on iOS and Android)

    My code

    <?xml version="1.0" encoding="UTF-8"?> <ContentPage xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" x:Class="XFApp20.MyPage"> <ContentPage.Content> <CarouselView x:Name="carouselView"> <CarouselView.ItemsSource> <x:Array Type="{x:Type x:String}"> <x:String>first</x:String> <x:String>second</x:String> <x:String>third</x:String> </x:Array> </CarouselView.ItemsSource> <CarouselView.ItemTemplate> <DataTemplate> <TextCell Text="{Binding}" /> </DataTemplate> </CarouselView.ItemTemplate> </CarouselView> </ContentPage.Content> </ContentPage>

    StackTrace(iOS)

    at Xamarin.Forms.ItemsView.Xamarin.Forms.IItemViewController.CreateView (System.Object type) [0x0000b] in :0 at Xamarin.Forms.Platform.iOS.CarouselViewController+Cell.Initialize (IItemViewController controller, System.Object itemType, System.Object item, Int32 position) [0x00017] in :0 at Xamarin.Forms.Platform.iOS.CarouselViewController.GetCell (UIKit.UICollectionView collectionView, Foundation.NSIndexPath indexPath) [0x000a2] in :0 at (wrapper managed-to-native) UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr) at UIKit.UIApplication.Main (System.String[] args, IntPtr principal, IntPtr delegate) [0x00005] in /Users/builder/data/lanes/3051/5f11db87/source/maccore/src/UIKit/UIApplication.cs:77 at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x00038] in /Users/builder/data/lanes/3051/5f11db87/source/maccore/src/UIKit/UIApplication.cs:61 at XFApp20.iOS.Application.Main (System.String[] args) [0x00008] in /Users/P3PPP/Projects/XFApp20/iOS/Main.cs:17

    StackTrace(Android)

    at Xamarin.Forms.ItemsView.Xamarin.Forms.IItemViewController.CreateView (System.Object type) [0x0000b] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Core\ItemsViewSimple.cs:56 at Xamarin.Forms.Platform.Android.ItemViewAdapter.OnCreateViewHolder (Android.Views.ViewGroup parent, Int32 viewType) [0x0000d] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\Renderers\CarouselViewRenderer.cs:1222 at Android.Support.V7.Widget.RecyclerView+Adapter.nOnCreateViewHolderLandroidviewViewGroupI (IntPtr jnienv, IntPtr nativethis, IntPtr nativeparent, Int32 viewType) [0x00011] in :0 at (wrapper dynamic-method) System.Object:bc27b837-4681-415d-ba4f-653106ab7bb7 (intptr,intptr,intptr,int)

    Sunday, April 10, 2016 7:11 AM
  • User352 posted

    @AdamNull it is at the top of our to-fix list. No promises because we only recently got a minimal reproduction but we will be trying.

    Monday, April 11, 2016 6:59 AM
  • User113114 posted

    @BjornB said: @AdamNull , thats not a bug, and here is your solution <item name="windowActionModeOverlay">true</item>. Add that to your style, if youre using forms appcompat, add it in the base style (not v21).

    It would be nice if xamarin included this in their tutorial though :P, scratched my head a lot with this one @XamarinHQ

    @TheRealJasonSmith what is there to fix if this already fixes it? Try it out in the attached project for the "bug".

    Monday, April 11, 2016 8:42 AM
  • User49731 posted

    Noticed that tap and hold in listview to bring up contextactions in UWP seems to only work if tapping on area in listitem that has a control beneath it .. if you tap and hold in space to the right (when label is less width than screen) although something detects it as it's highlighted, the contextactions do not appear.

    see this link too :

    https://forums.xamarin.com/discussion/64053/do-listview-contextactions-work-on-uwp#latest

    Monday, April 11, 2016 10:58 AM
  • User65389 posted

    @DerekPapworth.4183 Not sure, but I had a similar problem a longer time ago with WP 8.1. To set the backgroundcolor to a color was the solution...

    Monday, April 11, 2016 1:34 PM
  • User120969 posted

    For a Pre-Release this is looking very promising - It's not often that I upgrade Xamarin.Forms and bugs have been fixed without new ones being introduced.

    One happy Xamarin user right here :smile: . Please keep it up!

    Monday, April 11, 2016 7:54 PM
  • User352 posted

    @BjornB because it was my understanding the people running into this issue were already encountering this. Though on closer inspection it turns out the docs somehow have that setting dropped though it was in our original porting guide, hence why not everyone was getting this issue. Interesting. Either way the docs are going to be updated.

    Monday, April 11, 2016 9:15 PM
  • User195856 posted

    I have problem. After installation the newest version (pre2) all properties defined in styles override my properties in the controls. For example:

    Style:

    <Style x:Key="MainButtonStyle" TargetType="custom:MyButton">
      <Setter Property="BackgroundColor" Value="Red"/>
      <Setter Property="TextColor" Value="White"/>
      <Setter Property="BorderRadius" Value="0"/>
      <Setter Property="BorderWidth" Value="0"/>
    </Style>
    

    Button:

     <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    In app BackgroundColor is Red (as Style), and should be Black.

    Is it bug? Or it can be changed in the code?

    Tuesday, April 12, 2016 8:10 AM
  • User352 posted

    Does it happen with every control or just some?

    Tuesday, April 12, 2016 9:26 AM
  • User352 posted

    @P3PPP CarouselView doesn't use Cells

    Tuesday, April 12, 2016 9:27 AM
  • User195856 posted

    @TheRealJasonSmith said: Does it happen with every control or just some?

    Entry - bad Label - bad StackLayout - good BoxView - good

    Button is strange... If I'm using Custom Renderer, all properties defined in styles override my properties. If I'm not using CR everything is ok.

    Button is black:

    <Button Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    Button is not black (because in styles property is red):

    <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />`
    
    Tuesday, April 12, 2016 10:08 AM
  • User42408 posted

    @TheRealJasonSmith Thanks for answer. It workes fine if I use views instead of cells.

    Tuesday, April 12, 2016 10:21 AM
  • User81232 posted

    I updated to 2.2.0-pre2 and I can't compile my android forms app because of over 100 errors in resources.designer.cs file. Is this just me and my solution or is there a workaround/fix or something I'm doing wrong? I have all the updated Android SDK's etc...

    Tuesday, April 12, 2016 10:02 PM
  • User103333 posted

    @TheRealJasonSmith said: @P3PPP CarouselView doesn't use Cells

    @TheRealJasonSmith I have a ContentView on a CarouselView but no content is displayed, the ContentView has the standard Stacklyaout and a label.

    Tuesday, April 12, 2016 10:37 PM
  • User28549 posted

    @TheRealJasonSmith | @BryanHunterXam, am I reading this right?

    [Core] Automatically marshal all AnimationExtensions calls onto UI thread

    fixes

    Tuesday, April 12, 2016 11:12 PM
  • User140202 posted

    @MichaelDimoudis have you done a clean/rebuild and possibly restart XS/VS?

    Tuesday, April 12, 2016 11:23 PM
  • User76916 posted

    @MichaelDimoudis - I recently blogged about Android build errors because it just comes up so frequently.

    Let me know if my playbook for resolving Android build errors works for you: http://www.xamarinhelp.com/debugging-xamarin-android-build-and-deployment-failures/

    Tuesday, April 12, 2016 11:25 PM
  • User132171 posted

    Looks like 2.2 breaks Azure Mobile Services Authentication on Android which is a too bad cause outside of this it seems to be an awesome update for us. Calling MobileService.LoginAsync(Forms.Context,myidp) Brings up the authenticate screen but it is blank. Backreving to 2.1 fixes it.

    Tuesday, April 12, 2016 11:27 PM
  • User352 posted

    @JeffDalby which backend are you using?

    Wednesday, April 13, 2016 4:26 AM
  • User132171 posted

    Old mobile services, not the new stuff. Last I had looked a few months ago we couldn't migrate because we store user data based on the id from the provider which would change if we moved to app services. Probably should look if there is a fix for that yet.

    Regardless, it seems something has changed on the Forms end since all I have to do is update to break it. Maybe something with how it handles passing Forms.Context to display the login page from the IDP?

    Wednesday, April 13, 2016 5:03 AM
  • User67129 posted

    @MichaelDimoudis This is ususally down to a third party control not referencing the pre release Forms version. For me it was Syncfusion Datagrid. Have a closer look at the resources and you should be able to figure out what is causing those erros

    Wednesday, April 13, 2016 7:36 AM
  • User57869 posted

    I finally managed to compile all dependencies with pre2 which made my problems with the Resources.designer.cs go away.

    But this doesn't fix the "IllegalStateException: Recursive entry to executePendingTransactions", it makes it much worse. Now I get that exception every time I try to navigate. I created bug 40333 for that.

    Wednesday, April 13, 2016 9:31 AM
  • User57869 posted

    @AdamP I saw your blog post and found some things I didn't encounter yet. And I thought I got them all!

    But unfortunately when I delete the contents of the Resources.designer.cs file and recompile, my VS2015 does not regenerate the full file. It just creates an empty Resources class. Any idea how I can trigger that? The only thing which worked for reliably for me is installing a different XF version, but that takes very long.

    Wednesday, April 13, 2016 9:36 AM
  • User65827 posted

    Can we pretty please get this Bug - 31809 fixed?

    Wednesday, April 13, 2016 11:47 AM
  • User76916 posted

    @MichaelRumpler - I haven't seen that one in about a year. Have you tried deleting everything from Resources, then closing VS, deleting the bin and obj, then starting again and rebuilding? The obj cache sometimes causes intermittent issues.

    Then in your .proj file, this is just a check, that this exists (it probably will) <AndroidResgenFile>Resources\Resource.Designer.cs</AndroidResgenFile>

    Also I will suspect you have this further down but I have known Xamarin installs / reinstalls to mess around with these properties before

    <Import Project="$(MSBuildExtensionsPath)\Xamarin\Android\Xamarin.Android.CSharp.targets" />

    Then in your MSBuild\Xamarin\Android\Xamarin.Android.CSharp.targets that should reference the Resources.Designer.cs file.

    In the Xamarin.Android.Common.targets I found this, but at this point I am wildly speculating that maybe the temporary file is failing to create, hence not being copied.

        <!-- Only copy if the file contents changed, so users only get Reload? dialog for real changes -->
        <CopyIfChanged
            SourceFiles="$(ResgenTemporaryDirectory)\$(AndroidResgenFilename)"
            DestinationFiles="$(_AndroidResourceDesignerFile)"
            Condition="'$(_AndroidResourceDesignerFile)' != '' And Exists ('$(ResgenTemporaryDirectory)\$(AndroidResgenFilename)')"
        />
    
        <!-- Delete our temporary directory -->
        <RemoveDirFixed Directories="$(ResgenTemporaryDirectory)" />
    
        <!-- If there are no _AndroidResource items, create a blank file -->
        <CreateAndroidResourceStamp
            Condition="'$(_AndroidResourceDesignerFile)' != ''"
            AndroidResgenFile="$(_AndroidResourceDesignerFile)"
            AndroidResourceDest="@(_AndroidResourceDest)"
            MonoAndroidResDirIntermediate="$(MonoAndroidResDirIntermediate)"
            AndroidResgenFlagFile="$(_AndroidResgenFlagFile)" />
    

    The temporary files from MSBuild should be created in AppData\Local\Temp. If they are lingering around that could be causing and issue, I would also try wiping this directory. It shouldn't ever use the same directory again for the temp file but I am grasping at straws here :)

    I just went through all that to check if the MSBuild config files are all in order, its the only thing I could think of that Xamarin would update and what could cause the Resources.Designer.cs not to re-generate again. Maybe with a process not releasing locks on temporary files as needed or something similar.

    Wednesday, April 13, 2016 12:19 PM
  • User57869 posted

    Thanks, @AdamP , some more things I can check.

    I did delete the Resources' contents, deleted bin/obj and restarted VS, but I didn't check the rest as I didn't know, how generating that file is triggered/works.

    The error appears, when you change some dependencies like you already wrote, but also when I change .axml files in my Android project which I use in my custom renderers. Sometimes those changes will not be reflected in the Resources.designer.cs file.

    Wednesday, April 13, 2016 12:38 PM
  • User33994 posted

    https://bugzilla.xamarin.com/show_bug.cgi?id=40320 this has been a long standing issue for our implementation of our custom cell (no renderers, just a stack of labels and images). Seems to still be here for 2.2. Any thoughts @TheRealJasonSmith

    Wednesday, April 13, 2016 4:11 PM
  • User49731 posted

    @TheRealJasonSmith - Following on from my earlier post in here on issue with contextmenu not firing in ListView in Windows UWP I've done some more investigation and it appears the Cell in the ListView is not obeying the FillAndExpand or StartAndExpand in ListView and hence the contextmenu is only being triggered if tapped within the non-expanded cell limits. To check this I added background colour to my cell and as you can in attached captured pic when I tap (right click in this case as Windows UWP) on 4th cell for instance the highlight of the listview item covers complete width but cell doesn't. However same code exactly works fine in iOS, Android, Windows Phone 8.1 Silverlight but in the case of Windows UWP or Windows 8.1 I get this result. Apart from not being right, it means contextmenu won't work unless you tap inside the cell rather than just listitem which when no background colour used is difficult to tell. Any clues or is this a bug?

    p.s. Just to confirm as don't have screenshots to hand, in iOS, Android and Windows Phone with same aqua background set the colour covers complete width in all listitems with exactly same code.

    Wednesday, April 13, 2016 5:26 PM
  • User120969 posted

    @DerekPapworth.4183 said: @TheRealJasonSmith - Following on from my earlier post in here on issue with contextmenu not firing in ListView in Windows UWP I've done some more investigation and it appears the Cell in the ListView is not obeying the FillAndExpand or StartAndExpand in ListView and hence the contextmenu is only being triggered if tapped within the non-expanded cell limits. To check this I added background colour to my cell and as you can in attached captured pic when I tap (right click in this case as Windows UWP) on 4th cell for instance the highlight of the listview item covers complete width but cell doesn't. However same code exactly works fine in iOS, Android, Windows Phone 8.1 Silverlight but in the case of Windows UWP or Windows 8.1 I get this result. Apart from not being right, it means contextmenu won't work unless you tap inside the cell rather than just listitem which when no background colour used is difficult to tell. Any clues or is this a bug?

    p.s. Just to confirm as don't have screenshots to hand, in iOS, Android and Windows Phone with same aqua background set the colour covers complete width in all listitems with exactly same code.

    There was a similar sort of issue in Windows RT where the content of a List View header template wouldn't expand even though it was set to, my workaround was WidthRequest = 5000. Though this is no longer an issue in 2.2pre 2.

    As a workaround you should be able to set a really wide WidthRequest and it'll just go as wide as the screen is.

    Wednesday, April 13, 2016 5:46 PM
  • User76916 posted

    @MichaelRumpler - just to clarify, you change something in Android, it doesn't regenerate, you delete the file and it still doesn't generate?

    That one is tricky. Its almost like it thinks the file is generated already. I would probably try and get this in front of someone on the Android team in Xamarin, unless we can think of any idea on what is stopping that MSBuild process.

    While it should never reuse temporary folders again, I am thinking that when my deployment starts failing and I need to change something in my project, e.g. From Shared Runtime to not, to trigger it to deploy successfully again, it seems like something is getting locked. I might try deleting my temp folder when that happens to me again. It happens about every 5-10 build/deploys for me, so shouldn't be long. That might hint at a possible issue in Android's build process.

    Thursday, April 14, 2016 12:14 AM
  • User103333 posted

    Margin property is awesome!!

    Just one thing, on a ListView each element is a ViewCell with a grid inside but the margin is not respected on iOS, on android Works as spected. Pseudo code:

    *CustomViewCell code:

    var grid = new Grid()
            {
                Margin = 5,
                Padding = 0,
                RowSpacing = 0,
                ColumnSpacing = 0,
                RowDefinitions =
               {
            new RowDefinition { Height = new GridLength (20, GridUnitType.Absolute) },
               },
                ColumnDefinitions =
               {
                    new ColumnDefinition {Width = new GridLength(60, GridUnitType.Absolute)},
                    new ColumnDefinition {Width = new GridLength(60, GridUnitType.Auto)},
               }
            };
    View = grid;
    

    *ListView creation

            ListView Wall = new ListView(ListViewCachingStrategy.RecycleElement);
            Wall.RowHeight = 65;
            Wall.SeparatorVisibility = SeparatorVisibility.None;
    
            List<miniObject> Data = new List<miniObject>();
    
            for (int i = 0; i <= 30; i++ )
                Data.Add(new miniObject() { Text = "Element "+ i.ToString() });
    
    
            var cell = new DataTemplate(typeof(CustomViewCell));
            Wall.ItemTemplate = cell;
            Wall.ItemsSource = Data;
            Wall.HasUnevenRows = false;
    
    Thursday, April 14, 2016 12:59 AM
  • User49731 posted

    @Matthew.4307 - Great tip Matthew, thanks! I've set a widthrequest in the cell to 5000 and works a treat. I don't like using workarounds so hope it gets fixed in next release but at least I can continue for now so thanks again!

    Thursday, April 14, 2016 9:47 AM
  • User215658 posted

    Hi, I'm testing the CarouselView. How can i hook up to the OnItemAppearing/Disappearing event? I see it exists on the assembly but there's no public accessor to it from the carouselview c# class/object.

    Thanks

    Thursday, April 14, 2016 1:11 PM
  • User1948 posted

    Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    Stack trace: `System.AggregateException: One or more errors occurred.

    Thread finished: #5 04-14 21:05:18.246 D/Mono ( 2824): [0xb9bd60c0] worker finishing The thread '' (0x5) has exited with code 0 (0x0). 04-14 21:05:37.002 D/Mono ( 2824): DllImport attempting to load: '/system/lib/liblog.so'. 04-14 21:05:37.002 D/Mono ( 2824): DllImport loaded library '/system/lib/liblog.so'. 04-14 21:05:37.002 D/Mono ( 2824): DllImport searching in: '/system/lib/liblog.so' ('/system/lib/liblog.so'). 04-14 21:05:37.002 D/Mono ( 2824): Searching for 'androidlogprint'. 04-14 21:05:37.002 D/Mono ( 2824): Probing 'androidlogprint'. 04-14 21:05:37.002 D/Mono ( 2824): Found as 'androidlogprint'. 04-14 21:05:37.002 I/MonoDroid( 2824): UNHANDLED EXCEPTION: 04-14 21:05:37.002 I/MonoDroid( 2824): System.AggregateException: One or more errors occurred. ---> System.MissingMethodException: Method 'Looper.getIsCurrentThread' not found. 04-14 21:05:37.002 I/MonoDroid( 2824): at Xamarin.Forms.Device.getIsInvokeRequired () [0x00000] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Core\Device.cs:32 04-14 21:05:37.002 I/MonoDroid( 2824): at Xamarin.Forms.Application+d46.MoveNext () [0x0000a] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Core\Application.cs:125 04-14 21:05:37.002 I/MonoDroid( 2824): --- End of inner exception stack trace --- 04-14 21:05:37.002 I/MonoDroid( 2824): at System.Threading.Tasks.Task.ThrowIfExceptional (Boolean includeTaskCanceledExceptions) [0x00014] in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:2168 04-14 21:05:37.002 I/MonoDroid( 2824): at System.Threading.Tasks.Task.Wait (Int32 millisecondsTimeout, CancellationToken cancellationToken) [0x00052] in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:3218 04-14 21:05:37.002 I/MonoDroid( 2824): at System.Threading.Tasks.Task.Wait () [0x00000] in /Users/builder/data/lanes/3053/a94a03b5/source/mono/external/referencesource/mscorlib/system/threading/Tasks/Task.cs:3083 04-14 21:05:37.002 I/MonoDroid( 2824): at Xamarin.Forms.Platform.Android.FormsApplicationActivity.OnStateChanged () [0x00057] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:300 04-14 21:05:37.002 I/MonoDroid( 2824): at Xamarin.Forms.Platform.Android.FormsApplicationActivity.OnStop () [0x00019] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\FormsApplicationActivity.cs:215 04-14 21:05:37.002 I/MonoDroid( 2824): at Android.App.Activity.nOnStop (IntPtr jnienv, IntPtr nativethis) [0x00009] in /Users/builder/data/lanes/3053/a94a03b5/source/monodroid/src/Mono.Android/platforms/android-21/src/generated/Android.App.Activity.cs:4581 04-14 21:05:37.002 I/MonoDroid( 2824): at (wrapper dynamic-method) System.Object:94297873-f0f9-4c03-9f45-a1228c83cdee (intptr,intptr) 04-14 21:05:37.002 I/MonoDroid( 2824): ---> (Inner Exception #0) System.MissingMethodException: Method 'Looper.getIsCurrentThread' not found. 04-14 21:05:37.002 I/MonoDroid( 2824): at Xamarin.Forms.Device.get_IsInvokeRequired () [0x00000] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Core\Device.cs:32 04-14 21:05:37.002 I/MonoDroid( 2824): at Xamarin.Forms.Application+d46.MoveNext () [0x0000a] in C:\BuildAgent3\work\aad494dc9bc9783\Xamarin.Forms.Core\Application.cs:125 <---`

    Thursday, April 14, 2016 7:27 PM
  • User120969 posted

    I'm having issues with the Appearing events firing on Windows 8.1 for Tabbed Page and Master Detail Page, I thought it was a introduced in 2.2 issue until I was able to recreate in 2.1 while building my reproduction solution.

    https://bugzilla.xamarin.com/show_bug.cgi?id=40408

    Thursday, April 14, 2016 8:04 PM
  • User2148 posted

    @TheRealJasonSmith I use CarouselView and it works. I have this code in a ContentPage:

    CarouselView cv = new CarouselView ();
    cv.ItemsSource = _lista;
    cv.ItemTemplate = new DataTemplate (typeof(BarcodeTemplate));
    sl.Children.Add (cv);
    

    where

    public ObservableCollection<string>_lista = new ObservableCollection<string>();
    

    and

    public class BarcodeTemplate : ContentView {
    
        public BarcodeTemplate(){
    
            Label l = new Label();
            l.FontSize = 40;
            l.SetBinding (Label.TextProperty,".");
            Content = l;
        }
    }
    

    I fill the _lista with a webservice but the CarouselView is not updated correctly. To update the CarouselView I have to swipe from left to right or from right to left. How can I have the CarouselView updated immediately after the WS has changed the _lista? Do I implement INotifyPropertyChanged (If I use the same code with ListView with ViewCell instead of ContentView, I don't have to use INotifyPropertyChanged)

    This is a video that explain the problem. When I insert a Text in the Entry and press Enter on the keyboard, I receive data from WS and fill "_lista" but the first view of the CarouselView is not updated (remains "EMPTY"). If I swype to right and the to left, the View is updated

    http://screencast.com/t/YH1gNOvZgVV

    thanks

    Thursday, April 14, 2016 9:54 PM
  • User103333 posted

    @AlessandroCaliaro @TheRealJasonSmith Using a more complex ContentView, CarouselView doesn't show anything

    Friday, April 15, 2016 3:14 AM
  • User51906 posted

    @TheRealJasonSmith Ok, maybe I missed it. But why on earth where the dependenices for GooglePlayServies imbedded so deeply? I can't even remove them!?

    Friday, April 15, 2016 6:40 AM
  • User213733 posted

    is there somewhere a documentation, what nuget update version x with xamarin.forms y works. Have 600 errors like Fehler CS0117 "Resource.String" enthält keine Definition für "statusbarnotificationinfooverflow". and even my old project doesnt compile any longer since installed Xamarin.VisualStudio_4.1.0.298 also update of xamarin.support.design ... downgrade xamarin.forms to 1.5

    Monday, April 18, 2016 5:44 AM
  • User57869 posted

    @HannesPreishuber We talked about the errors in the REsource.designer.cs file at the very beginning of this thread. XF 2.2 raised the version of the Xamarin.Android.Support.* libraries. This seems to require, that all dependencies need to be compiled with that new version too. If these are open source, then you can compile them yourself. Otherwise you need to ask their supplier for a new version. Until this is there, you need to stay with XF 2.1. You don't need to go back to 1.5 unless the new versions introduced any other bugs which you depend upon.

    Monday, April 18, 2016 7:41 AM
  • User213733 posted

    it's not about a need to downgrade to 1.5 - it's happening by upgrading the other packets

    Monday, April 18, 2016 8:02 AM
  • User120969 posted

    Is there anything Xamarin can do that means we don't feel massive pain with 3rd party libraries caused by the Android.Support.x packages changing? I've faired quite well as I only needed to re-engineer one library, but for some it could be an absolute nightmare.

    Monday, April 18, 2016 3:15 PM
  • User4685 posted

    Having XF hard dependency on Xamarin.Android.Support.* libraries is a issue at the moment, especially for people who create XF components and well actually pretty much anyone who uses Xamarin.Forms.

    As component developers should we have different nuget versions for each of the different versions of .Forms? Is there a better solution?

    I hope there's a better way coming soon. :)

    Tuesday, April 19, 2016 1:46 AM
  • User76916 posted

    @TheRealJasonSmith - CarouselView is awesome, except found a bug when I switch the MainPage. https://bugzilla.xamarin.com/show_bug.cgi?id=40502

    Is there any chance you could add switching the MainPage as a common test scenario. My apps rely on it a lot and it frequently breaks XF :)

    Tuesday, April 19, 2016 3:31 AM
  • User76916 posted

    @MichaelRidland - there has only been one way I have found (though tedious and not ideal) of removing XF dependencies within components and that is to provide some kind of wire up.

    With Exrin I have: https://github.com/exrin/Tesla-Mobile-App/blob/master/Tesla/Tesla/Tesla/Wire/NavigationContainer.cs

    It wires up the NavigationContainer to a NavigationPage. You have to do the mappings manually but then Exrin never relies on Xamarin Forms. Though the developer has to do that in their project, create a class that implements the interface, then inject it into the DI framework.

    With so many issues on XF dependencies in the past, I will work around however I can to ensure I never created a component with an XF dependency again. Though I realize this can not always be effectively done.

    Tuesday, April 19, 2016 3:36 AM
  • User3066 posted

    About CarouselView: Any chance to get Orientation option?

    Tuesday, April 19, 2016 3:57 PM
  • User120969 posted

    @AdamP said: @TheRealJasonSmith - CarouselView is awesome, except found a bug when I switch the MainPage. https://bugzilla.xamarin.com/show_bug.cgi?id=40502

    Is there any chance you could add switching the MainPage as a common test scenario. My apps rely on it a lot and it frequently breaks XF :)

    I hope that for all bug fixes that are reported via bugzilla either have the original reproduction or re-engineered version added as an automated regression test. I fear this isn't the case though. If a Xamarin user raises a bugzill that means their application has been broken but that issue, and it has caused them some level of cost (time and or money) it is not fair on that individual if that isn't added as a regression test by Xamarin.

    Tuesday, April 19, 2016 7:10 PM
  • User76916 posted

    @Matthew.4307 - they do have tests and regression testing from what I know. The problem I described is more that a particular scenario keeps surfacing new bugs. Or something they don't account for when doing their initial tests on the code. But considering how many people I keep recommending that navigation solution to, its going to become more common.

    Also Windows isn't as thoroughly tested as Android and iOS because they don't have UITest for windows hence I know that internally they currently have to manually test for each windows release. Unless they magically release UITest for Windows at Evolve (I can but dream :) )

    Wednesday, April 20, 2016 1:34 AM
  • User120969 posted

    @AdamP said: @Matthew.4307 - they do have tests and regression testing from what I know. The problem I described is more that a particular scenario keeps surfacing new bugs. Or something they don't account for when doing their initial tests on the code. But considering how many people I keep recommending that navigation solution to, its going to become more common.

    Also Windows isn't as thoroughly tested as Android and iOS because they don't have UITest for windows hence I know that internally they currently have to manually test for each windows release. Unless they magically release UITest for Windows at Evolve (I can but dream :) )

    UITests for Windows is really needed, we are investing in Xamarin Test for Android and iOS but need to use Test Complete for Windows which means duplication of effort.

    Wednesday, April 20, 2016 7:42 AM
  • User120969 posted

    Is there a reason the tabs have now gone like this instead of spanning the whole width of the screen?

    Wednesday, April 20, 2016 8:16 AM
  • User113114 posted

    @Matthew.4307
    If you want your tabs to take up all avaliable width you can set that in you tabs.axml (or whatever you named it)

    app:tabMaxWidth="0dp" app:tabGravity="fill" app:tabMode="fixed"

    I assume you are not using the maxwidth prop. My personal thoght though would be to keep it the way it is in your screenshot :)

    Wednesday, April 20, 2016 10:37 AM
  • User173875 posted

    @fortinguillaume said: Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    Thanks! The team fixed this one last night. It will be in the next release.

    Wednesday, April 20, 2016 2:40 PM
  • User171749 posted

    @BryanHunterXam said:

    @fortinguillaume said: Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    Thanks! The team fixed this one last night. It will be in the next release.

    Hi When is the next release with this fix in?

    Thanks

    Wednesday, April 20, 2016 2:44 PM
  • User120969 posted

    @BjornB said: @Matthew.4307
    If you want your tabs to take up all avaliable width you can set that in you tabs.axml (or whatever you named it)

    app:tabMaxWidth="0dp" app:tabGravity="fill" app:tabMode="fixed"

    I assume you are not using the maxwidth prop. My personal thoght though would be to keep it the way it is in your screenshot :)

    That's not it, it was working fine in pre2, this seems to be something introduced in pre3. It isn't affecting all devices, just some, and only in Landscape.

    Seems that Jelly Bean devices are affected but Kit Kat+ are fine.

    EDIT: My tabs.axml wasn't specifying anything for tabMaxWidth, adding =0 has now fixed my device specific issue, I guess some have default values for tabMaxWidth.

    Wednesday, April 20, 2016 3:39 PM
  • User173875 posted

    @SeanDavies.1435 said:

    @BryanHunterXam said:

    @fortinguillaume said: Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    Thanks! The team fixed this one last night. It will be in the next release.

    Hi When is the next release with this fix in?

    Thanks

    I expect pre4 to ship in the next 24 hours.

    Wednesday, April 20, 2016 6:19 PM
  • User120969 posted

    @BryanHunterXam said:

    @SeanDavies.1435 said:

    @BryanHunterXam said:

    @fortinguillaume said: Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    Thanks! The team fixed this one last night. It will be in the next release.

    Hi When is the next release with this fix in?

    Thanks

    I expect pre4 to ship in the next 24 hours.

    Is it looking promising that there won't be many more preX and 2.2 will soon be regarded as stable? Is it just fixes going in or is there still functionality going in?

    Wednesday, April 20, 2016 6:24 PM
  • User173875 posted

    @Matthew.4307 said:

    @BryanHunterXam said:

    @SeanDavies.1435 said:

    @BryanHunterXam said:

    @fortinguillaume said: Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    Thanks! The team fixed this one last night. It will be in the next release.

    Hi When is the next release with this fix in?

    Thanks

    I expect pre4 to ship in the next 24 hours.

    Is it looking promising that there won't be many more preX and 2.2 will soon be regarded as stable? Is it just fixes going in or is there still functionality going in?

    Yes, should just be fixes from here.

    Wednesday, April 20, 2016 6:32 PM
  • User173875 posted

    Thanks for all the feedback on this thread. Without it, some very annoying bugs would have made it to stable.

    We are currently working on a problem (app crashes) related to Android API<23 using AppCompat. The problem is tied to a package update. That will be fixed before stable.

    Not a real problem after all. An issue with a reproduction project instead. :)

    Wednesday, April 20, 2016 6:53 PM
  • User105043 posted

    Hi,

    I've a System.ArgumentOutOfRangeException when trying to set the Position of a CarouselView but only on Android. It works well on iOS.

    xCarouselView.BindingContextChanged += (object sender, EventArgs e) =>
    { var a = (xCarouselView.ItemsSource as IList).Count; this.xCarouselView.Position = 3; };
    I've 6 items in the ItemsSource property.

    Thanks ;)

    Thursday, April 21, 2016 12:44 AM
  • User76916 posted

    @BryanHunterXam - I mentioned this critical CarouselView bug on WinRT when -pre2 was the latest release.

    https://bugzilla.xamarin.com/show_bug.cgi?id=40502

    is there any chance this will be fixed before 2.2.0 hits stable?

    Thursday, April 21, 2016 12:56 AM
  • User195856 posted

    .

    @PawelTkti said: I have problem. After installation the newest version (pre2) all properties defined in styles override my properties in the controls. For example:

    Style:

    <Style x:Key="MainButtonStyle" TargetType="custom:MyButton">
        <Setter Property="BackgroundColor" Value="Red"/>
        <Setter Property="TextColor" Value="White"/>
        <Setter Property="BorderRadius" Value="0"/>
        <Setter Property="BorderWidth" Value="0"/>
    </Style>
    

    Button:

     <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    In app BackgroundColor is Red (as Style), and should be Black.

    Is it bug? Or it can be changed in the code?

    @TheRealJasonSmith said: Does it happen with every control or just some?

    @PawelTkti said:

    @TheRealJasonSmith said: Does it happen with every control or just some?

    Entry - bad Label - bad StackLayout - good BoxView - good

    Button is strange... If I'm using Custom Renderer, all properties defined in styles override my properties. If I'm not using CR everything is ok.

    Button is black:

    <Button Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    Button is not black (because in styles property is red):

    <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />`
    

    Does it work in the latest version Xamarin Forms?

    Thursday, April 21, 2016 7:10 AM
  • User57869 posted

    @BryanHunterXam

    Well, as long as bug #40333 is not fixed, you cannot make it stable. That was clearly a regression introduced in XF 2.1 and made worse in 2.2. I'm currently locked to 2.1.0.6508-pre3 because of that.

    Thursday, April 21, 2016 7:39 AM
  • User57869 posted

    I tried to upgrade the repro project from bug #40333 from XF 2.2.0.5-pre2 to 2.2.0.23-pre4, but then I get a "java.lang.OutOfMemoryError" when I try to compile the Android project.

    I set the MSBuild project build output verbosity to Diagnostic. The output is attached. You can see that CompileToDalvik needs 50secs before it fails.

    The Android SDK Manager is up to date. Compiling with 2.2.0.5 still works.

    Thursday, April 21, 2016 8:18 AM
  • User78996 posted

    Bug 37113 does not appear to be fixed in pre4.

    Thursday, April 21, 2016 1:44 PM
  • User53703 posted

    @fortinguillaume said: Application crash on version 2.2.0.5-pre2 when you resume then back to android application who use Xamarin.Forms. Reproduce with Xamarin.Forms sample application (WorkingWithBehaviors application sample).

    Error : System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found.

    This issue appears fixed with 2.2.0.23-pre4.

    Thursday, April 21, 2016 4:20 PM
  • User28549 posted

    @MichaelRumpler said: @BryanHunterXam

    Well, as long as bug #40333 is not fixed, you cannot make it stable. That was clearly a regression introduced in XF 2.1 and made worse in 2.2. I'm currently locked to 2.1.0.6508-pre3 because of that.

    I'd say the same thing for 39821

    Thursday, April 21, 2016 4:41 PM
  • User28549 posted

    @MichaelRumpler said: I tried to upgrade the repro project from bug #40333 from XF 2.2.0.5-pre2 to 2.2.0.23-pre4, but then I get a "java.lang.OutOfMemoryError" when I try to compile the Android project.

    I set the MSBuild project build output verbosity to Diagnostic. The output is attached. You can see that CompileToDalvik needs 50secs before it fails.

    The Android SDK Manager is up to date. Compiling with 2.2.0.5 still works.

    @MichaelRumpler just change your Max Heap Size.

    Thursday, April 21, 2016 4:45 PM
  • User57869 posted

    @MichaelRumpler just change your Max Heap Size.

    Thanks, that worked. Now Xamarin, please set it as default if it doesn't work without it. This is a repro project with almost no code in it.

    The bug is still there in 2.2.0.23-pre4.

    Thursday, April 21, 2016 5:18 PM
  • User139758 posted

    Has it been determined when the code is going to be released? Or which release?

    Thursday, April 21, 2016 5:39 PM
  • User120969 posted

    Getting some layout issues on Windows RT. When there are Entry fields in a list they are often not resizing the height correctly. No problems on pre1, 2 or 3.

    Thursday, April 21, 2016 6:00 PM
  • User197084 posted

    Is there a way with the new CarouselView to have it "peek" the previous and next item in the list? In other words, show a small part of the previous and next item rather than having the control filling the entire space it is within. I quickly dabbled with the new control but didn't see a way to handle this in my PCL.

    Thursday, April 21, 2016 7:46 PM
  • User2148 posted

    @TravyDale said: Is there a way with the new CarouselView to have it "peek" the previous and next item in the list? In other words, show a small part of the previous and next item rather than having the control filling the entire space it is within. I quickly dabbled with the new control but didn't see a way to handle this in my PCL.

    this should be very interesting

    Thursday, April 21, 2016 7:57 PM
  • User66766 posted

    +1 @TravyDale

    Thursday, April 21, 2016 8:59 PM
  • User28549 posted

    @BryanHunterXam just a suggestion. When introducing new Views in a Pre-Release, I think it would be super cool if you attached a ScreenShot... similar to what you've done with the views in the official docs.

    https://developer.xamarin.com/guides/xamarin-forms/controls/views/

    This would help us get an idea of what we're getting without having to fully build it out just to see it.

    The reason I'm saying this is that with the new CarouselView, I'm interested in knowing if it has page indicators, and what they look like.

    Thursday, April 21, 2016 9:48 PM
  • User105043 posted

    @ChaseFlorell +1, it would be great ! Quick answer : no it doesn't have page indicators. I've seen somewhere that somebody succeeded in adding them but I don't remember... (I know it doesn't help you very much ^^)

    Thursday, April 21, 2016 9:57 PM
  • User105043 posted

    @BryanHunterXam Just for your informations (and to avoid duplicate bugs for people who are following this thread), I've created 5 new bugs in bugzilla :

    40630 CarouselView with ItemsSource null or empty throws Exception (v2.2.0.18-pre3) 40631 Setting CarouselView.Position throw exception (v2.2.0.18-pre3) 40632 CarouselView missed a "SelectedItem" property (v2.2.0.18-pre3) 40634 CarouselView fires (or not) "ItemSelected" or "PositionSelected" in an buggie way (v2.2.0.18-pre3) 40635 CarouselView needs either a page indicator or show part of the left and right pages (v2.2.0.18-pre3)

    CarouselView is an incredible component which really helps us to build great interfaces ! I hope you would consider these bugs and new features requested for the stable version.

    Friday, April 22, 2016 1:31 AM
  • User76916 posted

    I am currently out of time this week to provide a full bug report but the WebView in iOS is severely broken in 2.2.0.

    1 - Rotate the webview once and of course due to the never getting out of INPROGRESS bug report: https://bugzilla.xamarin.com/showbug.cgi?id=30047 it doesn't give the correct height. But by doing this you could essentially fix it if you had it full screen (which I did)

       public override void LayoutSubviews()
        {
            base.LayoutSubviews();
    
            CGRect bounds = UIScreen.MainScreen.Bounds;
            bounds.Height = NativeView.Bounds.Height;
    
            NativeView.Bounds = bounds;
    
        }
    

    This now no longer works.

    2 - Do a rotate to landscape, then back to portrait and the width of the WebView is half the screen.

    3 - Go away from the WebView, then go back to the page, then rotate and you get this exception (everytime)

    System.ObjectDisposedException: Cannot access a disposed object.

    Object name: 'WebViewRenderer'.

    Of course if I do this it stops the error

      protected override void Dispose(bool disposing)
            {
               // base.Dispose(disposing);
            }
    

    But it looks like the WebViewRenderer shouldn't be disposed at that point until the actual page or control is disposed of.

    This was all done on an iPhone 4S and 6 simulators on iOS 9.2

    Friday, April 22, 2016 1:32 AM
  • User162453 posted

    @ChaseFlorell Are > @ChaseFlorell said:

    @MichaelRumpler said: @BryanHunterXam

    Well, as long as bug #40333 is not fixed, you cannot make it stable. That was clearly a regression introduced in XF 2.1 and made worse in 2.2. I'm currently locked to 2.1.0.6508-pre3 because of that.

    I'd say the same thing for 39821

    @ChaseFlorell The fix for 39821 should be in pre4; I think it just got missed in the release notes. Let me know if it's still giving you any trouble.

    Friday, April 22, 2016 2:33 AM
  • User103333 posted

    @MiguelCervantes said:

    @TheRealJasonSmith said: @P3PPP CarouselView doesn't use Cells

    @TheRealJasonSmith I have a ContentView on a CarouselView but no content is displayed, the ContentView has the standard Stacklyaout and a label.

    Am i missing something?

    Friday, April 22, 2016 3:42 AM
  • User2148 posted

    @DavidCASBONNE there is the @ChrisRiesgo CarouselView on GitHub that has indicators. Are you talking about it?

    Friday, April 22, 2016 5:50 AM
  • User2148 posted

    @MiguelCervantes for me it works. Can you post your code?

    Friday, April 22, 2016 5:59 AM
  • User2148 posted

    @MiguelCervantes this is my code

    using System;
    using Xamarin.Forms;
    using System.Collections.ObjectModel;
    using SimpleCustomGesureFrame;
    
    namespace TestBth
    {
        public class PageCarousel : ContentPage
        {
    
            public PageCarousel (ObservableCollection<string> lista)
            {
                NavigationPage.SetTitleIcon (this, "icon.png");
                NavigationPage.SetHasNavigationBar (this, true);
                NavigationPage.SetHasBackButton (this, true);
    
                Title = "RIBALTE";
                StackLayout sl = new StackLayout ();
    
                CarouselView cv = new CarouselView ();
                cv.ItemsSource = lista;
                cv.ItemTemplate = new DataTemplate (typeof(BarcodeTemplate));
                sl.Children.Add (cv);
    
                Content = sl;
    
            }
    
            public class BarcodeTemplate : ContentView {
    
                public BarcodeTemplate(){
    
                    TapGestureRecognizer tgr = new TapGestureRecognizer();
                    tgr.NumberOfTapsRequired = 2;
                    tgr.Tapped += async (object sender, EventArgs e) => {
                        await App.MyNavPage.PopAsync ();
                    };
    
                    GestureRecognizers.Add (tgr);
                    Label l = new Label();
                    l.FontSize = 40;
                    l.SetBinding (Label.TextProperty,".");
                    Content = l;
    
                }
            }
        }
    }
    
    Friday, April 22, 2016 6:02 AM
  • User105043 posted

    @AlessandroCaliaro said: @DavidCASBONNE there is the @ChrisRiesgo CarouselView on GitHub that has indicators. Are you talking about it?

    Yes and no :) I'm talking about the built-in CarouselView in XF 2.2.0 pre3 but the one from @ChrisRiesgo inspired me for the indicators and I really would see a feature like this built-in in XF :)

    Friday, April 22, 2016 12:11 PM
  • User84670 posted

    Any chance of creating two properties in the CarouselView to disable vertical and horizontal scroll indicators? I don't like the idea of creating Custom Renderers for simple things like this.

    PS: ScrollView could have these two properties as well.

    Friday, April 22, 2016 4:45 PM
  • User84670 posted

    @AdamP, iOS Webview seems broken to me too, it's not scaling the content properly, I don't even need to rotate the device.

    It was working 100% on 2.0.1.6505 (last version that everything is stable to me).

    Friday, April 22, 2016 5:37 PM
  • User76916 posted

    @Momm i experience the scaling issue as well. Going away from the page with the webview and back again seems to correct it but obviously thats broken still. The webview is such a mess in 2.2.0 i hope they dont go to release in its current state.

    Friday, April 22, 2016 9:10 PM
  • User173875 posted

    @AdamP said: @BryanHunterXam - I mentioned this critical CarouselView bug on WinRT when -pre2 was the latest release.

    https://bugzilla.xamarin.com/show_bug.cgi?id=40502

    is there any chance this will be fixed before 2.2.0 hits stable?

    Hi Adam. This is being worked on right now.

    Sunday, April 24, 2016 12:55 AM
  • User76916 posted

    Thanks @BryanHunterXam

    Also any word on the WebView regressions in iOS. I did mention it in this thread but just put it in a bug report so at least its part of the bug tracking system. Its a severe regression in 2.2.0 that causes previously working webview's in iOS to be completely unusable. Others are experiencing the same issue.

    https://bugzilla.xamarin.com/show_bug.cgi?id=40656

    Sunday, April 24, 2016 1:02 AM
  • User173875 posted

    @DavidCASBONNE said: @BryanHunterXam Just for your informations (and to avoid duplicate bugs for people who are following this thread), I've created 5 new bugs in bugzilla :

    40630 CarouselView with ItemsSource null or empty throws Exception (v2.2.0.18-pre3) 40631 Setting CarouselView.Position throw exception (v2.2.0.18-pre3) 40632 CarouselView missed a "SelectedItem" property (v2.2.0.18-pre3) 40634 CarouselView fires (or not) "ItemSelected" or "PositionSelected" in an buggie way (v2.2.0.18-pre3) 40635 CarouselView needs either a page indicator or show part of the left and right pages (v2.2.0.18-pre3)

    CarouselView is an incredible component which really helps us to build great interfaces ! I hope you would consider these bugs and new features requested for the stable version.

    Thank you @DavidCASBONNE. Here's how we are progressing: 40630 - in progress 40631 - working on an accurate reproduction. If you could add your reproduction that would be helpful. 40632 - in progress 40634 - in progress 40635 - won't ship in 2.2.0, but we've added this to the feature backlog

    Sunday, April 24, 2016 3:20 AM
  • User173875 posted

    @AdamP said: Thanks @BryanHunterXam

    Also any word on the WebView regressions in iOS. I did mention it in this thread but just put it in a bug report so at least its part of the bug tracking system. Its a severe regression in 2.2.0 that causes previously working webview's in iOS to be completely unusable. Others are experiencing the same issue.

    https://bugzilla.xamarin.com/show_bug.cgi?id=40656

    I just spotted your bug report (thanks for filing it!). I have marked it as a regression. As we look into it tomorrow, I'll let you know where we are.

    Sunday, April 24, 2016 3:54 AM
  • User179286 posted

    @BryanHunterXam Regarding 40635 please make this only optional. Also I read that the new CarouselView has a position indicator. Please make this optional. Otherwise it cannot replace the CarouselView completely. In my App I use a full screen CarouselPage so any indicator will damage the look of my App.

    Sunday, April 24, 2016 6:45 AM
  • User173875 posted

    Hi @AdamP. The fix, PR, and merge for 40656 is ready for pre5. We re working on a set of related CarouselVIew issues that @DavidCASBONNE mentioned above. Once those are in we will push pre5.

    Sunday, April 24, 2016 9:47 PM
  • User105043 posted

    @BryanHunterXam said: Thank you @DavidCASBONNE. Here's how we are progressing: 40630 - in progress 40631 - working on an accurate reproduction. If you could add your reproduction that would be helpful. 40632 - in progress 40634 - in progress 40635 - won't ship in 2.2.0, but we've added this to the feature backlog

    Thanks @BryanHunterXam . Concerning 40631 I will send you a repro project as soon as possible.

    @BryanHunterXam said: Hi @AdamP. The fix, PR, and merge for 40656 is ready for pre5. We re working on a set of related CarouselVIew issues that @DavidCASBONNE mentioned above. Once those are in we will push pre5.

    Oh thanks for doing that for the pre5 !

    @ThomasBurkhart said: @BryanHunterXam Regarding 40635 please make this only optional. Also I read that the new CarouselView has a position indicator. Please make this optional. Otherwise it cannot replace the CarouselView completely. In my App I use a full screen CarouselPage so any indicator will damage the look of my App.

    Don't worry @ThomasBurkhart, on the feature request I have asked for 3 options including "None". You can go to the bug page and comment if you want !

    Monday, April 25, 2016 1:20 AM
  • User76916 posted

    @DavidCASBONNE @ChaseFlorell - I was impatient so I created my own View Indicators for the CarouselView, while we wait on Xamarin to implement it, if interested. https://xamarinhelp.com/carousel-view-page-indicators/

    Monday, April 25, 2016 3:25 AM
  • User3516 posted

    Hello,

    i noticed several problems in my UWP app after ugdating from 2.1.0.6526 to 2.2.0.23-pre4.

    [XamlCompilation(XamlCompilationOptions.Compile)] seems to be broken.

    The page rendering is different between the old and new verison, see the attached screenshots.

    For example i have a login screen. In the screenshots you will see that the entry fields are aligned differently and that the the two buttons below the entry fiedls are now white instead of grey.

    For the entry fields i use a custom viewcell with a grid inside:

    <ViewCell>
      <Grid Padding="15,0,15,0">
        <Grid.RowDefinitions>
          <RowDefinition Height="*"/>
        </Grid.RowDefinitions>
    
        <Grid.ColumnDefinitions>
          <ColumnDefinition Width="150"/>
          <ColumnDefinition Width="*"/>
        </Grid.ColumnDefinitions>
    
        <Label x:Name="NutzernameLabel" Grid.Row="0" Grid.Column="0" Text="{i18n:TranslateExtension Nutzername}" VerticalOptions="Center" HorizontalOptions="FillAndExpand"/>
        <local:EntryNoBorder Grid.Row="0" Grid.Column="1" x:Name="Nutzername" Keyboard="Email" Text="" Placeholder="{i18n:TranslateExtension Nutzername}" HorizontalOptions="FillAndExpand" VerticalOptions="Center"/>
      </Grid>
    </ViewCell>
    

    Next sreen contains a list and has several changes:

    The alignment of the labels in the list changed. The text color changed from white to black. The padding between the cells disappeared. The icon in the toolbar disappeared.

    This is the code for my cell:

    <?xml version="1.0" encoding="UTF-8"?>
    <ContentView xmlns="http://xamarin.com/schemas/2014/forms"
        xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" 
        x:Class="ClickLearn.Mobile.Forms.ContentViews.ThemaCellView" 
        Padding="4,1,4,1" BackgroundColor="#FFFFFF">
    
        <Grid BackgroundColor="{Binding UIFarbe}" Padding="5">
          <Grid.RowDefinitions>
            <RowDefinition Height="*"/>
          </Grid.RowDefinitions>
    
          <Grid.ColumnDefinitions>
            <ColumnDefinition Width="30"/>
            <ColumnDefinition Width="Auto"/>
            <ColumnDefinition Width="*"/>
            <ColumnDefinition Width="40"/>
          </Grid.ColumnDefinitions>
    
          <Label Grid.Row="0" Grid.Column="0" Text="{Binding Sortierung, StringFormat='{0}.'}" TextColor="#FFFFFF" XAlign="End" YAlign="Center"/>
          <Label Grid.Row="0" Grid.Column="1" Text="{Binding Bezeichnung}" TextColor="#FFFFFF" YAlign="Center" LineBreakMode="WordWrap"/>
          <Label Grid.Row="0" Grid.Column="3" Text="{Binding DispAnzFragen}" TextColor="#FFFFFF" XAlign="End" YAlign="Center"/>
        </Grid>
    </ContentView>
    

    There now is a problem with rendering of frames:

    In the old version my big buttons have a blue backgrounnd with an image and a label on it. Using the new XF version the background color is white, so the white image is no longer visible

    This is my code:

    <?xml version="1.0" encoding="utf-8" ?>
    <ContentView xmlns="http://xamarin.com/schemas/2014/forms"
        xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
        xmlns:local="clr-namespace:ClickLearn.Mobile.Forms.Extensions;assembly=ClickLearn.Mobile.Forms"
        xmlns:converters="clr-namespace:ClickLearn.Mobile.Forms.Converters;assembly=ClickLearn.Mobile.Forms"
        x:Class="ClickLearn.Mobile.Forms.ContentViews.ButtonWithImageView">
    
        <ContentView.Resources>
            <ResourceDictionary>
                <converters:ImageSourceConverter x:Key="ImageSourceConverter"/>
            </ResourceDictionary>
        </ContentView.Resources>
    
        <ContentView.GestureRecognizers>
            <TapGestureRecognizer Tapped="OnTapped"/>
        </ContentView.GestureRecognizers>
    
      <Frame x:Name="frame" WidthRequest="150" HeightRequest="150" HorizontalOptions="Center" VerticalOptions="CenterAndExpand" BackgroundColor="#1971AF" HasShadow="false" Padding="5,5,5,5">
        <StackLayout Orientation="Vertical" HorizontalOptions="FillAndExpand" VerticalOptions="FillAndExpand">
          <Image x:Name="image" Source="{Binding Source={x:Reference HiddenImageName}, Path=Text, Converter={StaticResource ImageSourceConverter}}" VerticalOptions="StartAndExpand" HeightRequest="100"/>
          <Label x:Name="textlabel" TextColor="White" HorizontalOptions="CenterAndExpand" VerticalOptions="EndAndExpand" HorizontalTextAlignment="Center" LineBreakMode="WordWrap" FontSize="Small"/>
        </StackLayout>
      </Frame>
    </ContentView>
    
    Monday, April 25, 2016 1:31 PM
  • User132171 posted

    Something new I'm seeing on pre-4 with iOS. I've got a custom user control I've created, which is just a grid with an image and some text. On iOS the SizeChanged event isn't firing when the control changes visibility, or when the control is first created.

    Monday, April 25, 2016 2:55 PM
  • User105043 posted

    @AdamP said: @DavidCASBONNE @ChaseFlorell - I was impatient so I created my own View Indicators for the CarouselView, while we wait on Xamarin to implement it, if interested. https://xamarinhelp.com/carousel-view-page-indicators/

    Thanks @AdamP , it seems to be just what I need :) I will try to implement it this evening.

    Monday, April 25, 2016 2:57 PM
  • User179286 posted

    @BryanHunterXam Has anything changed concerning the the different behaviour of OnAppearing on Android and iOS? https://forums.xamarin.com/discussion/18781/ios-and-android-different-behaviors-for-onappearing

    Monday, April 25, 2016 3:41 PM
  • User67129 posted

    Adding views to a CarouselView dynamically causes it on Android to lose track of where it is. It causes this bug: https://bugzilla.xamarin.com/show_bug.cgi?id=40513

    but also has knock on effects on other things when using it on android. Basically makes it unusable in its current state. Although I must say this control is (will be) great!

    Monday, April 25, 2016 4:01 PM
  • User120969 posted

    @ThomasBurkhart said: @BryanHunterXam Has anything changed concerning the the different behaviour of OnAppearing on Android and iOS? https://forums.xamarin.com/discussion/18781/ios-and-android-different-behaviors-for-onappearing

    I've raised a bug for these not firing correctly on Windows RT for Tabbed and MasterDetail pages

    https://bugzilla.xamarin.com/show_bug.cgi?id=40408

    Possibly a variant of that issue?

    I've ended up adding EventHandlers on my NavigationPage subclass for Popped and Pushed as this is the only reliable way to determine when pages have appeared and disappeared.

    Monday, April 25, 2016 4:44 PM
  • User84670 posted

    @AdamP said: @DavidCASBONNE @ChaseFlorell - I was impatient so I created my own View Indicators for the CarouselView, while we wait on Xamarin to implement it, if interested. https://xamarinhelp.com/carousel-view-page-indicators/

    Nice!

    As a suggestion, we could add a tapped event on each dot, so if the user taps in the 4th dot, it will move the carousel directly to the 4th item.

    This feature could be added to the Xamarin.Forms.CarouselView as well, @BryanHunterXam.

    Monday, April 25, 2016 6:52 PM
  • User76916 posted

    @Momm - I just added the tapped gesture and two-way binding on the Position, so now you can click on the indicators to jump to a page.

    @BryanHunterXam - Are we expecting -pre5 sometime this week or after Evolve?

    Monday, April 25, 2016 11:55 PM
  • User105043 posted

    @AdamP said:

    @DavidCASBONNE @ChaseFlorell - I was impatient so I created my own View Indicators for the CarouselView, while we wait on Xamarin to implement it, if interested. https://xamarinhelp.com/carousel-view-page-indicators/

    Thanks @AdamP , it seems to be just what I need :) I will try to implement it this evening.

    I have tried your indicators and the only thing I have to say is great!! It's easy to use, it works as excepted on Android and iOS. Thanks a lot!

    Are you planning to make a nuget to make it easier for everyone ?

    Tuesday, April 26, 2016 1:59 AM
  • User76916 posted

    thanks @DavidCASBONNE - because Xamarin have mentioned they will look at adding it into the core framework as per your Bugzilla Feature Request, I would rather leave it to them to do the final implementation, rather than creating a Nuget package that will be obsoleted in the future.

    However if they announce we can finally make Pull Requests to Xamarin Forms at the Evolve Keynote, I will package this up, try to make it a little more customizable and submit a pull request. They have to be announcing how we can submit a PR soon after their Build announcement of Open Source, just not sure when its coming, or if my implementation would be sufficient as I don't have any solid defaults for view indicators, which would be needed otherwise I could just see the huge amount of questions of view indicators aren't working just because they didn't specify an image :)

    Tuesday, April 26, 2016 3:21 AM
  • User74 posted

    @BryanHunterXam any eta on pre5? Im holding off of a TestFlight build for a fix to 40656.

    Tuesday, April 26, 2016 11:03 AM
  • User197084 posted

    Possible bug for CarouselView:

    I am using version Pre4 and am not having my CarouselView stretch the width of my device. I am resizing it to an aspect ratio and have it centered on the screen. On Android, the Position object is spot on and always correct to the object being shown. On iOS, the Position object is not always the correct index for what is being shown. I suspect this is due to the control not being stretched to the full width of the device.

    Has anyone else noticed the Position index being incorrect for iOS?

    Tuesday, April 26, 2016 2:23 PM
  • User197084 posted

    I lied. It is doing it on Android as well. I will double check my code but I wanted to make this aware just in case it is within the new CarouselView.

    Tuesday, April 26, 2016 4:03 PM
  • User76916 posted

    @BryanHunterXam i'm kind of eager for -pre5 with those webview fixes if there is any kind of ETA so I know what to plan for. I know its a pre-release but hoping to take 2.2.0 to production next month and hoping to get some UAT started this week.

    Tuesday, April 26, 2016 11:26 PM
  • User105043 posted

    @AdamP said: thanks @DavidCASBONNE - because Xamarin have mentioned they will look at adding it into the core framework as per your Bugzilla Feature Request, I would rather leave it to them to do the final implementation, rather than creating a Nuget package that will be obsoleted in the future.

    However if they announce we can finally make Pull Requests to Xamarin Forms at the Evolve Keynote, I will package this up, try to make it a little more customizable and submit a pull request. They have to be announcing how we can submit a PR soon after their Build announcement of Open Source, just not sure when its coming, or if my implementation would be sufficient as I don't have any solid defaults for view indicators, which would be needed otherwise I could just see the huge amount of questions of view indicators aren't working just because they didn't specify an image :)

    You're right, I will follow Evolve tomorrow and if you could make a PR it would be great ! Without build-in indicators it's sure that you would have a lot of questions ^^ Yesterday I was on the way to ask you that until I realized that gray indicators would not be really visible on gray background !

    Wednesday, April 27, 2016 1:23 AM
  • User197084 posted

    Ok there is definitely a bug with the CarouselView. I am binding to the Position object. Here is what is happening:

    I have my own indicator of which index is being shown (Ex -- 1 of 3). If I touch and just slightly move to the next item, the Position Setter gets called. Lets say I dont actually move it to the next item and stay on the original item. In that case, the Position object has the wrong index. That seems to break it from here on out. It never get corrected.

    Please fix this before you release!!

    Wednesday, April 27, 2016 1:24 AM
  • User105043 posted

    @TravyDale said: Ok there is definitely a bug with the CarouselView. I am binding to the Position object. Here is what is happening:

    I have my own indicator of which index is being shown (Ex -- 1 of 3). If I touch and just slightly move to the next item, the Position Setter gets called. Lets say I dont actually move it to the next item and stay on the original item. In that case, the Position object has the wrong index. That seems to break it from here on out. It never get corrected.

    Please fix this before you release!!

    You're right, I have submit a bug concerning this problem 4 days ago and they are working on it. (https://bugzilla.xamarin.com/show_bug.cgi?id=40634) As far as I know they would correct all bugs I have submit on CarouselView for the pre5 so it would be OK for the release!

    Wednesday, April 27, 2016 1:28 AM
  • User76916 posted

    @DavidCASBONNE - I was going to see if I could use the ASCII circle's instead of images as the default, alleviates a lot of hassles if I can get it to work and also resolves the color issue: http://www.fileformat.info/info/unicode/char/25cb/browsertest.htm

    Wednesday, April 27, 2016 1:39 AM
  • User105043 posted

    @AdamP It seems to be great ! I didn't even know ASCII has a circle character ^^ Hope you could get it to work. If I were much experienced in Xamarin development I would proposed to help you but unfortunately it's not the case for the moment...

    Wednesday, April 27, 2016 1:52 AM
  • User197084 posted

    @DavidCASBONNE said:

    @TravyDale said: Ok there is definitely a bug with the CarouselView. I am binding to the Position object. Here is what is happening:

    I have my own indicator of which index is being shown (Ex -- 1 of 3). If I touch and just slightly move to the next item, the Position Setter gets called. Lets say I dont actually move it to the next item and stay on the original item. In that case, the Position object has the wrong index. That seems to break it from here on out. It never get corrected.

    Please fix this before you release!!

    You're right, I have submit a bug concerning this problem 4 days ago and they are working on it. (https://bugzilla.xamarin.com/show_bug.cgi?id=40634) As far as I know they would correct all bugs I have submit on CarouselView for the pre5 so it would be OK for the release!

    Oh I didnt catch that. Thanks for the heads up!

    Wednesday, April 27, 2016 2:29 AM
  • User78996 posted

    Open source Xamarin.Forms

    https://github.com/xamarin/Xamarin.Forms

    Wednesday, April 27, 2016 1:41 PM
  • User74 posted

    Niiiice. :smile:

    Wednesday, April 27, 2016 2:08 PM
  • User28549 posted

    @JMarcus said: Open source Xamarin.Forms

    https://github.com/xamarin/Xamarin.Forms

    And everything else
    http://open.xamarin.com

    Wednesday, April 27, 2016 3:30 PM
  • User2148 posted

    I think there will be a lot of Pull request for XF in next weeks...

    Wednesday, April 27, 2016 3:40 PM
  • User220345 posted

    Any reason why this would stop working on 2.2.0 on Android? (worked fine up to 2.1.0)

    var wrapperLayout = new AbsoluteLayout {
        HeightRequest= EventTab.MainNavigationBarSize,
    WidthRequest = EventTab.MainNavigationBarSize,
    };
    var backImage = new Image
    {
     HeightRequest = EventTab.MainNavigationBarImageSize,
         Source = ImageSource.FromFile ("white_arrow.png")
    };
    
    // This BoxView will make for a bigger touch area, which is necessary for Windows Phone
    var box = new BoxView {
        HeightRequest = EventTab.MainNavigationBarSize,
        WidthRequest = EventTab.MainNavigationBarSize
    };
    
    wrapperLayout.Children.Add (box, new Point(0,0));
    wrapperLayout.Children.Add (backImage,new Point(15,11));
    navigationLayout.Children.Add (wrapperLayout);
    
    var tg = new TapGestureRecognizer {  
          NumberOfTapsRequired = 1 
    };
    tg.Command = new Command(async () =>
    {
        App.Navigation.PopAsync ();    // Navigation is static reference on App to the NavigationPage
     });
     wrapperLayout.GestureRecognizers.Add (tg);
    

    It does not register the tap on Emulator or real device.

    (Will create ticket in bugzilla if there is no obvious solution that I overlooked)

    Wednesday, April 27, 2016 6:58 PM
  • User33994 posted

    "CarouselView, which appeared in Xamarin.Forms 2.2.0-pre1 through pre4, has been been removed from the Xamarin.Forms package and moved into its own Nuget package. (Note: should be published later today)."

    Build is broke right now, is CarouselView accessible somewhere yet?

    Wednesday, April 27, 2016 11:50 PM
  • User76916 posted

    @LesterMeeks - not that I can see, I am also watching Nuget to wait for its release. Hopefully its soon as its getting late in the US. Though they deployed a Xamarin.Forms.Pages.Azure and -pre2 of XF about an hour ago, so some activity occurring.

    Thursday, April 28, 2016 1:14 AM
  • User89714 posted

    Is anybody else having problems deploying to iOS devices after upgrading XF to 2.2.0.39 ? I updated Xamarin.Insights and Visual Studio around the same time, but I think the issue started after doing the XF upgrade. Visual Studio gets to the Launching bit and changes color to the debugging color, but nothing happens.

    Thursday, April 28, 2016 6:01 PM
  • User181025 posted

    @JohnHardman I was having the same issue. For me, the fix was updating to Mac El Capitan as well as XCode 7.3. I also updated Xamarin Studio on the Mac.

    https://developer.xamarin.com/releases/ios/xamarin.ios9/xamarin.ios9.9/

    I'm not sure if you're using Cycle 8 Alpha or simply the newest version of XF or both.

    Thursday, April 28, 2016 6:55 PM
  • User89714 posted

    @AdrianKnight - I had the problem you hit when my Mac o/s updated. What I am getting now seems to be something different. Powering down and up my iPhone "seems" to have made a difference there, although only time will tell if that is 100% solved. I haven't powered down my iPad yet, to test whether this was the problem. I'll update here when I get a conclusion.

    Thursday, April 28, 2016 7:09 PM
  • User112992 posted

    XCC doesn't work anymore with the latest update. Seems like it is preprocessing the XAML files as before, but Xamarin must be pulling the original files in somehow because i'm getting this error again:

    MarkupExtension not found for d:DesignInstance

    Thursday, April 28, 2016 8:26 PM
  • User144019 posted

    @LesterMeeks @AdamP I am also looking the CarouselView nuget (broken build) Has anyone seen it yet? I can not find the source for it either on Github to build it myself. I can find issues related to it but a git multi-branch history search is turning up empty....

    Friday, April 29, 2016 2:07 AM
  • User76916 posted

    @RobertN.0489 - I have not found it yet. I've asked Jason for some kind of ETA, it should have been up already but with Evolve, a lot of the dev's are still in Orlando or on their way home.

    Friday, April 29, 2016 2:28 AM
  • User67129 posted

    Can I just say this: Optimizing App Performance with Xamarin.Forms with Jason Smith is a great video. Great presentation, really informative.

    Recommend it to anyone wanting to improve app performance

    Friday, April 29, 2016 12:00 PM
  • User181025 posted

    I just updated to XF 2.2.0 but wasn't able to build my Android project due to COMPILETODALVIK : UNEXPECTED TOP-LEVEL error. The fix was to set java maximum heap size to 1G. I'm not sure why I had to do that. I thought GooglePlayServices was removed from XF? I remember reading somewhere that GPS required a large heap.

    Friday, April 29, 2016 5:35 PM
  • User54846 posted

    So how many other people can no longer build due to android resource errors? I get 453 errors right now in Resource.Designer.cs

    Note: Simply rolling back to previous build -- everything works.

    Friday, April 29, 2016 9:06 PM
  • User4685 posted

    @ShawnAnderson I would guess that the issue is a 3rd party component references a older android sdk.

    Friday, April 29, 2016 10:05 PM
  • User92610 posted

    Instead of deleting old android sdks which other components may reference I added this to my build config in android.csproj for the time being to target the correct framework:

    <AndroidSdkBuildToolsVersion>23.0.3</AndroidSdkBuildToolsVersion>

    It's annoying because now i need to remember to update that but it worked. Re-download the old needed android sdk and try that maybe?

    Friday, April 29, 2016 10:08 PM
  • User54846 posted

    @MichaelRidland I created a brand new PCL based project compiled and deployed to an Android device. Then upgraded to 2.2 and it broke. Nothing else was added.

    Friday, April 29, 2016 10:17 PM
  • User51749 posted

    @ShawnAnderson - that's very interesting. I think that is probably the best way to point at the problem.

    Sunday, May 1, 2016 12:15 AM
  • User151034 posted

    where is carouselview nuget package?

    Monday, May 2, 2016 11:21 AM
  • User130379 posted

    @ChristianSvrd said: where is carouselview nuget package?

    Missing in action. I'm also stuck on prerelese version due to missing carousel view. Let's hope they will release it soon.

    Monday, May 2, 2016 1:04 PM
  • User340 posted

    38416 - ListView Sized Incorrectly After Containing Layout's Visibility is Toggled

    This actually happens now after I've updated to 2.2 from 2.1.... It really seems like every update brings bugs, I have to fix stuff that worked perfectly fine before with every Forms update.

    On the other side, I'm really happy that it's finally open-sourced, I was crying about this a long time ago :)

    Monday, May 2, 2016 5:31 PM
  • User81232 posted

    My ListView cell is broken in 2.2.0 :( It's a quite complex ListView with elements showing/hiding depending on data, but I got it working really nice in 2.0.0 (Had to skip 2.1.0 due to bug 39403).

    I'm trying to re build the UI of my ListView cell but it's just not playing nicely... Anyone else experiencing issues with layouts broken in ListView cell?

    I'll change my code to use DataTemplateSelector's and see how that goes, but I hope this won't be a recurring issue with 2.3.0+, and keen to hear if anyone else had to rebuild their ListView cells in 2.2.0.

    Tuesday, May 3, 2016 1:38 AM
  • User171749 posted

    What is the nuget called for the Carousel view??

    Tuesday, May 3, 2016 9:52 AM
  • User340 posted

    @MichaelDimoudis

    Yes, already found a bug related to showing/hiding controls on Android: https://bugzilla.xamarin.com/show_bug.cgi?id=40809

    Tuesday, May 3, 2016 10:22 AM
  • User130379 posted

    @SeanDavies.1435 said: What is the nuget called for the Carousel view??

    It will be called Xamarin.Forms.CarouselView It is not yet available on NuGet

    Tuesday, May 3, 2016 12:11 PM
  • User67129 posted

    @TheRealJasonSmith Can you upload the slides to your "Optimising App Performance with Xamarin.Forms" I've had to take screenshots from the youtube video which isn't great. Be really useful if someone could post them somewhere

    Tuesday, May 3, 2016 2:56 PM
  • User157715 posted

    Any updates on the CarouselView Nuget yet?

    Wednesday, May 4, 2016 10:59 AM
  • User28517 posted

    Where is CarouselView Nuget package?

    Wednesday, May 4, 2016 1:51 PM
  • User130379 posted

    It would be really nice if we could get CarouselView even in prerelease state instead of being stuck on prerelease forms version. I would really like to try XAML preview from 2.3 but can't update forms now.

    Wednesday, May 4, 2016 5:31 PM
  • User78421 posted

    Does anyone get this error when running on a 9.3.1 device? It happens when I attempt to click on an image that has a tapgesturerecognizer:

    System.TypeInitializationExceptionThe type initializer for 'Scollar.PetTrainingPage' threw an exception. Raw at (wrapper managed-to-native) System.Object:icallwrappermonogsharedvtconstrainedcall (intptr,intptr,intptr,intptr,intptr) at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[TStateMachine] (System.Runtime.CompilerServices.TStateMachine& stateMachine) <0x1002d9d90 + 0x001bb> in :0 at (wrapper unknown) System.Object:gsharedvtin () at (wrapper unknown) System.Object:gsharedvtout () at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (System.Runtime.CompilerServices.TStateMachine& stateMachine) <0x1002d7fa0 + 0x0005f> in :0 at (wrapper unknown) System.Object:gsharedvtin () at Scollar.MyPetsPage.petTapTapped (System.Object sender, System.EventArgs e) <0x100436050 + 0x00143> in :0 at Xamarin.Forms.TapGestureRecognizer.SendTapped (Xamarin.Forms.View sender) <0x1004b13d0 + 0x000e7> in :0 at Xamarin.Forms.Platform.iOS.EventTracker+<>cDisplayClass120.b__0 (UIKit.UITapGestureRecognizer r) <0x100a60710 + 0x00153> in :0 at UIKit.UITapGestureRecognizer+Callback.Activated (UIKit.UITapGestureRecognizer sender) <0x100af9cd0 + 0x0002b> in :0 at (wrapper managed-to-native) UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr) at UIKit.UIApplication.Main (System.String[] args, IntPtr principal, IntPtr delegate) <0x100adad50 + 0x0002b> in :0 at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) <0x100adac90 + 0x000ab> in :0 at Scollar.iOS.Application.Main (System.String[] args) <0x1000e27f0 + 0x00023> in :0

    inner stack:

    System.NullReferenceExceptionObject reference not set to an instance of an object at Scollar.PetTrainingPage..cctor () <0x1003fb910 + 0x0008c> in :0

    It also interestingly enough happens only in an Ah-Hoc build and not a debug build

    Wednesday, May 4, 2016 10:12 PM
  • User172209 posted

    Any news on the CarouselView? I'm not finding the Nuget package yet.

    Monday, May 9, 2016 12:59 PM
  • User180941 posted

    Any docs or howtos for:

    Nest platform controls to Forms layout

    Allows adding platform-specific controls (iOS, Android, and Windows) directly to a Forms layout. Note: this isn't available from PCL and requires #if defines to work from a shared project.

    ?

    Monday, May 9, 2016 6:43 PM
  • User181025 posted

    I'd also like to see documentation on how to integrate platform-specific controls into Forms.

    Monday, May 9, 2016 8:28 PM
  • User43 posted

    @AdrianKnight @JMDF: Yes, we have documentation available for native control embedding: https://developer.xamarin.com/guides/xamarin-forms/user-interface/layouts/add-platform-controls/

    Monday, May 9, 2016 8:35 PM
  • User33994 posted

    Well... just got excited to grab the new CarouselView that i saw on nuget, but now I am thinking it is not the "official" one. "CarouselView Control for Xamarin Forms".

    Monday, May 9, 2016 9:27 PM
  • User57571 posted

    Anyone having the same issue with the packages restores and updates and also no finding any package?

    I cannot restore any package neither updating it.

    Tuesday, May 10, 2016 5:16 AM
  • User31582 posted

    I cannot find the Xamarin.Forms.CarouselView nuget package anywhere.

    @BryanHunterXam quote:

    CarouselView split into separate package

    CarouselView, which appeared in Xamarin.Forms 2.2.0-pre1 through pre4, has been been removed from the Xamarin.Forms package and moved into its own Nuget package. (Note: should be published later today).

    That was 12 days ago!

    Can we expect the nuget package to be available soon?

    Thanx!

    Tuesday, May 10, 2016 8:51 AM
  • User109755 posted

    Any expected date on XF 2.3? Really looking forward to URLNavigation/DeepLink :)

    Tuesday, May 10, 2016 9:32 AM
  • User171749 posted

    Could really do with the carousel nuget being released so I can update to the stable release

    Tuesday, May 10, 2016 2:18 PM
  • User181025 posted

    Also, since CarouselView is a separate package, will we see a separate GitHub repository for that? It doesn't appear to have been open-sourced yet.

    Tuesday, May 10, 2016 4:20 PM
  • User75196 posted

    I guess I'll throw my name in the hat as well. Would be nice to hear from Xamarin when we should expect the CarouselView nuget package.

    Wednesday, May 11, 2016 5:25 PM
  • User57869 posted

    I understand that the CarouselView will be merged into the main XF and thus also open sourced when they fixed the most important bugs. See https://twitter.com/jassmith87/status/725568983617921024

    Thursday, May 12, 2016 7:36 AM
  • User161125 posted

    Sorry to break the chain but I have a problem with the Master Detail behavior with the 2.2 I have the IsGestureEnable set to false, but now even tapping on the hamburger does not open the sliding panel, is this the intended behavior?

    Any new on the CarouselView ? (didn't really want to break the chain, and really looking forward to it)

    Friday, May 13, 2016 2:05 PM
  • User217848 posted

    Hi,

    I was playing around with the Xamarin Forms Gallery project. I built the project and ran it on the android simulator. Every single page works except the one with the image. When I tap that cell I get

    "System.MissingMethodException: Method 'Looper.get_IsCurrentThread' not found"

    I tried updating to the latest stable release - no luck. I tried upgrading to the latest pre release - still no luck.

    it drives me crazy. Any idea what could cause this issue?

    tnx

    Saturday, May 14, 2016 7:36 AM
  • User2148 posted

    Hi friends. I am using XF 2.2.0 on Android. It works fine on Debug mode. If I switch to Release and try to recompile the project, I have this error. It's a XF problem or I have to contact @AllanRitchie ?

    /Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Error executing task LinkAssemblies: error XA2006: Reference to metadata item 'System.Int64 System.DateTimeOffset::ToUnixTimeMilliseconds()' (defined in 'Acr.UserDialogs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null') from 'Acr.UserDialogs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' could not be resolved. (Comanda.Droid)

    If I Try to recompile on iOS, on Debug it's OK. On Release, Ok. If I try to Archive for Publishing, I have this error

    /Users/alessandrocaliaro/Projects/comanda/iOS/MTOUCH: Error MT2002: Failed to resolve "System.Void CoreGraphics.CGRect::.ctor(System.Single,System.Single,System.Single,System.Single)" reference from "Xamarin.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065" (MT2002) (Comanda.iOS)

    Any suggestion?

    Sunday, May 15, 2016 8:35 AM
  • User125713 posted

    @AlessandroCaliaro I was having a similar issue when doing Archive for Publishing.

    What worked in my case was deleting the Release\bin and Release\obj folders.

    Sunday, May 15, 2016 11:50 PM
  • User393 posted

    @DanieleZ said: Sorry to break the chain but I have a problem with the Master Detail behavior with the 2.2 I have the IsGestureEnable set to false, but now even tapping on the hamburger does not open the sliding panel, is this the intended behavior?

    Any new on the CarouselView ? (didn't really want to break the chain, and really looking forward to it)

    I am wondering about it too. I don't see any updates on it or anything.

    Monday, May 16, 2016 12:29 AM
  • User2148 posted

    Thanks @AntoineElDaher . I try

    Monday, May 16, 2016 5:27 AM
  • User181025 posted

    @RyanWatson We haven't seen any updates by Xamarin lately.

    Thursday, May 19, 2016 9:00 PM
  • User125713 posted

    +1 CarouselView has been MIA for a month now.

    Friday, May 20, 2016 7:04 PM
  • User139758 posted

    They could just release an instable version on github and let people help fix it.... It can't be that bad??

    Sunday, May 22, 2016 11:14 PM
  • User174034 posted

    @TobiasSchulz.9796 said: They could just release an instable version on github and let people help fix it.... It can't be that bad??

    Monday, May 23, 2016 7:21 AM
  • User40225 posted

    I just downloaded ButtonXaml sample and built it. The app runs and after 5-8 seconds it exits automatically with some error that I don't understand. Attached is the debug log file that I saved from LogCat.

    Actually, my real app behaved this way. So I thought of trying a sample to see if the problem is really with my app or some configuration.

    I am using Visual Studio 2015 Community Edition. The ButtonXaml automatically downloads all the Nuget packages.

    The problem seems to be with some configuration. I am using the Android SDK that is shipped with Android Studio because the emulator is real fast. Building using API 23 SDK. Running on API 19 Emulator image.

    The app steps logging the below message: 05-23 05:41:17.683: D/Mono(10398): [0xb9bfc5b0] worker finishing

    Please help.

    Monday, May 23, 2016 9:53 AM
  • User113114 posted

    after update all pages in navigationstack trigger OnApparing/OnDissapearing when I go out and back in to my app. Totally breaking everything in my app... @TheRealJasonSmith is XF 2.2 supposed to be like this?

    Wednesday, May 25, 2016 9:41 AM
  • User8854 posted

    @JKay said: @TheRealJasonSmith Can you upload the slides to your "Optimising App Performance with Xamarin.Forms" I've had to take screenshots from the youtube video which isn't great. Be really useful if someone could post them somewhere

    There you go http://kent-boogaart.com/blog/jason-smith's-xamarin-forms-performance-tips

    Wednesday, May 25, 2016 4:50 PM
  • User113114 posted

    @BjornB said: after update all pages in navigationstack trigger OnApparing/OnDissapearing when I go out and back in to my app. Totally breaking everything in my app... @TheRealJasonSmith is XF 2.2 supposed to be like this?

    This bug only appears when using FormsAppCompatActivity, FormsActivity works just like its supposed to

    Wednesday, May 25, 2016 8:53 PM
  • User97927 posted

    @BryanHunterXam @TheRealJasonSmith Do you know any process on this failure?

    The signature-issue on google maps using the latest final xamarin.Forms and googleplayservices 29.0.0.1 http://stackoverflow.com/questions/37333220/googlesignatureverifier-signature-not-valid-message-not-using-the-google-maps-a

    https://forums.xamarin.com/discussion/67177/xamarin-forms-maps-2-2-0-31-and-googleplayservices-signature-not-valid

    And I saw there is an update on the googleplayservices to 29.0.0.2 https://www.nuget.org/packages/Xamarin.GooglePlayServices.Maps/29.0.0.2 The problem is I cannot update because here you set it directly to 29.0.0.1 https://www.nuget.org/packages/Xamarin.Forms.Maps/2.2.0.31

    I need definately it getting to work

    Thursday, May 26, 2016 6:24 AM
  • User3252 posted

    After upgrading to version 2.2 of Xamarin.Forms, I'm with the following problem:

    /Users/HomeroKzam/Projects/Components/grial-uikit-extended/samples/Grial/Droid: Error XA5209: Unzipping failed. Please download https://dl-ssl.google.com/android/repository/androidm2repositoryr29.zip and extract it to the /Users/HomeroKzam/.local/share/Xamarin/Android.Support.v4/23.3.0.0/content directory. (XA5209) (Grial.Droid) /Users/HomeroKzam/Projects/Components/grial-uikit-extended/samples/Grial/Droid: Error XA5209: Reason: /Users/HomeroKzam/.local/share/Xamarin/zips/2A3A8A6D6826EF6CC653030E7D695C41.zip is not a valid zip file (XA5209) (Grial.Droid)

    ... (more 52 errors)

    I again compile the same code, without making any changes, these errors disappear, but displays the following error: /Users/HomeroKzam/Projects/Components/grial-uikit-extended/samples/Grial/Droid/Resources/values/Style.xml(0,0): Error APT0000: Error retrieving parent for item: No resource found that matches the given name 'Theme.AppCompat.Light.NoActionBar'. (APT0000) (Grial.Droid) /Users/HomeroKzam/Projects/Components/grial-uikit-extended/samples/Grial/Droid/Resources/values-v21/Style.xml(0,0): Error APT0000: Error retrieving parent for item: No resource found that matches the given name 'Theme.AppCompat.Light.NoActionBar'. (APT0000) (Grial.Droid)

    ... (more 25 errors)

    Thanks, Homero.

    Thursday, May 26, 2016 2:06 PM
  • User149286 posted

    @AlessandroCaliaro Make sure your Target Android Version and your Target Framework both point to the same API

    Ref: http://forums.xamarin.com/discussion/comment/104444/#Comment_104444

    Thursday, May 26, 2016 11:11 PM
  • User40225 posted

    @HomeroBatistaKzam

    The following steps worked for me:

    1. Manually delete the file /Users/HomeroKzam/.local/share/Xamarin/zips/2A3A8A6D6826EF6CC653030E7D695C41.zip
    2. Then rebuild all. This rebuild all will take a lot of time because in the background androidm2repositoryr29.zip is being downloaded. Don't cancel the build. Let it complete. The build should succeed now. Or at least, you will not get any related errors.
    Friday, May 27, 2016 8:30 AM
  • User171749 posted

    Any news on the carousel view?!

    Friday, May 27, 2016 8:42 AM
  • User3252 posted

    @Gautam-Jain

    Thank you very much. Now it's working!

    Friday, May 27, 2016 10:54 AM
  • User393 posted

    @lpdavies said: Any news on the carousel view?!

    @lpdavies I got a message from support last night after sending them an email that said they are close to having a package ready.

    Crossing my fingers that it is out really soon.

    Friday, May 27, 2016 1:43 PM
  • User171749 posted

    @RyanWatson said:

    @lpdavies said: Any news on the carousel view?!

    @lpdavies I got a message from support last night after sending them an email that said they are close to having a package ready.

    Crossing my fingers that it is out really soon.

    Thanks! Much appreciated @RyanWatson

    Friday, May 27, 2016 1:44 PM
  • User173875 posted

    Tonight Xamarin.Forms 2.2.0-hotfix1 and Xamarin.Forms 2.3.0-pre3 both shipped.

    The Nuget for Xamarin.Forms.CarouselView 2.3.0-pre1 also shipped. CarouselView is ganged to Xamarin.Forms 2.3.0 (pre3 or greater). Please note that the CarouselView package will not work with Xamarin Forms 2.2.0 versions. Apologies for that, and also apologies for the long, unexpected delay on getting it out the door.

    Saturday, May 28, 2016 1:56 AM
  • User340 posted

    Bugzilla doesn't allow me to see:

    For:

    40844 - [Android] Forms Android app gets stuck with GC bridge calls when using current beta branch of Xamarin.Android/Mono Runtime

    Error:

    You are not authorized to access bug #40844.

    Sunday, May 29, 2016 10:43 AM
  • User33877 posted

    O just updated Xamarin.Forms to 2.2.0.43 and am getting this error when trying to build for iOS...

    Error MT2002: Failed to resolve "System.Void CoreGraphics.CGSize::.ctor(System.Single,System.Single)" reference from "Xamarin.iOS

    Monday, May 30, 2016 12:19 AM
  • User84300 posted

    I am also getting this error ater upgrading.

    Error MT2002: Failed to resolve "System.Void CoreGraphics.CGSize::.ctor(System.Single,System.Single)" reference from "Xamarin.iOS

    Monday, May 30, 2016 2:00 AM
  • User229506 posted

    @DonMesserli.1843 said: O just updated Xamarin.Forms to 2.2.0.43 and am getting this error when trying to build for iOS...

    Error MT2002: Failed to resolve "System.Void CoreGraphics.CGSize::.ctor(System.Single,System.Single)" reference from "Xamarin.iOS

    @TimBarton said: I am also getting this error ater upgrading.

    Error MT2002: Failed to resolve "System.Void CoreGraphics.CGSize::.ctor(System.Single,System.Single)" reference from "Xamarin.iOS

    Yes, this is the common issue we're facing right now after upgrading to XF 2.2.0.43.. Any idea when will this be fixed?? Luckily, my project whose I am updating the XF version is just a demo project, imagine if the one updated is the live app source code, it will be such a pain (this is where source control or source code backup mechanism plays an important role I believe, so we can easily roll it back to the previous version if the build fails because of XF update)..

    Monday, May 30, 2016 7:15 AM
  • User51906 posted

    @DonMesserli.1843 @TimBarton @JuanWahyudihardjo This is more likely a problem with the Linker. Try to set it to No Linking, this should fix it. At least that was a problem on my end.

    Monday, May 30, 2016 8:02 AM
  • User229506 posted

    @RaphaelSchindler said: @DonMesserli.1843 @TimBarton @JuanWahyudihardjo This is more likely a problem with the Linker. Try to set it to No Linking, this should fix it. At least that was a problem on my end.

    @RaphaelSchindler Sorry, just to make sure I do the correct step, how can I set it to No Linking?? is it in my Xamarin.IOS project options -> iOS Build -> Linker Behavior -> then we select don't link??

    Thanks in advance

    Monday, May 30, 2016 8:11 AM
  • User51906 posted

    @JuanWahyudihardjo Yes, it's in the options from you Xamarin.iOS options. Right click on solution -> Options -> iOS Build -> Linker behavior to Don't link.

    I get this error on all 3 channels at the moment. So the bug is in Stable/Beta/Alpha release. At least for me

    Monday, May 30, 2016 8:14 AM
  • User229506 posted

    @RaphaelSchindler said: @JuanWahyudihardjo Yes, it's in the options from you Xamarin.iOS options. Right click on solution -> Options -> iOS Build -> Linker behavior to Don't link.

    I get this error on all 3 channels at the moment. So the bug is in Stable/Beta/Alpha release. At least for me

    @RaphaelSchindler after setting it to don't link, it works, but i got many warnings, something like this : "Native Linking warning : object file..... was built for newer iOS version than being linked", is it ok?? Can u also help me to understand what this linking behavior stuff means?:smile:

    I saw there are 3 options : Don't link, Link with frameworks SDK and Link All.. and I've also checked the same way in my xamarin.android project, for the linker behavior, it's no link by default..

    Monday, May 30, 2016 8:26 AM
  • User52818 posted

    I would like to see the linker to work properly. What's the use of it, if we can never be sure that our code is working. I have it turned on because otherwise I do get errors.

    Monday, May 30, 2016 8:34 AM
  • User51906 posted

    @JuanWahyudihardjo Yeah the warnings are ignorable. Maybe you just don't have the newest XCode and iOS Version on your Mac or something like that, I'm not sure though :/

    So the linker basically strips out not needed API functions in the used SDK's. Which results in smaller builds for the stores and devices. That part is actually a pretty rad idea, but it must be extremly hard to get this to work properly. That's why I never used Link all. Your app could become unusable if the Linker decides that a used part of the SDK is not used and strips it out. So Linking the Framework SDK's only can work, but right now the linker is just broken^^

    Monday, May 30, 2016 8:34 AM
  • User229506 posted

    @RaphaelSchindler > @RaphaelSchindler said:

    @JuanWahyudihardjo Yeah the warnings are ignorable. Maybe you just don't have the newest XCode and iOS Version on your Mac or something like that, I'm not sure though :/

    So the linker basically strips out not needed API functions in the used SDK's. Which results in smaller builds for the stores and devices. That part is actually a pretty rad idea, but it must be extremly hard to get this to work properly. That's why I never used Link all. Your app could become unusable if the Linker decides that a used part of the SDK is not used and strips it out. So Linking the Framework SDK's only can work, but right now the linker is just broken^^

    I'm pretty sure that I got the latest version of OS X(10.11.5 El Capitan) and XCode (7.3.1).. but i'm just curious, by setting it to no linking, could it bring impact later in runtime when we run our apps?? I mean it could be some DLL missing or something resulting in error..

    Monday, May 30, 2016 8:43 AM
  • User51906 posted

    @JuanWahyudihardjo Hmm ok then I don't know what his problem is^^ No, actually setting it to No Link means that everything is in your app. Even unneeded code, which blows up the app size. If you use Linking then it could be possible that some DLL's could be missing.

    Monday, May 30, 2016 8:46 AM
  • User229506 posted

    The case was solved in xamarin studio on my Mac, now the problem comes on my Visual Studio 2015 Community, I just made a new test project just to test to connect to my macbook as build host.

    When i update the xamarin forms package to version 2.2.0.43, I straight run my iOS "Welcome to xamarin forms" project on VS 2015 to my testing iphone device, It gives following exception on running base.FinishedLaunching(app, options)

    "Attempting to JIT compile method 'Xamarin.Forms.Platform.iOS.SizeExtensions"..

    Edit : it also happens while trying to run from Mac

    A very serious question , does xamarin really do a unit and regression testing prior to release of a new version or subversion??

    Walao,, if this is the case, then we should always make a backup first of our apps' source code before upgrading to the latest XF..

    Monday, May 30, 2016 9:30 AM
  • User76049 posted

    @Juan.Wahyudihardjo

    Seeing the exact same issue after upgrading to Forms 2.2.0.43 with iOS projects. Have to roll back to the previous version on two apps which is a PITA :neutral: Not using linking either as I don't usually for debugging.

    Monday, May 30, 2016 12:30 PM
  • User125713 posted

    @BryanHunterXam is there a bug tracking this issue with compiling the newly released XF2.2.0.43? Can we get an ETA on a fix for the hotfix?

    Monday, May 30, 2016 4:49 PM
  • User173875 posted

    Thanks for all of your reports. There was a problem with the build/packaging. The issues are now fixed. Please update to 2.2.0.45

    What happened? One of our build machines was set to beta channel and it was 'picked' by our CI to build the Nuget packages. This caused the iOS API mismatch.

    Why didn't tests catch this? Our UI tests ran on an OSX machine that was correctly set to the stable channel. We are discussing mistake-proofing guards to prevent mismatches in the future.

    Monday, May 30, 2016 5:23 PM
  • User76049 posted

    @BryanHunterXam

    Thanks for the update.

    Monday, May 30, 2016 6:09 PM
  • User150855 posted

    Just if all at Xamarin missed some earlier post about TapGestureRecognizer...

    It is still broken on Android, even in 2.3.0-pre3. It is working well if used with Image, but not if used with ContentView, Grid (working in 2.1.x), Label or BoxView (I tested only).

    I am using it a lot in my custom controls, so now I must go back to 2.1 or my app will not respond on any tap.

    Tuesday, May 31, 2016 6:14 AM
  • User150855 posted

    And another problem with 2.2.0.45 on WP8.1

    I have ListView with custom controls as ViewCells, where I have some buttons with TapGestureRecognizer. I have disabled standard selection in list by set SelectedItem = null on "ItemSelected" handler and it always work in previous releases of XF in Android and WP8.1.

    But now in 2.2.0.45 on WP listview selects (and only selects, never deselects on second tap) items in backgraoud while tapping on buttons and change colors of my labels in items contentview.

    What interesting SelectedItem is always null, ItemSelected handler is not invoked, seems like only internally list change item visuality to selected state.

    To solving this wrong behaviour I had to add forced set SelectedItem to item was tapped and back to null;

    Tuesday, May 31, 2016 8:20 AM
  • User76049 posted

    iOS AOT startup issue seems to be resolved now in 2.2.0.45.

    Tuesday, May 31, 2016 10:23 AM
  • User393 posted

    @CezaryGrabski said: Just if all at Xamarin missed some earlier post about TapGestureRecognizer...

    It is still broken on Android, even in 2.3.0-pre3. It is working well if used with Image, but not if used with ContentView, Grid (working in 2.1.x), Label or BoxView (I tested only).

    I am using it a lot in my custom controls, so now I must go back to 2.1 or my app will not respond on any tap.

    @CezaryGrabski I have TapGestureRecognizer working with a Grid in 2.2.0 (upgrading to 2.30 this morning though). The one issue I had is that I had frames and labels with background colors set that were interfering. I have my TGR on the my frame that is in the grid.

    Tuesday, May 31, 2016 12:42 PM
  • User212707 posted

    Hi,

    After updating XForms 2.2.0.45 I have iOS release issue too.

    MTOUCH: error MT2002: Failed to resolve "System.Void CoreGraphics.CGRect::.ctor(System.Single,System.Single,System.Single,System.Single)" reference from "Xamarin.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065" Task "MTouch" execution -- FAILED

    I am getting this error in release mode. On some threads they said ACR.UserDialogs can cause this. So I updated it to 5.2.2 also.

    Any suggestion? Thanks Edebali.

    Tuesday, May 31, 2016 2:50 PM
  • User4513 posted

    This (and previous) stable releases do not match the open source repository. For example. InvalidationTrigger has an access modifier of Public in the open source repository, but is Internal in the NuGet package. Please could we get everything in sync? Better still, please could you remove all the Internal modifiers altogether. Whenever I try to extend XF and use the existing classes I'm continually coming across access issues due to classes, properties and methods being marked internal, and then have to use reflection to access them. Not exactly conducive to either fixing bugs or extending functionality!!

    Tuesday, May 31, 2016 6:56 PM
  • User2496 posted

    Hi @DavidAllen are sure you are checking the right branch/tag on the public repo?

    For example on 2.2 InvalidationTrigger is still internal ... https://github.com/xamarin/Xamarin.Forms/blob/release-2.2.0-hf1/Xamarin.Forms.Core/InvalidationTrigger.cs

    The master branch doesn't reflect the current public nugets, for that you have to check the branches 2.2 and 2.3, or the tags.

    We are working on removing most of the internals, some changes have landed others are still being reviewed.

    Wednesday, June 1, 2016 9:32 AM
  • User4513 posted

    Thanks Rui. I was looking at the master branch, my mistake. Thanks for working on removing the internal declarations, it will make life much easier when we try to extend forms.

    Wednesday, June 1, 2016 1:24 PM
  • User97927 posted

    @FokkeVermeulen said: @BryanHunterXam @TheRealJasonSmith Do you know any process on this failure?

    The signature-issue on google maps using the latest final xamarin.Forms and googleplayservices 29.0.0.1 http://stackoverflow.com/questions/37333220/googlesignatureverifier-signature-not-valid-message-not-using-the-google-maps-a

    https://forums.xamarin.com/discussion/67177/xamarin-forms-maps-2-2-0-31-and-googleplayservices-signature-not-valid

    And I saw there is an update on the googleplayservices to 29.0.0.2 https://www.nuget.org/packages/Xamarin.GooglePlayServices.Maps/29.0.0.2 The problem is I cannot update because here you set it directly to 29.0.0.1 https://www.nuget.org/packages/Xamarin.Forms.Maps/2.2.0.31

    I need definately it getting to work

    @rmarinho that one still occurs. Do you have a fix for that?

    Thursday, June 2, 2016 7:58 AM
  • User164182 posted

    In our Android (AppCompat) app we are getting a ArgumentException: 'jobject' must not be IntPtr.Zero when changing the icon of a ToolbarItem at runtime. Forms version is 2.2.0.45

    I attached a test project. Switch to 'Page 3' and than back to 'Page 1' and click on the toggle button to get the exception. A fix would be much appreciated!

    System.ArgumentException: 'jobject' must not be IntPtr.Zero. Parameter name: jobject at Android.Runtime.JNIEnv.CallObjectMethod (IntPtr jobject, IntPtr jmethod) [0x00010] in /Users/builder/data/lanes/3236/ee215fc9/source/monodroid/src/Mono.Android/src/Runtime/JNIEnv.g.cs:170 at Android.Views.View.get_Context () [0x0002d] in /Users/builder/data/lanes/3236/ee215fc9/source/monodroid/src/Mono.Android/platforms/android-23/src/generated/Android.Views.View.cs:4891 at Xamarin.Forms.Platform.Android.AppCompat.NavigationPageRenderer.UpdateMenu () [0x00006] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\AppCompat\NavigationPageRenderer.cs:643 at Xamarin.Forms.Platform.Android.AppCompat.NavigationPageRenderer.HandleToolbarItemPropertyChanged (System.Object sender, System.ComponentModel.PropertyChangedEventArgs e) [0x00045] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\AppCompat\NavigationPageRenderer.cs:387 at (wrapper delegate-invoke) <Module>:invoke_void_object_PropertyChangedEventArgs (object,System.ComponentModel.PropertyChangedEventArgs) at Xamarin.Forms.BindableObject.OnPropertyChanged (System.String propertyName) [0x0000a] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\BindableObject.cs:137 at Xamarin.Forms.Element.OnPropertyChanged (System.String propertyName) [0x00000] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\Element.cs:362 at Xamarin.Forms.BindableObject.SetValueActual (Xamarin.Forms.BindableProperty property, Xamarin.Forms.BindablePropertyContext context, System.Object value, Boolean currentlyApplying, SetValueFlags attributes, Boolean silent) [0x000f4] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\BindableObject.cs:581 at Xamarin.Forms.BindableObject.SetValueCore (Xamarin.Forms.BindableProperty property, System.Object value, SetValueFlags attributes, SetValuePrivateFlags privateAttributes) [0x0014b] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\BindableObject.cs:378 at Xamarin.Forms.BindableObject.SetValue (Xamarin.Forms.BindableProperty property, System.Object value, Boolean fromStyle, Boolean checkAccess) [0x0005f] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\BindableObject.cs:531 at Xamarin.Forms.BindableObject.SetValue (Xamarin.Forms.BindableProperty property, System.Object value) [0x00000] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\BindableObject.cs:83 at Xamarin.Forms.MenuItem.set_Icon (Xamarin.Forms.FileImageSource value) [0x00000] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\MenuItem.cs:37 at TestDroid.Page1.ToggleClicked (System.Object sender, System.EventArgs e) [0x0003a] in /Users/quadcore/Projects/TestDroid/Page1.xaml.cs:21 at Xamarin.Forms.Button.Xamarin.Forms.IButtonController.SendClicked () [0x00020] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Core\Button.cs:122 at Xamarin.Forms.Platform.Android.AppCompat.ButtonRenderer+ButtonClickListener.OnClick (Android.Views.View v) [0x0000b] in C:\BuildAgent2\work\aad494dc9bc9783\Xamarin.Forms.Platform.Android\AppCompat\ButtonRenderer.cs:274 at Android.Views.View+IOnClickListenerInvoker.n_OnClick_Landroid_view_View_ (IntPtr jnienv, IntPtr native__this, IntPtr native_v) [0x00011] in /Users/builder/data/lanes/3236/ee215fc9/source/monodroid/src/Mono.Android/platforms/android-23/src/generated/Android.Views.View.cs:1903 at (wrapper dynamic-method) System.Object:041a8b72-2872-4ad9-896f-b5245b1c2421 (intptr,intptr,intptr)

    Friday, June 3, 2016 10:52 AM
  • User1407 posted

    Already getting the Error MT2002 after updating to Form 2.2.0.45 : Failed to resolve "System.Void CoreGraphics.CGRect::.ctor(System.Single,System.Single,System.Single,System.Single)" reference from "Xamarin.iOS, Version=0.0.0.0, Culture=neutral, PublicKeyToken=84e04ff9cfb79065" (MT2002) (Dassault.MyFalcon.iOS).

    When setting the link to "Don't link" I am getting this Error MT4134: Your application is using the 'HealthKitUI' framework, which isn't included in the iOS SDK you're using to build your app (this framework was introduced in iOS 9.3, while you're building with the iOS 9.2 SDK.) This configuration is only supported with the legacy registrar (pass --registrar:legacy as an additional mtouch argument in your project's iOS Build option to select). Alternatively select a newer SDK in your app's iOS Build options. (MT4134) (Dassault.MyFalcon.iOS).:smile:

    Please note that my app is not using HealthKitUI is any way.

    Please note also that I am working on a project for a really important customer and I am unable to build the project. Please Xamarin don't publish UPDATES that you have not tested

    Friday, June 3, 2016 11:28 AM
  • User164182 posted

    @PawelTkti said: .

    @PawelTkti said: I have problem. After installation the newest version (pre2) all properties defined in styles override my properties in the controls. For example:

    Style:

    <Style x:Key="MainButtonStyle" TargetType="custom:MyButton">
      <Setter Property="BackgroundColor" Value="Red"/>
      <Setter Property="TextColor" Value="White"/>
      <Setter Property="BorderRadius" Value="0"/>
      <Setter Property="BorderWidth" Value="0"/>
    </Style>
    

    Button:

     <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    In app BackgroundColor is Red (as Style), and should be Black.

    Is it bug? Or it can be changed in the code?

    @TheRealJasonSmith said: Does it happen with every control or just some?

    @PawelTkti said:

    @TheRealJasonSmith said: Does it happen with every control or just some?

    Entry - bad Label - bad StackLayout - good BoxView - good

    Button is strange... If I'm using Custom Renderer, all properties defined in styles override my properties. If I'm not using CR everything is ok.

    Button is black:

    <Button Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    Button is not black (because in styles property is red):

    <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />`
    

    Does it work in the latest version Xamarin Forms?

    This is from April 21 and it's still not working in 2.2.0.45 and 2.3-pre3!

    A workaround is to put the property before the style (yes, I'm serious): <Button Text="Need help" BackgroundColor="Black" Style="{StaticResource MainButtonStyle}" />

    Please fix this!

    Wednesday, June 8, 2016 10:34 AM
  • User92610 posted

    TapGestureRecognizer is still broken for me on android. Has anyone found a solution? I have it on an absolute layout. Worked fine before 2.2.

    Has anyone found a work around?

    Wednesday, June 8, 2016 5:47 PM
  • User92610 posted

    work around for me was putting a boxview in the absolute layout and adding the gesturerecognizer to it

    Wednesday, June 8, 2016 9:54 PM
  • User164182 posted

    Usually when the keyboard appears the entry control gets moved up so it's still visible. This does not work on Android (but iOS) when using translation (TranslateTo, TranslationX/Y). See the attached test project. Forms version is 2.2.0.45.

    Thursday, June 9, 2016 8:06 AM
  • User193082 posted

    It seems that the Master Detail Page's 'IsGestureEnabled' property changed behavior. I was using XF 2.1.0.6529 before I updated to 2.2.0.45.

    Before it was just enabling/disabling the swipe feature of the Master Detail Page to be presented or not, but now when I set the 'IsGestureEnabled' to false, it doesn't let me open the drawer even by clicking the Burger icon.

    Can anyone confirm this?

    I dont want swipe gesture to be enabled in android since scrolling Up or Down the Master Page seems to have conflicting gesture with left or right.

    Friday, June 10, 2016 4:03 AM
  • User233429 posted

    @FokkeVermeulen said:

    @FokkeVermeulen said: @BryanHunterXam @TheRealJasonSmith Do you know any process on this failure?

    The signature-issue on google maps using the latest final xamarin.Forms and googleplayservices 29.0.0.1 http://stackoverflow.com/questions/37333220/googlesignatureverifier-signature-not-valid-message-not-using-the-google-maps-a

    https://forums.xamarin.com/discussion/67177/xamarin-forms-maps-2-2-0-31-and-googleplayservices-signature-not-valid

    And I saw there is an update on the googleplayservices to 29.0.0.2 https://www.nuget.org/packages/Xamarin.GooglePlayServices.Maps/29.0.0.2 The problem is I cannot update because here you set it directly to 29.0.0.1 https://www.nuget.org/packages/Xamarin.Forms.Maps/2.2.0.31

    I need definately it getting to work

    @rmarinho that one still occurs. Do you have a fix for that?

    @rmarinho I've the same problem here...any Info on when this will be fixed? I can't move on working on the project if the app just keeps crashing. :(

    Thursday, June 16, 2016 7:55 AM
  • User2496 posted

    @FokkeVermeulen @MarkusStoebe i can't reproduce the issue, can you please submit a bug in bugzilla with a repo and point it to me so i can take a look.

    Thanks.

    Thursday, June 16, 2016 3:03 PM
  • User233429 posted

    I created Bug 41926 and I hope I entered all info necessary. If not just let me know...

    @rmarinho said: @FokkeVermeulen @MarkusStoebe i can't reproduce the issue, can you please submit a bug in bugzilla with a repo and point it to me so i can take a look.

    Thanks.

    Friday, June 17, 2016 10:11 AM
  • User166441 posted

    @DarkwingDuck said:

    @PawelTkti said: .

    @PawelTkti said: I have problem. After installation the newest version (pre2) all properties defined in styles override my properties in the controls. For example:

    Style:

    <Style x:Key="MainButtonStyle" TargetType="custom:MyButton">
        <Setter Property="BackgroundColor" Value="Red"/>
        <Setter Property="TextColor" Value="White"/>
        <Setter Property="BorderRadius" Value="0"/>
        <Setter Property="BorderWidth" Value="0"/>
    </Style>
    

    Button:

     <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    In app BackgroundColor is Red (as Style), and should be Black.

    Is it bug? Or it can be changed in the code?

    @TheRealJasonSmith said: Does it happen with every control or just some?

    @PawelTkti said:

    @TheRealJasonSmith said: Does it happen with every control or just some?

    Entry - bad Label - bad StackLayout - good BoxView - good

    Button is strange... If I'm using Custom Renderer, all properties defined in styles override my properties. If I'm not using CR everything is ok.

    Button is black:

    <Button Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />
    

    Button is not black (because in styles property is red):

    <custom:MyButton Text="Need help" Style="{StaticResource MainButtonStyle}"  BackgroundColor="Black"  />`
    

    Does it work in the latest version Xamarin Forms?

    This is from April 21 and it's still not working in 2.2.0.45 and 2.3-pre3!

    A workaround is to put the property before the style (yes, I'm serious): <Button Text="Need help" BackgroundColor="Black" Style="{StaticResource MainButtonStyle}" />

    Please fix this!

    THANKS! It's working! Xamarin please...

    Thursday, June 23, 2016 5:01 PM
  • User120163 posted

    @Matthew.4307 said:

    @DerekPapworth.4183 said: @TheRealJasonSmith - Following on from my earlier post in here on issue with contextmenu not firing in ListView in Windows UWP I've done some more investigation and it appears the Cell in the ListView is not obeying the FillAndExpand or StartAndExpand in ListView and hence the contextmenu is only being triggered if tapped within the non-expanded cell limits. To check this I added background colour to my cell and as you can in attached captured pic when I tap (right click in this case as Windows UWP) on 4th cell for instance the highlight of the listview item covers complete width but cell doesn't. However same code exactly works fine in iOS, Android, Windows Phone 8.1 Silverlight but in the case of Windows UWP or Windows 8.1 I get this result. Apart from not being right, it means contextmenu won't work unless you tap inside the cell rather than just listitem which when no background colour used is difficult to tell. Any clues or is this a bug?

    p.s. Just to confirm as don't have screenshots to hand, in iOS, Android and Windows Phone with same aqua background set the colour covers complete width in all listitems with exactly same code.

    There was a similar sort of issue in Windows RT where the content of a List View header template wouldn't expand even though it was set to, my workaround was WidthRequest = 5000. Though this is no longer an issue in 2.2pre 2.

    As a workaround you should be able to set a really wide WidthRequest and it'll just go as wide as the screen is.

    Thanks for the workaround @Matthew.4307 !

    I'm actually using Xamarin.Forms 2.3.0 and I had to set the WidthRequest of a View inside a Frame that is also within the row to FillAndExpand full Width. I filed a bug so Xamarin dev team can keep track of this issue. I started experiencing this behavior in Xamarin.Forms 2.2.0.45. Apparently the ListView shows fine in XF 2.0.1.6505 Here's the bugzilla: https://bugzilla.xamarin.com/show_bug.cgi?id=42132

    Hope this helps you identifying the problem.

    Best Regards.

    Thursday, June 23, 2016 9:21 PM
  • User103333 posted

    Hey folks, I'm having a werid issue with the recent updates. I'm Using Visual Studio Enterprise 2015 and XF 2.3

    I'm using Service Stack, and everything works cool but here's when the story goes werid.

    I have a REST API with service stack, and the app is the client, but when I request a method, no matter if its using POST or GET the API response is correct but when it enters the app it goes to empty with a custom property type. I know it is correct because logs on the API says so and I know it reaches the app using WireShark.

    If I run the same code (client methods) in a windows forms it works as spected but running it on Xamarin.Forms it does not.

    the issue happens with a custom type I created but when I use the custom type

    public class DataProperty
    {
        protected string base64Value;
    
        public DataProperty();
    
        public string Value { get; }
    
        public byte[] Get();
        public DataProperty Set(byte[] data);
    
        public static implicit operator DataProperty(byte[] data);
        public static implicit operator byte[] (DataProperty PropertyValue);
    }
    
    public class DataProperty<T> : DataProperty
    {
        public DataProperty();
    
        public DataProperty<T> Set(byte[] data);
    
        public static implicit operator DataProperty<T>(byte[] data);
        public static implicit operator byte[] (DataProperty<T> PropertyValue);
    }
    

    Service stack json returns:

    [0:] { "SessionToken": { "Value": "WFE1Au5DoIb0sEttlD3h08Xg+E+KwrZ5tFusJqP1TsSY6D6PACjcBAiub+ydX84Wa95Gu318ziDXssUnwe0fWE0L/0A6h5IcLEYk8xGxKdW3ooehjrOR/7KwEypZRcmVI6oKX75id21npQDJZP8Y4U18gBeJuuKjpckeL8b54U8=" }, "Id": { "Value": "" }, "AId": { "Value": "" }, "Iden": { "Value": "" }, "ACID": 13, "ResponseStatus": null }

    //SessionToken is a DataProperty //Id is DataProperty<long> //AId is DataProperty<double> //Iden is DataProperty<string> //ACID is long //ResponseStatus is a service stack property not filled. As I said, if I run exactly the same code on a PCL+Windows Forms(or even console) app it works correctly but running it on PCL+Xamarin.Forms it doesn't (using emulator or phisical phone)

    Tried XF 2.1,2.2, 2.3.

    Any ideas?

    Friday, June 24, 2016 11:35 PM
  • User88504 posted

    Hi, I have an issue with page lifecycle on Android. I am currently using AppCompatActivity and Xamarin.Forms 2.2.0.31. For example, when I move to Page2 from Page1, XF called OnAppearing() for Page2 and OnDisappearing() for Page1. When I click "Back" button XF triggers Page1.OnAppearing() and Page2.OnDisappearing(). And it's fine. But, in another case, when I go to Page2 and move application to background (Page2.OnDisappearing() called) and then move application to foreground, XF will call Page2.OnAppearing() and Page1.OnAppearing() (this is Incorrect behaviour). After that, when I return to Page1, Page2.OnDisappearing() is called, but nothing more, and I don't know when Page1 is visible (it's also Incorrect behaviour).

    The same issues in BugZilla: https://bugzilla.xamarin.com/showbug.cgi?id=41322, https://bugzilla.xamarin.com/showbug.cgi?id=40722

    Do you have any ideas how to fix this?

    Thursday, June 30, 2016 11:45 AM
  • User189201 posted

    @BryanHunterXam said: Thanks for all of your reports. There was a problem with the build/packaging. The issues are now fixed. Please update to 2.2.0.45

    What happened? One of our build machines was set to beta channel and it was 'picked' by our CI to build the Nuget packages. This caused the iOS API mismatch.

    Why didn't tests catch this? Our UI tests ran on an OSX machine that was correctly set to the stable channel. We are discussing mistake-proofing guards to prevent mismatches in the future.

    FYI - This bug is back in the latest build (2.3.1.113-pre3)

    Thursday, July 21, 2016 5:16 AM
  • User173875 posted

    Hi @LeoReading! Regarding your comment...

    FYI - This bug is back in the latest build (2.3.1.113-pre3)

    What made that "bad build" bad for 2.2.0 was the unintentional, surprise requirement to upgrade Xamarin to Cycle 7 after multiple pre-releases of 2.2.0 had been tied to Cycle 6.

    With 2.3.1 it's a different story. The dependency on Cycle 7 for 2.3.1 is intentional and was announced in the release notes (under "important notes") :

    When upgrading to Xamarin.Forms 2.3.1 (and future releases), users should upgrade their Xamarin installation to Cycle 7.

    We build each new Forms versions against the current stable platform version.

    Thursday, July 21, 2016 4:59 PM