LinkAssemblies errors after upgrade to Xamarin.Forms v3.0

20 posts, 1 answers
  1. Cory
    Cory avatar
    4 posts
    Member since:
    Aug 2011

    Posted 10 May 2018 Link to this post

    Error       The "LinkAssemblies" task failed unexpectedly.
    Mono.Linker.MarkException: Error processing method: 'System.Void Telerik.XamarinForms.Input.RadNumericInputResourceDictionary::InitializeComponent()' in assembly: 'Telerik.XamarinForms.Input.dll' ---> Mono.Cecil.ResolutionException: Failed to resolve System.Func`2<System.String,System.String> Xamarin.Forms.Internals.ResourceLoader::get_ResourceProvider()
       at Mono.Linker.Steps.MarkStep.HandleUnresolvedMethod(MethodReference reference)
       at Mono.Linker.Steps.MarkStep.MarkMethod(MethodReference reference)
       at Mono.Linker.Steps.MarkStep.MarkInstruction(Instruction instruction)
       at Mono.Linker.Steps.MarkStep.MarkMethodBody(MethodBody body)
       at Mono.Linker.Steps.MarkStep.ProcessMethod(MethodDefinition method)
       at Mono.Linker.Steps.MarkStep.ProcessQueue()
       --- End of inner exception stack trace ---
       at Mono.Linker.Steps.MarkStep.ProcessQueue()
       at Mono.Linker.Steps.MarkStep.ProcessPrimaryQueue()
       at Mono.Linker.Steps.MarkStep.Process()
       at Mono.Linker.Steps.MarkStep.Process(LinkContext context)
       at Mono.Linker.Pipeline.Process(LinkContext context)
       at MonoDroid.Tuner.Linker.Process(LinkerOptions options, ILogger logger, LinkContext& context)
       at Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)
       at Xamarin.Android.Tasks.LinkAssemblies.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() App7.Android    C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets 1812   

     

    Telerik.UI.for.Xamarin version 2018.1.405.2

    Platform: Android

     

  2. Dirk
    Dirk avatar
    2 posts
    Member since:
    Nov 2017

    Posted 11 May 2018 Link to this post

    +1
  3. Namysław
    Namysław avatar
    42 posts
    Member since:
    Jul 2017

    Posted 11 May 2018 Link to this post

    Same for me - my iOS app is not building starting from any *3.x* version.
    It's building only up to: *2.5.1.527436*.

    Telerik version - newest available - 2018.1.405.2.

    Error:
    C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(791,3): error : Can't resolve the reference 'System.Func`2<System.String,System.String> Xamarin.Forms.Internals.ResourceLoader::get_ResourceProvider()', referenced from the method 'System.Void Telerik.XamarinForms.Input.MaskedInputResources::InitializeComponent()' in 'Xamarin.Forms.Core, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null'.
  4. Yana
    Admin
    Yana avatar
    4865 posts

    Posted 15 May 2018 Link to this post

    Hello Namysław,

    We have received several reports about this issue with the resource loading in Xamarin.Forms 3.0 and we're looking into it with high priority.  You could follow the feedback item in our public portal here: https://feedback.telerik.com/Project/168/Feedback/Details/249296-linkassemblies-build-errors-with-xamarin-forms-3-0

    Hopefully we will manage to provide a fix for the upcoming R2 2018 release scheduled for May 16, please give it a try it then.

    Regards,
    Yana
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  5. Namysław
    Namysław avatar
    42 posts
    Member since:
    Jul 2017

    Posted 15 May 2018 in reply to Yana Link to this post

    Hello Yana,
    Yes, I'll try to build my app tomorrow, once there will be new release of Telerik for Xamarin.Forms available on nuget, and I'll give feedback of it.

    Thanks a lot for quick response!
  6. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 15 May 2018 Link to this post

    Hello Cory and Namyslaw,

    I can confirm the issue was identified and repaired, the fix will be in the 2018 R2 release Yana mentioned. If you have any additional problem with using Xamarin.Forms version 2.5 (or later), please let us know and share any exception or stack trace you may have.

    Thank you for your patience and understanding in this matter.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  7. Hari
    Hari avatar
    1 posts
    Member since:
    Nov 2017

    Posted 16 May 2018 Link to this post

    1+
  8. Dirk
    Dirk avatar
    2 posts
    Member since:
    Nov 2017

    Posted 16 May 2018 Link to this post

    I can confirm the issue wasn´t repaired!

    Telerik - 2018.2.516.2
    Xamarin - 3.0.0.482510

  9. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 16 May 2018 Link to this post

    Hi Dirk,

    Thank you for reporting this, we're investigating with high priority. This specific issue appears to be from a different cause, as the fixes for Xamarin.Forms breaking changes in v 3.0+ have been applied, however for a more definitive answer I have alerted the dev team.

    I'll respond again once more is known.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  10. Namysław
    Namysław avatar
    42 posts
    Member since:
    Jul 2017

    Posted 17 May 2018 Link to this post

    Same for me at Xamarin.Forms 3.x release, even latest pre release - 3.1.0.469394-pre1:

    C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(791,3): error : Can't resolve the reference 'System.Func`2<System.String,System.String> Xamarin.Forms.Internals.ResourceLoader::get_ResourceProvider()', referenced from the method 'System.Void Telerik.XamarinForms.Input.RadNumericInputResourceDictionary::InitializeComponent()' in 'Xamarin.Forms.Core, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null'.


    Reported also here https://feedback.telerik.com/Project/168/Feedback/Details/249296-linkassemblies-build-errors-with-xamarin-forms-3-0
  11. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 18 May 2018 Link to this post

    Hi Namyslaw,

    Correct, that's the issue that we're working on now, it's suspected to be related to a breaking change in Xamarin.Forms.

    I'll come back and update this thread once the developers identify a solution, but I also recommend that you up-vote and follow the related Feedback Portal item you linked to (click the follow button). The developers who are investigating this will update that item when they've found a solution. If you're following the item, you'll be notified via email with their response.

    In the meantime, to workaround this, you'll need to switch the linker to SDK Assemblies only.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  12. Chris
    Chris avatar
    7 posts
    Member since:
    Jan 2012

    Posted 23 May 2018 in reply to Lance | Technical Support Engineer, Principal Link to this post

    Hi Lance, 

    the option 'Link SDK assemblies only' is not working for me. The only workaround is to use the 'Don't link' option.

  13. Namysław
    Namysław avatar
    42 posts
    Member since:
    Jul 2017

    Posted 23 May 2018 Link to this post

    Same for me - with *SDK Assemblies only* it's not working. Didn't checked with *Don't link*.
  14. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 23 May 2018 Link to this post

    Hello,

    Thank you all for your patience and understanding. I've spoken with the development team, they're still working hard on this and are aiming to provide support for Xamarin.Forms 3.0 in an upcoming release. I will come back here an update you on the progress (or you can subscribe to the related Feedback Portal item for immediate notification on status changes).

    For now, let me explain where we're at and how you can workaround it.

    We believe the problem is rooted in the fact that the Xamarin made a breaking change to use .NET Standard 2.0 after v 2.5.1.527436. Telerik UI for Xamarin is built using Xamarin.Forms 2.4, and has backwards compatibility for PCL based projects..

    In order for us to completely fix this, we need to update the entire product to use a Xamarin.Forms version later than 2.5.1.527436. We are currently checking to see what the lowest version we can move to that would provide support for XF 3.0, but also introduce the least amount of breaking changes.

    Summary:

    UI for Xamarin 2018.2.516 does not officially support Xamarin.Forms versions later than v2.5.1.527436

    Solutions:

    - If you have to use Link All: downgrade to Xamarin.Forms 2.5.1.527436
    - If you can use Link SDK Assemblies Only: You can continue using Xamarin.Forms 3.0 (there still might be unexpected instability)


    Rest assured that the dev team is working hard on this and it's our highest priority at the moment.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  15. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 29 May 2018 Link to this post

    Hello Everyone,

    I wanted to take a moment to update you on the progress of this issue as we're getting closer to a solution.

    Here's where we stand now:

    - I was able to isolate the problem in a 'vanilla' Xamarin.Forms reproducible (i.e. no Telerik UI for Xamarin)
    - I reported this to the Xamarin.Forms developers in a Xamarin.Forms Issue and they've confirmed the bug as a regression
    - I have escalated this to the Microsoft program manager responsible for Xamarin.Forms (we're in direct contact and are working to resolve this quickly)


    Follow Along

    If you'd like to read my report, see the reproducible and follow the discussion, go herehttps://github.com/xamarin/Xamarin.Forms/issues/2835

    If you want to add your voice to the Issue, and help communicate its impact, you can "Thumbs up" my GitHub Issue. Here's a screenshot of where to find that button:





    Next Steps

    I will come back here and update you again as soon as I have more news to share. If all go well, a fix could be released in the next release of Xamarin.Forms 3.0, (no Telerik UI for Xamairn update necessary).

    Again, I sincerely thank you all for your patience and understanding throughout this process.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  16. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 01 Jun 2018 Link to this post

    Hello,

    I have some good news to share! The Xamarin team worked quickly and was able to fix the underlying problem that was causing this problem. 

    A couple points I'd like to call out:

    1 - See my confirmation post at the bottom of the official Issue thread: ResourceProvider Exception in Xamarin.Forms 3.0 due to Signature Change #2835
    2 - The change has been committed and marked Done, go here: Xamarin.Forms Kanban Board for vCurrentTarget (3.0.0).

    The Xamarin development team provided me with a test package (v3.1.0.538216) and I can confirm the issue is resolved in that build. Once they've published a release, simply updating your Xamarin.Forms version will also fix the issue in your app (find the Xamarin.Forms package sources list here). It's still possible there may be other issues, but I can confidently say that this one has been resolved. 

    Although this problem wasn't in Telerik UI for Xamarin, I deeply appreciate your patience and understanding while I worked to investigate, replicate and escalate the problem to Microsoft and the Xamarin team (they were excellent and worked quickly to fix the problem).

    If you have any new issues, please open a new Support Ticket (if you have a support license) or open a new forum thread (if you don't have a support license). We do monitor the forums, and reply as much as we can, but this can be limited by available resources at that time. Whereas a support ticket carries a guaranteed response time and is the fastest path to a solution.

    Thank you for hanging in there and for choosing UI for Xamarin.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  17. Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 06 Jun 2018 Link to this post

    Hi,

    The Xamarin.Forms 3.0 fix is now available in 3.0 sr3 release (3.0.0.550146), available via Nuget or download it directly from the Xamarin.Forms Releases page 

    Build Test

    I have tested this against the May 16th release of Telerik UI for Xamarin (2018.2.516) and confirm it resolves the build issue.

    XF Package Update

    Here's a screenshot of my test app's NuGet Package manager where I call out the SR3 package version number.




    Build result

    With the Linker set "SDK and User Assemblies", the ResourceDictionaries will compile again.




    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  18. Cory
    Cory avatar
    4 posts
    Member since:
    Aug 2011

    Posted 06 Jun 2018 Link to this post

    Thank you for the update.  Unfortunately, it doesn't work for me.  Got an exception where RadNumericInput is used.  The rest of the controls is OK.

    06-06 15:24:25.927 I/MonoDroid( 9499): UNHANDLED EXCEPTION:
    06-06 15:24:25.967 I/MonoDroid( 9499): System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeInitializationException: The type initializer for 'Telerik.XamarinForms.Input.RadNumericInput' threw an exception. ---> System.MissingMethodException: System.Func`2<string, string> Xamarin.Forms.Internals.ResourceLoader.get_ResourceProvider()
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Telerik.XamarinForms.Input.RadNumericInputResourceDictionary..ctor () [0x00006] in <05a9022984a44c32a3a7ba37abe0a7e8>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Telerik.XamarinForms.Input.RadNumericInput..cctor () [0x00229] in <05a9022984a44c32a3a7ba37abe0a7e8>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):    --- End of inner exception stack trace ---
    06-06 15:24:25.967 I/MonoDroid( 9499):   at (wrapper managed-to-native) System.Reflection.MonoCMethod.InternalInvoke(System.Reflection.MonoCMethod,object,object[],System.Exception&)
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) [0x00002] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):    --- End of inner exception stack trace ---
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.Reflection.MonoCMethod.InternalInvoke (System.Object obj, System.Object[] parameters) [0x00017] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.RuntimeType.CreateInstanceMono (System.Boolean nonPublic) [0x000a8] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.RuntimeType.CreateInstanceSlow (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) [0x00009] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.RuntimeType.CreateInstanceDefaultCtor (System.Boolean publicOnly, System.Boolean skipCheckThis, System.Boolean fillCache, System.Threading.StackCrawlMark& stackMark) [0x00027] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.Activator.CreateInstance (System.Type type, System.Boolean nonPublic) [0x0002c] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at System.Activator.CreateInstance (System.Type type) [0x00000] in <f32579baafc1404fa37ba3ec1abdc0bd>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.CreateValuesVisitor.Visit (Xamarin.Forms.Xaml.ElementNode node, Xamarin.Forms.Xaml.INode parentNode) [0x00256] in D:\a\1\s\Xamarin.Forms.Xaml\CreateValuesVisitor.cs:95
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.ElementNode.Accept (Xamarin.Forms.Xaml.IXamlNodeVisitor visitor, Xamarin.Forms.Xaml.INode parentNode) [0x000ac] in D:\a\1\s\Xamarin.Forms.Xaml\XamlNode.cs:149
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.ElementNode.Accept (Xamarin.Forms.Xaml.IXamlNodeVisitor visitor, Xamarin.Forms.Xaml.INode parentNode) [0x00079] in D:\a\1\s\Xamarin.Forms.Xaml\XamlNode.cs:145
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.ElementNode.Accept (Xamarin.Forms.Xaml.IXamlNodeVisitor visitor, Xamarin.Forms.Xaml.INode parentNode) [0x00079] in D:\a\1\s\Xamarin.Forms.Xaml\XamlNode.cs:145
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.ElementNode.Accept (Xamarin.Forms.Xaml.IXamlNodeVisitor visitor, Xamarin.Forms.Xaml.INode parentNode) [0x00079] in D:\a\1\s\Xamarin.Forms.Xaml\XamlNode.cs:145
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.RootNode.Accept (Xamarin.Forms.Xaml.IXamlNodeVisitor visitor, Xamarin.Forms.Xaml.INode parentNode) [0x00079] in D:\a\1\s\Xamarin.Forms.Xaml\XamlNode.cs:202
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.XamlLoader.Visit (Xamarin.Forms.Xaml.RootNode rootnode, Xamarin.Forms.Xaml.HydrationContext visitorContext) [0x00054] in D:\a\1\s\Xamarin.Forms.Xaml\XamlLoader.cs:140
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.XamlLoader.Load (System.Object view, System.String xaml) [0x00058] in D:\a\1\s\Xamarin.Forms.Xaml\XamlLoader.cs:89
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.XamlLoader.Load (System.Object view, System.Type callingType) [0x00026] in D:\a\1\s\Xamarin.Forms.Xaml\XamlLoader.cs:67
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Xaml.Extensions.LoadFromXaml[TXaml] (TXaml view, System.Type callingType) [0x00000] in D:\a\1\s\Xamarin.Forms.Xaml\ViewExtensions.cs:36
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Zenith.Clients.UI.ParameterNumericCell.InitializeComponent () [0x00001] in d:\workspace.zenith\Zenith\Zenith\Zenith.Clients.UI\obj\Debug
    etstandard2.0\Cells\ParameterNumericCell.xaml.g.cs:24
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Zenith.Clients.UI.ParameterNumericCell..ctor () [0x00008] in d:\workspace.zenith\Zenith\Zenith\Zenith.Clients.UI\Cells\ParameterNumericCell.xaml.cs:11
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Zenith.Clients.UI.Pages.Application.ApplicationPage+<InitializeComponent>_anonXamlCDataTemplate_0.LoadDataTemplate () <0x94c72bf0 + 0x0005b> in <3e4af3a5a08543ba8044c36d78ddd1b9>:0
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.ElementTemplate.CreateContent () [0x00026] in D:\a\1\s\Xamarin.Forms.Core\ElementTemplate.cs:82
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Internals.DataTemplateExtensions.CreateContent (Xamarin.Forms.DataTemplate self, System.Object item, Xamarin.Forms.BindableObject container) [0x00000] in D:\a\1\s\Xamarin.Forms.Core\DataTemplateExtensions.cs:19
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Internals.TemplatedItemsList`2[TView,TItem].ActivateContent (System.Int32 index, System.Object item) [0x00000] in D:\a\1\s\Xamarin.Forms.Core\TemplatedItemsList.cs:534
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Internals.TemplatedItemsList`2[TView,TItem].CreateContent (System.Int32 index, System.Object item, System.Boolean insert) [0x00000] in D:\a\1\s\Xamarin.Forms.Core\TemplatedItemsList.cs:543
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Internals.TemplatedItemsList`2[TView,TItem].GetOrCreateContent (System.Int32 index, System.Object item) [0x00023] in D:\a\1\s\Xamarin.Forms.Core\TemplatedItemsList.cs:602
    06-06 15:24:25.967 I/MonoDroid( 9499):   at Xamarin.Forms.Internals.TemplatedItemsList`2[TView,TItem].get_Item (System.Int32 index) [0x00000] in D:\a\1\s\Xamarin.Forms.Core\TemplatedItemsList.cs:337
    06-06 15:24:25.977 I/MonoDroid( 9499):   at Xamarin.Forms.Platform.Android.ListViewAdapter.GetCellsFromPosition (System.Int32 position, System.Int32 take) [0x0003b] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\ListViewAdapter.cs:516
    06-06 15:24:25.977 I/MonoDroid( 9499):   at Xamarin.Forms.Platform.Android.ListViewAdapter.GetCellForPosition (System.Int32 position) [0x00000] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\ListViewAdapter.cs:437
    06-06 15:24:25.977 I/MonoDroid( 9499):   at Xamarin.Forms.Platform.Android.ListViewAdapter.GetView (System.Int32 position, Android.Views.View convertView, Android.Views.ViewGroup parent) [0x0006d] in D:\a\1\s\Xamarin.Forms.Platform.Android\Renderers\ListViewAdapter.cs:215
    06-06 15:24:25.977 I/MonoDroid( 9499):   at Android.Widget.BaseAdapter.n_GetView_ILandroid_view_View_Landroid_view_ViewGroup_ (System.IntPtr jnienv, System.IntPtr native__this, System.Int32 position, System.IntPtr native_convertView, System.IntPtr native_parent) [0x00018] in <263adecfa58f4c449f1ff56156d886fd>:0
    06-06 15:24:25.977 I/MonoDroid( 9499):   at (wrapper dynamic-method) System.Object.6ce4f953-7bb6-42c6-9f0c-68dbc7196ad2(intptr,intptr,int,intptr,intptr)
    06-06 15:24:26.007 W/art     ( 9499): JNI RegisterNativeMethods: attempt to register 0 native methods for android.runtime.JavaProxyThrowable
    06-06 15:24:26.007 D/Mono    ( 9499): DllImport searching in: '__Internal' ('(null)').
    06-06 15:24:26.007 D/Mono    ( 9499): Searching for 'java_interop_jnienv_throw'.
    06-06 15:24:26.007 D/Mono    ( 9499): Probing 'java_interop_jnienv_throw'.
    06-06 15:24:26.007 D/Mono    ( 9499): Found as 'java_interop_jnienv_throw'.

     

  19. Answer
    Lance | Technical Support Engineer, Principal
    Admin
    Lance | Technical Support Engineer, Principal avatar
    1002 posts

    Posted 06 Jun 2018 Link to this post

    Hello Cory,

    I've just finished tested RadNumericInput and am not seeing the System.MissingMethodException: System.Func`2<string, string> error.

    Here's the result:



    Two Things

    1 - Can you confirm you're using UI for Xamarin 2018.2.516? (there were some ResourceDictionary fixes in that release that you should also compile with).
    2 - It is possible that the project wasn't fully clean upon building after the Xamarin.Forms update.

    Here's what you can do to ensure a clean build using only the lastest packages and assemblies:

    1 - Close Visual Studio and navigate to the project in File Explorer (or Finder if you're on Mac)
    2 - Go though every project and permanently delete the bin and obj folder from each project
    3 - If your solution root has a Packages folder, delete that also
    4 - Reopen the solution in Visual Studio
    5 - Right click and "rebuild" each project separately, starting with the class library 

    If it doesn't work, open a support ticket using this link and include the all the code you're using for the RadNumericInput so I can replicate it. I'll start investigating as soon as I see your ticket come in.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  20. Cory
    Cory avatar
    4 posts
    Member since:
    Aug 2011

    Posted 06 Jun 2018 in reply to Lance | Technical Support Engineer, Principal Link to this post

    Thanks, Lance.  That did the trick.
Back to Top