Bug 36956 - Xamarin.Forms compilation error
Summary: Xamarin.Forms compilation error
Status: RESOLVED NORESPONSE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.0.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-14 05:25 UTC by Bikash
Modified: 2017-06-17 01:54 UTC (History)
5 users (show)

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


Attachments
Error Details (96.61 KB, text/plain)
2015-12-14 05:25 UTC, Bikash
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 or GitHub 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 Bikash 2015-12-14 05:25:40 UTC
Created attachment 14267 [details]
Error Details

Getting following error related to android.support.v4. But iOS project is compiling fine. I am using Xamarin.Forms.
The version details is below. The error also attached.

-------------------------
Xamarin Studio
Version 5.10 (build 871)
Installation UUID: 4fff93c2-9964-48d0-9184-0cf94f0815ed
Runtime:
	Microsoft .NET 4.0.30319.34003
	GTK+ 2.24.23 (MS-Windows theme)
	GTK# 2.12.30

Xamarin.Profiler
Not Installed

Xamarin.Android
Version: 6.0.0 (Enterprise Edition)
Android SDK: D:\Installation\Android\android-sdk
	Supported Android versions:
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1

SDK Build Tools Version: 23.0.2


Java SDK: C:\Program Files (x86)\Java\jdk1.7.0_71
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode, sharing)

Xamarin Android Player
Not Installed

Build Information
Release ID: 510000871
Git revision: 4e9c5abb5ffdae12ba02ac49da83f8b2011dbb88
Build date: 2015-11-12 07:16:34-05
Xamarin addins: 55007ed0e56436f385d8e26394a45be563abc7e8
Build lane: monodevelop-windows-cycle6

Operating System
Windows 6.3.9600.0 (64-bit)
Comment 1 Paul DiPietro [MSFT] 2015-12-14 18:09:35 UTC
A few questions, here: Is this in a new project, or an existing one? Are you able to reproduce the issue in a new project, if it's an existing one?  Based on some of the errors, is the v4 package added to the Android project? Are all of the packages up-to-date and is the same version of Forms being used in each project in the solution?
Comment 2 Bikash 2015-12-14 18:15:17 UTC
Here is the answer:
1.This is a new project and getting this error every time I create a new project and compile it.
2. Yes v4 package is already added.
3. I reinstall Xamarin software multiple times. Every package is showing up-to-date.

Is there any issue with Xamarin.Forms new version ? If so how to downgrade it
Comment 3 Paul DiPietro [MSFT] 2015-12-14 18:16:51 UTC
Uploading the sample project would be much appreciated if you're able to do so.
Comment 4 Bikash 2015-12-14 18:19:25 UTC
It is not related to a specific project. I created new project , just the simple one , multiple times, everytime facing this issue.
Comment 5 David Ortinau [MSFT] 2017-06-17 01:54:27 UTC
We are not able to reproduce this issue.

Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!