Bug 51422 - [VS20170] - Incorrect ABIs set by default
Summary: [VS20170] - Incorrect ABIs set by default
Status: CONFIRMED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 7.4 (15.3)
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2017-01-11 18:52 UTC by Cody Beyer (MSFT)
Modified: 2017-06-27 17:04 UTC (History)
9 users (show)

Tags:
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 for Bug 51422 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Cody Beyer (MSFT) 2017-01-11 18:52:48 UTC
# Description

By default, the only ABI set in release mode is armeabi-v7a

While this may be appropriate for devices (perhaps arm64 should be included also) this causes a deployment failure when deploying to the x86 emulator

# Solutions

I suggest that we either include the appropriate ABIs for emulator testing, or provide a more appropriate error message when the incorrect ABI is set for the chosen deployment target

# Versions

Microsoft Visual Studio Enterprise 2017 RC
Version 15.0.26020.0 D15REL
Microsoft .NET Framework
Version 4.6.01586

Installed Version: Enterprise

Architecture Diagrams and Analysis Tools   00369-50000-00000-AA345
Microsoft Architecture Diagrams and Analysis Tools

Visual Basic 2017 RC   00369-50000-00000-AA345
Microsoft Visual Basic 2017 RC

Visual C# 2017 RC   00369-50000-00000-AA345
Microsoft Visual C# 2017 RC

Visual C++ 2017 RC   00369-50000-00000-AA345
Microsoft Visual C++ 2017 RC

Visual F# 4.1   00369-50000-00000-AA345
Microsoft Visual F# 4.1

Application Insights Tools for Visual Studio Package   8.4.01118.2
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2016   15.0.21206.0
ASP.NET and Web Tools 2016

Command Bus, Event Stream and Async Manager   Merq
Provides ICommandBus, IEventStream and IAsyncManager MEF services for loosely coupled Visual Studio extension components communication and integration.

Common Azure Tools   1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

JavaScript Language Service   2.0
JavaScript Language Service

JavaScript Project System   2.0
JavaScript Project System

JavaScript UWP Project System   2.0
JavaScript UWP Project System

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

Mono Debugging for Visual Studio   Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.

NuGet Package Manager   4.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

TypeScript   2.1.3.0
TypeScript tools for Visual Studio

Visual Studio Tools for Universal Windows Apps   15.0.26009.00
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.

Xamarin   4.3.0.459 (7c3dcf2)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   7.1.0.13 (72366f7)
Visual Studio extension to enable development for Xamarin.Android.

Xamarin.iOS   10.4.0.33 (d93ae7e)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 1 Joaquin Jares 2017-06-05 14:36:53 UTC
This is now fixed in the property pages. All the ABIs are selected by default (and there are other options, like fastdev or not and such).
Comment 2 Joaquin Jares 2017-06-05 14:55:45 UTC
My bad. I checked debug. It makes sense that release will only be arm, though, but I'm reopening while we decide.
Comment 3 Jonathan Pryor 2017-06-27 17:02:43 UTC
> By default, the only ABI set in release mode is armeabi-v7a
> 
> While this may be appropriate for devices (perhaps arm64 should be included also)
> this causes a deployment failure when deploying to the x86 emulator.

We're trying to "thread" between two subjective requirements:

1. We don't want the default app size to be "too big", and
2. We want the default Release app to be "useful"

Each ABI requires 1.3-2MB in native libraries be added to the .apk, depending on whether `libmono-btls-shared.so` is required (required to support TLS 1.2 with WebRequest), so we want to choose only *one* ABI *by default*.

Additionally, we want the default Release .apk to be able to be meaningfully useful on the Google Play Store.

x86 would not be "meaningfully useful"; very few Android devices support x86.

The last time we updated the default, armeabi-v7a was the ABI that best fit these requirements: it is supported on a majority of Android devices, so making it the default single ABI made the most sense.

x86 doesn't make sense, and *still* doesn't make sense. If we were to update today, *arguably* arm64-v8a should be made the default, but I see no reason for x86 to be made the default.

If you need x86 support, enable x86 support in the Project Properties dialog.
Comment 4 Jonathan Pryor 2017-06-27 17:04:20 UTC
> or provide a more appropriate error message when the incorrect ABI is 
> set for the chosen deployment target

This is something we should do.