Bug 44382 - Custom controls or Android Support controls (CoordinatorLayout/TextInputLayout) just shows RED in the designer
Summary: Custom controls or Android Support controls (CoordinatorLayout/TextInputLayou...
Status: RESOLVED NORESPONSE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android Designer ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jérémie Laval
URL:
Depends on:
Blocks:
 
Reported: 2016-09-15 18:38 UTC by Jeremy Kolb
Modified: 2017-08-10 08:24 UTC (History)
7 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Logs (8.29 KB, application/x-zip-compressed)
2016-09-15 19:47 UTC, Jeremy Kolb
Details
App Theme (1.22 KB, application/xml)
2016-09-21 18:19 UTC, Jeremy Kolb
Details
App Theme v21 (674 bytes, text/xml)
2016-09-21 18:20 UTC, Jeremy Kolb
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Jeremy Kolb 2016-09-15 18:38:31 UTC
I have JDK8 x64 installed.  VS2015 update 3.

All custom views seem to render red in the designer.  I haven't seen any debug information or instructions on how to debug this.  Is there something I need to do to enable this much touted feature?
Comment 1 Jeremy Kolb 2016-09-15 18:39:04 UTC
Even support library UI pieces like CoordinatorLayout and TextInputLayout render as red rectangles.
Comment 2 Jérémie Laval 2016-09-15 19:43:05 UTC
The information would be contained in the normal Visual Studio logs, if you can zip them up for me and attach them to this bug report (see https://kb.xamarin.com/customer/en/portal/articles/1675684-where-can-i-find-my-version-information-and-logs-#ide-and-installer-logs)

Off-hand the only thing I would suggest is to make sure you have rebuilt your project after adding the support-library NuGets/upgraded Xamarin and that it compiled fine.
Comment 3 Jeremy Kolb 2016-09-15 19:47:20 UTC
Created attachment 17517 [details]
Logs

Look at the most recent log
Comment 4 Jeremy Kolb 2016-09-15 19:47:45 UTC
Yes I have definitely rebuilt.  See the most recent log entry in the zip.
Comment 5 Jeremy Kolb 2016-09-15 19:56:40 UTC
According to that log file I need to use an AppCompat theme.  That seems to help in most cases where I am seeing this issue.  Can I get the designer to use MY theme?  It does not appear in the drop down (and is based on AppCompat).

Also does the tools xml namespace work?
Comment 6 Jérémie Laval 2016-09-15 20:17:51 UTC
If we aren't showing your theme in the dropdown that's an issue.

Once we figure why that's not the case you can set that theme in your AndroidManifest.xml file and the designer will use it by default for every layout that you open when you do this.

Could you attach your theme XML file to this bug so that I can take a look?
Comment 7 Jeremy Kolb 2016-09-21 18:19:54 UTC
Created attachment 17647 [details]
App Theme

Style.xml file
Comment 8 Jeremy Kolb 2016-09-21 18:20:18 UTC
Created attachment 17648 [details]
App Theme v21
Comment 9 Jeremy Kolb 2016-10-24 15:02:59 UTC
Is this still NEEDINFO?
Comment 11 John Miller [MSFT] 2017-07-07 16:06:01 UTC
Thanks so much for taking the time to provide the files Jeremie requested! I’m unable to reproduce this issue using the latest Visual Studio 15.3 preview builds. Can you attach a sample project that reproduces the issue and include the steps I can take to reproduce it? If you don't see the issue with 15.3, please let me know.
Comment 12 Prashant [MSFT] 2017-08-10 08:24:05 UTC
Because we have not received a reply to our request for more information, we are marking this issue as RESOLVED→NORESPONSE. If you are still encountering this issue on the latest Visual Studio 2017 Preview version 15.3, please don’t hesitate to reopen the ticket with the requested information. 

Thanks!