Cannot build TestFlight version after upgrading to 0.46.4
See original GitHub issueIs this a bug report?
Yes
Environment
macOs Sierra
I deleted the node_modules folder and ran npm install. After that I change the package.json to:
"dependencies": {
"react": "16.0.0-alpha.12",
"react-native": "^0.46.4",
},
"devDependencies": {
"babel-jest": "20.0.3",
"babel-preset-react-native": "1.9.2",
"eslint-config-rallycoding": "^3.2.0",
"jest": "20.0.4",
"react-test-renderer": "16.0.0-alpha.13"
},
react-native -v
: react-native-cli: 2.0.1 react-native: 0.46.4node -v
: v6.11.1npm -v
: 5.3.0
After I upgraded to React Native 0.46.4 I cannot build TestFlight version. I can build version for the simulator and for the device (Debug) but when I tried to make an Archive for TestFlight (Release) I have the following error:
/Users/user/Workspace/BobeZ/node_modules/metro-bundler/build/lib/TerminalClass.js:141
this._nextStatusStr = util.format(format, ...args);
SyntaxError: Unexpected token ...
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Module._extensions..js (module.js:417:10)
at Object.require.extensions.(anonymous function) [as .js] (/Users/user/Workspace/BobeZ/node_modules/babel-register/lib/node.js:152:7)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/Users/user/Workspace/BobeZ/node_modules/react-native/local-cli/server/runServer.js:18:18)
at Module._compile (module.js:410:26)
+ [[ false != true ]]
+ [[ ! -f /Users/user/Library/Developer/Xcode/DerivedData/BobeZ-gftwimogvotpwtbuhunewxpyezll/Build/Intermediates/ArchiveIntermediates/Tuts/BuildProductsPath/Release-iphoneos/BobeZ.app/main.jsbundle ]]
+ echo 'error: File /Users/user/Library/Developer/Xcode/DerivedData/BobeZ-gftwimogvotpwtbuhunewxpyezll/Build/Intermediates/ArchiveIntermediates/BobeZ/BuildProductsPath/Release-iphoneos/BobeZ.app/main.jsbundle does not exist. This must be a bug with'
error: File /Users/user/Library/Developer/Xcode/DerivedData/BobeZ-gftwimogvotpwtbuhunewxpyezll/Build/Intermediates/ArchiveIntermediates/BobeZ/BuildProductsPath/Release-iphoneos/BobeZ.app/main.jsbundle does not exist. This must be a bug with
+ echo 'React Native, please report it here: https://github.com/facebook/react-native/issues'
React Native, please report it here: https://github.com/facebook/react-native/issues
+ exit 2
I edited the scheme to be for Release and also have the right signing setup.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Can not install TestFlight version… | Apple Developer Forums
A solution that worked for a team mate is to install a previous release from TestFlight — after verifying that it works, she...
Read more >New build disappears after uploading it to iTunes Connect
I tried to upload it again by Xcode 8, but it says the build is already uploaded to iTunesConnect. So when I tried...
Read more >Upgrade path for iTunes Connect TestFlight external testers ...
The pragmatic way to ensure all testers are off the app is to wait the 30 days for the build to expire and...
Read more >How To Get Your iOS App Into TestFlight and Test It, for Xcode ...
Every archive uploaded to the App Store needs a unique version and build number combination. My practice is to only change the version...
Read more >TestFlight - How to Upload and Distribute Your App - YouTube
Your browser can't play this video. ... We walk thought creating an App ID, registering with the App Store, archiving and uploading your ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kelset updating to node 8 fixed the problem. Thank you!
@zakster12 I’m currently on 8.1.2 version node and it’s not working. This is only it’s solved with 8 version node? Don’t make sense!