Bug 44636 - Getting operation load failed popup in Android designer
Summary: Getting operation load failed popup in Android designer
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android Designer ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: --- minor
Target Milestone: ---
Assignee: Jérémie Laval
Depends on:
Reported: 2016-09-22 19:30 UTC by Ben Beckley
Modified: 2017-07-07 16:11 UTC (History)
6 users (show)

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

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:

Description Ben Beckley 2016-09-22 19:30:40 UTC
While verifying Bug 44460, I ran into a non-fatal error where I would sometimes get a popup stating
>The operation Load failed due to an internal error: android/support/v7/widget/ViewInfoStore$InfoRecord.

Here is the accompanying error from the IDE log

Reproduction Steps (not 100% consistent):
1) Open the axml files in this project
2) Rebuild the project
3) Open and close the axml files
4) Repeat steps 2 & 3 until the popup occurs

Env info: https://gist.github.com/BenBeckley/84a13ed3bc86353116b7821b3bc22800
Comment 1 Luis Aguilera 2017-02-18 00:21:38 UTC
C9 is now closed. We'll move this bug to the next scheduled milestone, "15.1". We'll continue working on these issues, and will attempt to resolve them ASAP.
Comment 2 John Miller [MSFT] 2017-07-07 16:11:11 UTC
I can confirm I am no longer able to reproduce this issue using the latest Visual Studio 15.3 preview builds. Marking this report as RESOLVED.