Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E46D418A93 for ; Mon, 14 Dec 2015 22:20:03 +0000 (UTC) Received: (qmail 42681 invoked by uid 500); 14 Dec 2015 22:20:03 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 42646 invoked by uid 500); 14 Dec 2015 22:20:03 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 77972 invoked by uid 99); 14 Dec 2015 21:53:23 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2015 21:53:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 9C5CCC0026 for ; Mon, 14 Dec 2015 21:53:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Kh83T_XXyA3G for ; Mon, 14 Dec 2015 21:53:11 +0000 (UTC) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 267F2429D0 for ; Mon, 14 Dec 2015 21:53:11 +0000 (UTC) Received: by ioae126 with SMTP id e126so59687734ioa.1 for ; Mon, 14 Dec 2015 13:53:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=vyi1xA/XBT/1++mtqr0cg+v2zxs+SXIn+v8Wu4lu1Oc=; b=N1fDl8pe2eX3yFddXQ0Kys2/F/v2YqfZkDli+GLVpkbn6jw16aSXkR5KkL3Qfq+B6y YnECMY3+f8JUZng7Wyy9BZVjRdEBNyyX6FqSabmRakr4HScZhJ/JlyX+CVtqhp37Af7i CpboEwwgso8CF4nnsY8Kz8/iY9l8ID7egtiKvvE2Acy5pMpI1kMvPg5cQTyd9lk5zyh9 UruvlNPi9p7qL5d7H8UjKqvSJsISsg4hYdcsNTnTGJ9hxscyPKysvv+kup1G41uenrY4 ZW/aL4mH1Rgwzgl8KJiJT/1VBumn2WE5TDD9kHBLReiW2yCvm+aCLr743qfj1BWrK3CL AgyQ== MIME-Version: 1.0 X-Received: by 10.107.128.156 with SMTP id k28mr30210013ioi.26.1450129990805; Mon, 14 Dec 2015 13:53:10 -0800 (PST) Received: by 10.64.25.98 with HTTP; Mon, 14 Dec 2015 13:53:10 -0800 (PST) In-Reply-To: References: Date: Mon, 14 Dec 2015 13:53:10 -0800 Message-ID: Subject: Re: Cordova and Proguard From: Joe Bowser To: dev Content-Type: multipart/alternative; boundary=001a113f8d1efaf75f0526e2b2ef --001a113f8d1efaf75f0526e2b2ef Content-Type: text/plain; charset=UTF-8 It's something that we might add. That said, we may just skip it and add whatever replaces ProGuard, since Google implied it would be replaced at the Android Dev Summit. If you want to work on this and submit a patch or pull request, that'd be awesome. On Sun, Dec 13, 2015 at 10:48 PM, jdhabolt wrote: > Hello, > > I've been unable to find much info online regarding the issue I'm having > with Cordova and Proguard, so as a last ditch effort I'm emailing in hopes > that someone can point me toward a solution. > > I've been developing a simple app via the Cordova CLI workflow (v. 5.4.1). > The Android launch checklist recommends obfuscating with Proguard (or other > tool) while building my release apk. I couldn't find anything on the > Cordova site about Proguard, so I've been Googling around trying to figure > out how this works. The info I've been able to dig up suggests that I can > enable Proguard by adding a few lines to build.gradle ( > > https://stackoverflow.com/questions/30925029/proguard-with-cordova-android-4?rq=1 > ) and/or project.properties ( > > https://iphonedevlog.wordpress.com/2014/12/05/adding-proguard-to-your-android-cordova-project/ > ) file(s). I've tried both to no avail. I've also come across a couple Jira > tickets that seem to indicate that Proguard may not be supported in Cordova > CLI ( https://issues.apache.org/jira/browse/CB-9269 > < > https://issues.apache.org/jira/browse/CB-9269%29%28https://issues.apache.org/jira/browse/CB-9708 > > > )( https://issues.apache.org/jira/browse/CB-9708 > < > https://issues.apache.org/jira/browse/CB-9269%29%28https://issues.apache.org/jira/browse/CB-9708 > > > ) > > It's not clear to me whether the feature is unsupported or if I'm just > doing something wrong as I'm new to app development. Any clarity on this > would be much appreciated! > > Thanks! > --001a113f8d1efaf75f0526e2b2ef--