Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C70CE200CC0 for ; Sun, 9 Jul 2017 16:22:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C565016A936; Sun, 9 Jul 2017 14:22:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1710E16A933 for ; Sun, 9 Jul 2017 16:22:04 +0200 (CEST) Received: (qmail 40644 invoked by uid 500); 9 Jul 2017 14:22:04 -0000 Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@cordova.apache.org Received: (qmail 40633 invoked by uid 99); 9 Jul 2017 14:22:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Jul 2017 14:22:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id BD04319117F for ; Sun, 9 Jul 2017 14:22:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id eFQyzTXJraRL for ; Sun, 9 Jul 2017 14:22:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C7F945FC97 for ; Sun, 9 Jul 2017 14:22:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 17277E0BB3 for ; Sun, 9 Jul 2017 14:22:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C295624695 for ; Sun, 9 Jul 2017 14:22:00 +0000 (UTC) Date: Sun, 9 Jul 2017 14:22:00 +0000 (UTC) From: "Connor Pearson (JIRA)" To: issues@cordova.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CB-12959) Conflict between camera and media capture plugin MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 09 Jul 2017 14:22:06 -0000 [ https://issues.apache.org/jira/browse/CB-12959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079618#comment-16079618 ] Connor Pearson commented on CB-12959: ------------------------------------- Yeah I accidentally linked to the wrong issue. Right now I'm setting the same variables for each plugin, but I agree that supporting a single config.xml property and documenting how to use it in the plugins is a nicer solution. > Conflict between camera and media capture plugin > ------------------------------------------------ > > Key: CB-12959 > URL: https://issues.apache.org/jira/browse/CB-12959 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-camera, cordova-plugin-media-capture > Reporter: Connor Pearson > Priority: Minor > > We recently had a build fail the itunes upload due to NSCameraUsageDescription not being set. It was caused by the newer version of the media-capture plugin defining NSCameraUsageDescription and NSPhotoLibraryUsageDescriptionentry with an empty string and blowing away the value set by the camera plugin variables. > The workaround is pretty simple: just set the same variables for both plugins, but I would expect core plugins to work nicely with each other. Is it necessary for the plugins to control these parameters? Could one define these values in config.xml instead of relying on the plugins? > Also, if an empty string is no longer valid for app submission should it be added by default? -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org For additional commands, e-mail: issues-help@cordova.apache.org