Completed
Last Updated: 25 Mar 2019 16:04 by ADMIN
ADMIN
Lance | Technical Support Engineer, Principal
Created on: 20 Jul 2018 12:50
Category: UI for Xamarin
Type: Feature Request
2
Common: Android Build Warnings
As of 2018.2.620, UI for Xamarin will invoke approximate 600 warnings when compiling an Android project that uses SDK later than 23.

This is due to the fact that the UI for Xamarin.Android controls are built on API 23, which will surface warnings at compile time if the project consuming them is using a later version.

Although UI for Xamarin is compatible with newer version, and causes no impact on the outcome, these warnings obscure any meaningful warnings the user might have. 

This is a problem when projects are built in a CI/Cd pipeline and warnings are treated as important/significant for enterprise CD deployment (i.e. scrolling through 600 warnings to find any legitimate warnings is not practical).

Available in R3 2018 release.
10 comments
ADMIN
Georgi
Posted on: 25 Mar 2019 16:04
Hi Rob,

The original issue is fixed and it works with Xamarin.Forms 3.4 and with Xamarin.Forms 3.5 is more case of a new issue.
What happens is that with some new version of Xamarin.Forms, new Support Libraries are introduced (and your projects targets that specific Android version that uses it, in this case 9.0) these type of warnings would appear as we are build against the older version.

Usually, we upgrade to latest Xamarin.Forms for major release after we have done intensive testing, making sure no regression issues are introduced and this fixes the issue.

Therefore

Regards,
Georgi
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
Rob
Posted on: 25 Mar 2019 15:40

@Georgi,

If I understand correctly, this is fixed in the "old" version of Xamarin.Forms (3.4).  However, the problem still exits in the "current" version of Xamarin.Forms (3.5). 

Is this correct? 

Thanks,

Rob (I reported the bug originally)

ADMIN
Georgi
Posted on: 25 Mar 2019 15:32
Hello Ben,

Indeed I was able to observe the warnings when using Xamarin.Forms 3.5 or newer. It introduces new support libraries (version 28) and  as we are built against Xamarin.Forms 3.4 we are using version 27.

Please note, that it is in our plans to upgrade the Xamarin.Forms version for our next major release (R2 2019, expected in May) and  thus we will upgrade the support libraries and the warnings should not be present.

Meanwhile using Xamarin.Forms 3.4 should resolve the warnings, and if you are using 3.4 and you are still experiencing this please send us a repo project so I can investigate it further.

Hope this would help.


Regards,
Georgi
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
Ben
Posted on: 18 Mar 2019 21:26

We're using your newest release 2019.1.318.1 and we're still getting about 100 of these. I have a few below so you can see. We're using version 28.0.0.1 of the Xamarin.Android packages and our project is set to target Android 9 (API version 28). 

 

4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Animation.tooltip_enter. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Animation.tooltip_exit. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Attribute.textColorError. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Boolean.abc_config_closeDialogWhenTouchOutside. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Boolean.abc_config_showMenuShortcutsWhenKeyboardPresent. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Color.error_color_material. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Dimension.abc_action_bar_progress_bar_size. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Layout.tooltip. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Style.Base_V11_Theme_AppCompat_Dialog. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Style.Base_V11_Theme_AppCompat_Light_Dialog. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Style.Base_V11_ThemeOverlay_AppCompat_Dialog. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Style.Base_V12_Widget_AppCompat_AutoCompleteTextView. Please check that your Nuget Package versions are compatible.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1783,2): warning XA0106: Skipping MLHCMobile.Droid.Resource.Style.Base_V12_Widget_AppCompat_EditText. Please check that your Nuget Package versions are compatible.
ADMIN
Yana
Posted on: 17 Sep 2018 13:02
Hi all,

I am glad to inform you this issue is resolved in the latest R3 2018 release of Telerik UI for Xamarin.  Please give it a try and if you experience such issues with it, let us know.

-Yana
n/a
Posted on: 12 Sep 2018 09:11
Hi there guys, any progress regarding this, were busy with creating very important mobile apps on our side and were worried about investing too much and that it will be too difficult to spot meaningful warnings when it comes to later stages in our development, any feedback would be appreciated.
ADMIN
Yana
Posted on: 23 Aug 2018 11:12
Hi Robert,

I am sorry for the delayed reply. Actually, we've made some progress on that matter, still I cannot specify a timeframe as this change requires thorough testing. 
Currently the controls are compatible with the newer Android versions - although build warnings are raised, this doesn't affect the app.  Am I missing something regarding this?

Lastly, I'd like to assure you we're working extensively on our Telerik UI for Xamarin suite, you could check the latest stuff here: https://www.telerik.com/support/whats-new/xamarin-ui
and what we're preparing for R3 2018 here: https://www.telerik.com/support/whats-new/xamarin-ui/roadmap

Regards,
Yana
Rob
Posted on: 07 Aug 2018 06:49
Why hasn’t work been started on this issue already? Telerik has known about the problem for at least a year. As a customer, I have to ask if Telerik is committed to the Xamarin platform. 

Given Google’s requirement, can you guarantee that new applications will work on Google Play?
ADMIN
Yana
Posted on: 07 Aug 2018 06:06
Hi Robert,

Thank you for your comment. I understand how important this is and we definitely have it marked with high priority on our side. 
I cannot commit to a certain timeframe, still as you're following the item, you will receive an email notification as soon as there is any progress on the task.

Regards,
Yana
Rob
Posted on: 06 Aug 2018 14:40
Per Google: "Google Play will require that new apps target at least Android 8.0 (API level 26) from August 1, 2018, and that app updates target Android 8.0 from November 1, 2018."

https://developer.android.com/distribute/best-practices/develop/target-sdk

That doesn't give us much time to find and squash bugs introduced by compiling Telerik UI for Xamarin once you release a version compiled with API Level 26.

Any time frame for this?