Build with own configuration in wrong Build/Products folder #17650

Activity

1. react-native-bot commented on Feb 24, 2018

   

   react-native-bot

   on Feb 24, 2018

   Collaborator

   More actions

   Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

   I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

   _{How to Contribute • What to Expect from Maintainers}
2. react-native-bot

   added

   Ran CommandsOne of our bots successfully processed a command.One of our bots successfully processed a command.

   StaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.

   on Feb 24, 2018
3. react-native-bot

   closed this as completedon Feb 24, 2018
4. stale

   removed

   StaleThere has been a lack of activity on this issue and it may be closed soon.There has been a lack of activity on this issue and it may be closed soon.

   on Feb 24, 2018
5. salmanwaheed commented on Feb 24, 2018

   

   salmanwaheed

   on Feb 24, 2018 via email

   More actions

   This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a temporary error. The following address(es) deferred: mkdirenv@gmail.com Domain salmanwaheed.info has exceeded the max emails per hour (180/150 (120%)) allowed. Message will be reattempted later

   …

   ------- This is a copy of the message, including all the headers. ------ Received: from github-smtp2-ext5.iad.github.net ([192.30.252.196]:45529 helo=github-smtp2a-ext-cp1-prd.iad.github.net) by box1177.bluehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from <noreply@github.com>) id 1epQVu-003Je9-4Q for hello@salmanwaheed.info; Fri, 23 Feb 2018 20:28:42 -0700 Date: Fri, 23 Feb 2018 19:24:40 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1519442893; bh=GUYxIoL5mjQS0YsLvxqcCBdJ+sQ3Os2wy1XwOHeeWGg=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tGBd+wFxIIJs1VDl4lmEF4RxN/sZE/k8gE/fLSTW0eliT8endo0AxY10kKNG5cVtq cFFQ1fDYwXRIDbXdBeo/MLK8Xqmt6eWh+A3P7Feb3oWskT0UGaftoyIglbxh2ZjB5h k1+GhKn6dDSte8lAFEKs2zV7h4jCPOtexoMqhbVI= From: React Native Bot <notifications@github.com> Reply-To: facebook/react-native <reply@reply.github.com> To: facebook/react-native <react-native@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Message-ID: <facebook/react-native/issue/17650/issue_event/1490268388@github.com> In-Reply-To: <facebook/react-native/issues/17650@github.com> References: <facebook/react-native/issues/17650@github.com> Subject: Re: [facebook/react-native] Build with own configuration in wrong Build/Products folder (#17650) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5a90daf84acb5_2df23fc30e9c0f34279995"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: react-native-bot X-GitHub-Recipient: salmanwaheed X-GitHub-Reason: subscribed List-ID: facebook/react-native <react-native.facebook.github.com> List-Archive: https://github.com/facebook/react-native List-Post: <mailto:reply@reply.github.com> List-Unsubscribe: <mailto:unsub+00ef1b38a3d0e4cb5e19471f7eeede920f56b460a4f29fb792cf0000000116a89cf892a169ce1142bdca@reply.github.com>, <https://github.com/notifications/unsubscribe/AO8bOBwQpFHpqBY3ouDjoPy_lqRZPhJ0ks5tX4D4gaJpZM4RivUm> X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: hello@salmanwaheed.info X-Spam-Status: No, score=0.8 X-Spam-Score: 8 X-Spam-Bar: / X-Ham-Report: Spam detection software, running on the system "box1177.bluehost.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see root\@localhost for details. Content preview: Closed #17650. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #17650 (comment) [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: github.com] -0.5 SPF_PASS SPF: sender matches SPF record 1.3 HTML_IMAGE_ONLY_24 BODY: HTML: images with 2000-2400 bytes of words 0.0 HTML_MESSAGE BODY: HTML included in message 2.5 DCC_CHECK No description available. -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -2.3 AWL AWL: Adjusted score from AWL reputation of From: address X-Spam-Flag: NO

   ----==_mimepart_5a90daf84acb5_2df23fc30e9c0f34279995 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #17650.

   -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #17650 (comment) ----==_mimepart_5a90daf84acb5_2df23fc30e9c0f34279995 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <p>Closed <a href="#17650" class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="289586634" data-permission-text="Issue title is private" data-url="#17650> <p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="#17650 (comment) it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AO8bOCLFoDPy1uOvMpQ5MrZDGVIoGUniks5tX4D4gaJpZM4RivUm">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AO8bOONUqQtstu9N67cukuHZOpmmIHJHks5tX4D4gaJpZM4RivUm.gif" width="1" /></p> <div itemscope itemtype="http://schema.org/EmailMessage"> <div itemprop="action" itemscope itemtype="http://schema.org/ViewAction"> <link itemprop="url" href="#17650 (comment)> <meta itemprop="name" content="View Issue"></meta> </div> <meta itemprop="description" content="View this Issue on GitHub"></meta> </div> <script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/facebook/react-native","title":"facebook/react-native","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/facebook/react-native"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Closed #17650."}],"action":{"name":"View Issue","url":"#17650 (comment)> ----==_mimepart_5a90daf84acb5_2df23fc30e9c0f34279995--
6. lukaszgoworko commented on Jun 25, 2018

   

   lukaszgoworko

   on Jun 25, 2018

   Author

   More actions

   now I updated my react native

   Environment:
   OS: macOS High Sierra 10.13.5
   Node: 10.4.0
   Yarn: 1.7.0
   npm: 6.1.0
   Watchman: 4.9.0
   Xcode: Xcode 9.4.1 Build version 9F2000
   Android Studio: 2.3 AI-162.3764568

   Packages: (wanted => installed)
   react: 16.3.1 => 16.3.1
   react-native: ^0.55.4 => 0.55.4

   So this is still a problem in newer.
   Should I create a new issue or can this be open again?
7. react

   locked as resolved and limited conversation to collaborators on Feb 24, 2019
8. react-native-bot

   added

   Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.

   on Feb 24, 2019