xamarin/Xamarin.Forms

[Bug] Xamarin.Forms 3.6 and Xamarin.Forms.Visual.Material 3.6 failed with exception when resources are defined in Android class library

Open

#6,343 opened on May 29, 2019

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)C# (1,926 forks)batch import
4.0.0e/3 :clock3:help wantedi/highinactivep/Androidt/bug :bug:up-for-grabs

Repository metrics

Stars
 (5,644 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

To have multiple Android applications sharing the same resources mostly images, there's an Android class library containing the resources and assets, referenced by each Android app project. This has been working well with Xamarin.Forms 3.6. However, after introducing Xamarin.Forms.Visual.Material 3.6, the app fails at LoadApplication(new App());

Steps to Reproduce

https://github.com/zijianhuang/xamarinforms4bugs/tree/Branch_ResourcesLib was created from good tag ResourcesLibWorkingWell

Expected Behavior

Show Material Design rendering.

Actual Behavior

Crash at LoadApplication(new App()); with TargetInvocationException

Basic Information

  • Version with issue: Xamarin.Forms.Visual.Material 3.6.0.344457

  • Last known good version:

  • IDE: Visual Studio 2017 Pro

  • Platform Target Frameworks:

    • Android: 5,6,7,8,9

Reproduction Link

https://github.com/zijianhuang/xamarinforms4bugs/tree/Branch_ResourcesLib

Contributor guide

Research direction
Investigate the resource loading mechanism in Xamarin.Forms.Visual.Material when resources are defined in an Android class library, and trace the exception at LoadApplication.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Xamarin.FormsAndroid development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40