Andres Zsogon created CB-14077:
----------------------------------
Summary: Build path changed and broke Visual Studio deployment
process
Key: CB-14077
URL: https://issues.apache.org/jira/browse/CB-14077
Project: Apache Cordova
Issue Type: Bug
Components: cordova-android
Affects Versions: 7.0.0, 6.4.0, 7.1.0
Environment: Visual Studio 2017
[email protected]
[email protected]
Reporter: Andres Zsogon
Assignee: Joe Bowser
Attachments: vs2017.png
The *output path* for the built APK was like this on _cordova-android 6.3.0_
and *everything worked perfectly*:
{color:#14892c}/platforms/android/build/outputs/apk/android-debug.apk{color}
The new output path since _cordova-android 6.4.0_ now includes a debug subdir:
{color:#14892c}/platforms/android/build/outputs/apk/{color:#d04437}debug{color}/android-debug.apk{color}
{color:#333333}As a result, the APK can no longer be deployed to device nor
emulator, nor debugged, nor run by any means in *Visual Studio 2017*.{color}
{color:#333333}If this change has been intentional to benefit the _Android
Studio_ IDE, the Visual Studio (which includes far better support for Cordova
apps) users are now totally lost.{color}
{color:#333333}*Android Studio does not provide a SINGLE menu item related to
Apache Cordova. Breaking Visual Studio support in benefit of Android Studio is
exactly the opposite that should be done. I hope this was not the case.*
{color}
{color:#333333}Kindly let me know how do we deploy an APK from Visual Studio
now, even if it requires external hacks and workarounds to make it work like
before. Thanks in advance.{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
