Closed lukaszgoworko closed 6 years ago
react-native-bot
commented
6 years ago 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.
salmanwaheed
commented
6 years ago 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
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: https://github.com/facebook/react-native/issues/17650#event-1490268388 [...]
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: https://github.com/facebook/react-native/issues/17650#event-1490268388 ----==_mimepart_5a90daf84acb5_2df23fc30e9c0f34279995 Content-Type: text/html; 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, view it on GitHub, or mute the thread.
----==_mimepart_5a90daf84acb5_2df23fc30e9c0f34279995--
lukaszgoworko
commented
6 years ago 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?
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment:
OS: macOS High Sierra 10.13.2 Node: 9.3.0 Yarn: 1.3.2 npm: 5.6.0 Watchman: 4.9.0 Xcode: Xcode 9.2 Build version 9C40b Android Studio: 2.3 AI-162.3764568
Packages: (wanted => installed)
react: 16.0.0 => 16.0.0 react-native: 0.50.3 => 0.50.3
dependencies
devDependencies
Target Platform: iOS (8.0)
Steps to Reproduce
Creating new configuration and scheme in Xcode with own icons, name, and app-ID. Change debug configuration.
(Write your steps here:)
At this Point trying to run ProjectStaging on Simulator fails because the build fails. I have noticed, that when building ProjectStaging with Staging configuration on an fresh git clone of my project, some files are build in ios/build/Build/Products/Release-iphonesimulator.
Because of this files the build fails, they can't be found in the Staging-iphonesimulator folder.
There are some links to solutions by changing some build settings for Staging configuration
Changing: Header Search Paths, Framework Search Paths, Library Search Paths and User Header Search Paths to
$(BUILD_DIR)/Release$(EFFECTIVE_PLATFORM_NAME)Now all scheme builds failing when trying to run from Xcode:
/Volumes/Workspace/Projects/Project/ios/ProjectTests/ProjectTests.m:11:9: 'XCTest/XCTest.h' file not foundRunning from console:
node node_modules/react-native/local-cli/cli.js run-ios --device --scheme ProjectStaging --configuration StagingBuild fails because of same issue, but App is installed and running well (cant find any errors for now)Building archive always working
Expected Behavior
Project files for a configuration are in their own folder, so the build is always ok.
Actual Behavior
Correct Build with all files in the right place