{"push_id":1080325574,"size":597,"distinct_size":597,"ref":"refs/heads/master","head":"9936573efa9989150f957b2177485719fcc1d037","before":"a493795ea4aa0d9f550d3a54d75e8cc9849e070b","commits":[{"sha":"11594b8531ee2611e2885b5511e09e3af6fdbaf5","author":{"email":"869b6d4ad2e8568ee95f278df489a5ca0c6a560a@gmail.com","name":"Michal Kulinski"},"message":"Fix navigation in UIExplorer. Use current index instead of fixed valu…\n\nSummary:Motivation: After second navigation event in UIExplorer, content in main page always stayed the same.\nFix: For second and future navigation events use stack.index to retrieve state from stack.children.\nCloses https://github.com/facebook/react-native/pull/6312\n\nDifferential Revision: D3018119\n\nPulled By: andreicoman11\n\nfb-gh-sync-id: 4c502c42a0cb7b240e558515fb8fd766d6e1f856\nshipit-source-id: 4c502c42a0cb7b240e558515fb8fd766d6e1f856","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/11594b8531ee2611e2885b5511e09e3af6fdbaf5"},{"sha":"464273374306bcbe81400e782d1fe1c5c7129a07","author":{"email":"b57005b4b34ac31b85270b9cb24e8436b410d81c@gmail.com","name":"manonthemat"},"message":"Add app to showcase with source link\n\nSummary:3 small changes\n\nAdded a published android app to the showcase.\n\nModified the rendering of the apps.\nWhen there's a _source_ property on the app object, the link will show up as shown in this screenshot.\n![screen shot 2016-02-04 at 9 13 31 am](https://cloud.githubusercontent.com/assets/5065940/12823220/a79bafcc-cb1f-11e5-8cf5-03b03ecadc45.png)\n\nAlso, external links have the _blank target and not just blank (without the underscore), so a new tab/window will always be opened.\nCloses https://github.com/facebook/react-native/pull/5761\n\nDifferential Revision: D2943464\n\nfb-gh-sync-id: 18c88a90fc7c477730a78442ab0ab45733676dea\nshipit-source-id: 18c88a90fc7c477730a78442ab0ab45733676dea","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/464273374306bcbe81400e782d1fe1c5c7129a07"},{"sha":"7dbba3ba5f7d6cb161d67e4070f3827ffe1033a6","author":{"email":"2bf091d4671a593de182b9af634bcbec9c44db5e@gmail.com","name":"Jan Monschke"},"message":"Add SoundCloud Pulse to the app showcase\n\nSummary:Simple PR that adds SoundCloud Pulse to the app showcase\nCloses https://github.com/facebook/react-native/pull/6224\n\nDifferential Revision: D2994345\n\nfb-gh-sync-id: 97c81c9149f90bf10c4b04ff79eeaf9f8710f26c\nshipit-source-id: 97c81c9149f90bf10c4b04ff79eeaf9f8710f26c","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/7dbba3ba5f7d6cb161d67e4070f3827ffe1033a6"},{"sha":"006907bdaa6975fc65480f8bf6867f1b97a3b2c4","author":{"email":"35a1091f854fff1e63c654c7a51cad152cfd07b8@fb.com","name":"Nick Lockwood"},"message":"Initialize bridge on a background queue\n\nSummary: This diff adds support for initializing the bridge on an arbitrary thread. This is helpful if you want to defer bridge creation, or prevent it from delaying your app startup.\n\nReviewed By: javache\n\nDifferential Revision: D2965725\n\nfb-gh-sync-id: 8065fa89e850031c72ee4427351300986985e9de\nshipit-source-id: 8065fa89e850031c72ee4427351300986985e9de","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/006907bdaa6975fc65480f8bf6867f1b97a3b2c4"},{"sha":"24c458aa0851bb9990ad20d336380ae9a546c370","author":{"email":"e03af45c95eb87e11570d8d0a0c39ab7f4f86030@fb.com","name":"Tadeu Zagallo"},"message":"Fix JS deallocation on load errors\n\nSummary:Fixes #6281\n\nThe JS executor is invalidated from `[RCTBatchedBridger stopLoadingWithError:]`\nwhich prevented another blocks that depended on the executor to run in the bridge\ninvalidation.\n\nReviewed By: javache\n\nDifferential Revision: D3018299\n\nfb-gh-sync-id: 4f482b9b697bfabd24b405398d25c72b9e1a3c84\nshipit-source-id: 4f482b9b697bfabd24b405398d25c72b9e1a3c84","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/24c458aa0851bb9990ad20d336380ae9a546c370"},{"sha":"f885f5335c63b37c46be740da19dd16b739b134d","author":{"email":"cdbf1580cf396fd1b0e402edbd6e13feca87b8ea@fb.com","name":"Fada Chen"},"message":"Backed out D3012969\n\nDifferential Revision: D3019087\n\nfb-gh-sync-id: 8f137351d1fd89b71260b73b2f8daefb6f00127a\nshipit-source-id: 8f137351d1fd89b71260b73b2f8daefb6f00127a","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/f885f5335c63b37c46be740da19dd16b739b134d"},{"sha":"33e9e3464896bdc31d634f7e538c97f2ce7b9014","author":{"email":"cdbf1580cf396fd1b0e402edbd6e13feca87b8ea@fb.com","name":"Fada Chen"},"message":"Backed out changeset D3012925\n\nDifferential Revision: D3019076\n\nfb-gh-sync-id: 201895cd5555845c8a7aa3c0b0f4d0a012912144\nshipit-source-id: 201895cd5555845c8a7aa3c0b0f4d0a012912144","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/33e9e3464896bdc31d634f7e538c97f2ce7b9014"},{"sha":"fd3a0ba781082a567d5713524fb269877baa0b1d","author":{"email":"2e272eddd959d1d0cf6ef86cf6e48f56f05de4d1@fb.com","name":"David Aurelio"},"message":"Play nice with `fetch` after the newest changes that add support for `XMLHttpRequest.response`\n\nSummary:After adding support for `XMLHttpRequest#response`, the `fetch` polyfill detects buffer support when debugging in Chrome and sets `responseType` to `'blob'`.\nIn that case, the response was always empty.\n\nThis change will construct a blob if `responseType` has been set to `'blob'` in order to avoid that problem\n\nReviewed By: steveluscher\n\nDifferential Revision: D3018884\n\nfb-gh-sync-id: 4ade0413de67242c3565d95c2880d4a981ba2342\nshipit-source-id: 4ade0413de67242c3565d95c2880d4a981ba2342","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/fd3a0ba781082a567d5713524fb269877baa0b1d"},{"sha":"62788a15f9e41daf2b5f1da48df02301b67f6fba","author":{"email":"deae6cab6ae66c911ff49cdbe437e28e9273e38a@gmail.com","name":"Mark Rickert"},"message":"Allows a user to specify an xcode scheme name.\n\nSummary:When running `react-native run-ios`, this feature allows a user to specify which scheme to run.\n\nMy project's scheme name is not the same as the xcode project name. Running `react-native run-ios` would error with the following:\n\n```\n± |master ↓95 ✓| → react-native run-ios\nFound Xcode workspace Poot.xcworkspace\nLaunching iPhone 6 (9.2)...\nBuilding using \"xcodebuild -workspace Poot.xcworkspace -scheme Poot -destination id=2B3E8AAC-DD61-414C-95BD-F4829A8F7CE6 -derivedDataPath build\"\nUser defaults from command line:\n    IDEDerivedDataPathOverride = /Users/mrickert/Documents/project/ios/build\n\nxcodebuild: error: The workspace named \"Poot\" does not contain a scheme named \"Poot\". The \"-list\" option can be used to find the names of the schemes in the workspace.\nInstalling build/Build/Products/Debug-iphonesimulator/Poot.app\nAn error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):\nFailed to install the requested application\nAn application bundle was n\nCloses https://github.com/facebook/react-native/pull/6157\n\nDifferential Revision: D3020313\n\nPulled By: frantic\n\nfb-gh-sync-id: 9d99fa382b3f50045759acea18eff418b15d511d\nshipit-source-id: 9d99fa382b3f50045759acea18eff418b15d511d","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/62788a15f9e41daf2b5f1da48df02301b67f6fba"},{"sha":"e9c96451e08d1693c462b9165bd777751592afe0","author":{"email":"f87e5dba9accef1a9a04e8942bedbac1246035be@gmail.com","name":"Janic Duplessis"},"message":"Add issue bot close command and add janicduplessis to the bot whitelist\n\nSummary:Adds a generic close command to the issue bot and add myself to the task force list.\nCloses https://github.com/facebook/react-native/pull/6349\n\nReviewed By: mkonicek\n\nDifferential Revision:D3021271\nNinja: RN GitHub bot only\n\nPulled By: mkonicek\n\nfb-gh-sync-id: dbdce129c4287173a4c16889c16bb5ed9ded5f79\nshipit-source-id: dbdce129c4287173a4c16889c16bb5ed9ded5f79","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/e9c96451e08d1693c462b9165bd777751592afe0"},{"sha":"72b274a9b94a256431e595446a54bcc6eb2192a8","author":{"email":"0fc59c042372860aa6b62d775ccdea45759761a6@gmail.com","name":"Nick Baugh"},"message":"Removed Parse reference since its service is shutting down\n\nSummary:I updated the Network documentation to not lead users to use Parse, since its service is shutting down.\nCloses https://github.com/facebook/react-native/pull/6140\n\nDifferential Revision: D2974665\n\nfb-gh-sync-id: 2a784ad00f742f9f2e2ce369f8b3e1eaab0e2ad4\nshipit-source-id: 2a784ad00f742f9f2e2ce369f8b3e1eaab0e2ad4","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/72b274a9b94a256431e595446a54bcc6eb2192a8"},{"sha":"d0a26a75fb5d2740b93e3960cd6bbd13f11a8c88","author":{"email":"08eb872429d0023047f532457bedba8a9a1ab8d1@fb.com","name":"Tim Yung"},"message":"RN: Fix Exponential WebSocket Growth from DevTools\n\nSummary:025281230de2e316f2770a2db71f8bec6fe43a07 changed `WebSocket` to fire both `onerror` and `onclose`.\n\nHowever, `setupDevtools` assumed that only one of the two handlers would ever be invoked. When the handler is invoked, it re-invokes itself to keep a socket open. But since both handelrs are invoked, a series of closed or failed sockets can cause an exponential increase in sockets opened.\n\nSymptoms of this bug include eventually reaching the maximum number of file descriptors allowed by the operating system, or a non-responsive system. Within React Native applications, symptoms include a failure to load resources from the React Native server or application crashes.\n\nReviewed By: frantic\n\nDifferential Revision: D3022697\n\nfb-gh-sync-id: 8131ecbd6d8ba30281253340d30370ff511a5efd\nshipit-source-id: 8131ecbd6d8ba30281253340d30370ff511a5efd","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/d0a26a75fb5d2740b93e3960cd6bbd13f11a8c88"},{"sha":"aae521f57e56c0790f957a2f254327057b8ee72e","author":{"email":"d0dfade14ee01c1c97ef649c8d2cde2551fd86b7@fb.com","name":"Denis Koroskin"},"message":"Add ReactCompoundViewGroup interface that allows having both virtual and non-virtual (View) children\n\nSummary: In React, ReactCompoundView is supposed to be implemented by a View, but there is no ViewGroup counterpart that allows mixing virual nodes and non-virtual ones (Views) in the same parent. This is needed because TouchTargetHelper always considers child Views when looking for touch target before falling back to View/ReactCompoundView. This works incorrectly for e.g. layout-only / flattened nodes. ReactCompoundViewGroup allow intercepting touch event before it is dispatched to its children. In that sense, ReactCompoundView.reactTagForTouch() is like View.onTouchEvent() whereas ReactCompoundViewGroup.interceptsTouchEvent() is like ViewGroup.onInterceptTouchEvent().\n\nDifferential Revision: D3018028\n\nfb-gh-sync-id: d2c70a55afb9ce9823275e7483d72e0ebedf52e4\nshipit-source-id: d2c70a55afb9ce9823275e7483d72e0ebedf52e4","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/aae521f57e56c0790f957a2f254327057b8ee72e"},{"sha":"102a31c13eed82432b3e0d93230653394f7baa3d","author":{"email":"f87e5dba9accef1a9a04e8942bedbac1246035be@gmail.com","name":"Janic Duplessis"},"message":"Fix RefreshControl layout on screen rotation and consecutive pull to refresh not working properly\n\nSummary:Fixes the RefreshControl layout after a screen rotation. See #6311 for a more detailed explanation. I fixed it by adjusting the frame of the RefreshControl in `layoutSubviews` of the parent ScrollView.\n\nWhile working on fixing this I noticed that when doing a 'pull to refresh' and then not scrolling and wait for it to end the next one will not behave like the first one (it will require pulling further down for the spinner to start spinning). I fixed that too by scrolling the scrollview back to 0 manually before calling `UIRefreshControl.endRefreshing`.\n\n**Test plan (required)**\nTested using the UIExplorer RefreshControl example.\n\nWhen doing a pull to refresh and then rotating the screen the RefreshControl must stay positioned properly.\nDoing multiple consecutive pull to refresh without scrolling after should all behave the same.\n\nFixes #6311\nCloses https://github.com/facebook/react-native/pull/6359\n\nDifferential Revision: D3023727\n\nfb-gh-sync-id: f50ae52ea769c2b3e5025c362544a8809a71aa00\nshipit-source-id: f50ae52ea769c2b3e5025c362544a8809a71aa00","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/102a31c13eed82432b3e0d93230653394f7baa3d"},{"sha":"49b2805da2237c60559b779f3f6475914f311698","author":{"email":"c957e032d335b473767cd9e88f389763705ccb58@gmail.com","name":"realaboo"},"message":"Geolocation Accuracy and Cached Location Bug\n\nSummary:There are two issues:\n\n1. When calling startObserving or getCurrentPosition for the first time, _locationManager is not initialized and the accuracy value set in options is lost.\n\n2. When using the cached location _lastLocationEvent, current timestamp retrieved by CFAbsoluteTimeGetCurrent() is from 2001, but the timestamp of the location is from 1970. In addition, the comparison between _lastLocationEvent[@\"coords\"][@\"accuracy\"] and options.accuracy is incorrect. Less value indicates more accurate location.\nCloses https://github.com/facebook/react-native/pull/6198\n\nDifferential Revision: D3023786\n\nPulled By: nicklockwood\n\nfb-gh-sync-id: 869c0e34252470275bf99cf0e5861747247f1158\nshipit-source-id: 869c0e34252470275bf99cf0e5861747247f1158","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/49b2805da2237c60559b779f3f6475914f311698"},{"sha":"82e2038dfdd5b9b251a51b03ca31ec1895ba7347","author":{"email":"b28fe47f344ea47a742972f6caa7ef1537d21708@microsoft.com","name":"Daniel Rosenwasser"},"message":"Link to 'LinuxWindowsSupport.md' at the appropriate commit.\n\nSummary:Fixes #6314.\n\nWhen node-haste is officially the package for users to fix the timeout constant, the docs will need to be updated again, but that's a worry for down the line.\nCloses https://github.com/facebook/react-native/pull/6328\n\nDifferential Revision: D3023114\n\nPulled By: mkonicek\n\nfb-gh-sync-id: 939cba5f065c1d3bbd2706115a3a704e62975c98\nshipit-source-id: 939cba5f065c1d3bbd2706115a3a704e62975c98","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/82e2038dfdd5b9b251a51b03ca31ec1895ba7347"},{"sha":"2fe67162ae8abbe6fafbd070a5ff5762c7656254","author":{"email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@alper.nl","name":"Alper Cugun"},"message":"Added objective-c class/module semantics\n\nSummary:This really stumped me and I thought it could be added to the docs.\nCloses https://github.com/facebook/react-native/pull/6136\n\nDifferential Revision: D2973912\n\nPulled By: mkonicek\n\nfb-gh-sync-id: 0da1a946e2c2ad00056037a6492be3e99096582e\nshipit-source-id: 0da1a946e2c2ad00056037a6492be3e99096582e","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/2fe67162ae8abbe6fafbd070a5ff5762c7656254"},{"sha":"10e990f415e3aabf49bde098956723c356948503","author":{"email":"e8f1c8c7b1c5136249ca30be657ad3ccc05f3c3e@fb.com","name":"Martin Konicek"},"message":"Don't publish shrinkwrap\n\nSummary:See comments on https://github.com/facebook/react-native/pull/6346\nWe cannot publish the shrinkwrap file to npm and make the same file\nwork with the internal fb infra.\n\nWe've never had the shrinkwrap file in a release of RN, keeping it\nthat way for now should be ok.\n\nReviewed By: bestander\n\nDifferential Revision: D3024260\n\nfb-gh-sync-id: 477509eb9a9890c1955a957ece922d692cd35aab\nshipit-source-id: 477509eb9a9890c1955a957ece922d692cd35aab","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/10e990f415e3aabf49bde098956723c356948503"},{"sha":"87c26885a3520cbb661afcc23efb22943438e52d","author":{"email":"bcef7a046258082993759bade995b3ae8bee26c7@byteburgers.com","name":"Laurence Bortfeld"},"message":"Update fetch to latest https://github.com/github/fetch\n\nSummary:This fixes https://github.com/facebook/react-native/issues/6326 with updating https://github.com/facebook/react-native/blob/master/Libraries/Fetch/fetch.js to latest from  https://github.com/github/fetch.\n\ncc skevy steveluscher\nCloses https://github.com/facebook/react-native/pull/6347\n\nDifferential Revision: D3024308\n\nPulled By: davidaurelio\n\nfb-gh-sync-id: da87827b94d683aeb66be345e255bd771fdba1be\nshipit-source-id: da87827b94d683aeb66be345e255bd771fdba1be","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/87c26885a3520cbb661afcc23efb22943438e52d"},{"sha":"9d09efdd53017877328a9fbaef2fd2cfd31352fc","author":{"email":"2e272eddd959d1d0cf6ef86cf6e48f56f05de4d1@fb.com","name":"David Aurelio"},"message":"transform before extracting dependencies\n\nSummary:Make packager transform files before extracting their dependencies.\n\nThis allows us to extract dependencies added by transforms (and to avoid including them manually).\n\nIt also allows for better optimization and to get rid of the “whole program optimization” step:\nThis diff utilizes the new worker introduced in D2976677 / d94a567 – that means that minified builds inline the following variables:\n\n- `__DEV__` → `false`\n- `process.env.NODE_ENV` → `'production'`\n- `Platform.OS` / `React.Platform.OS` → `'android'` / `'ios'`\n\nand eliminates branches of conditionals with constant conditions. Dependency extraction happens only after that step, which means that production bundles don’t include any modules that are not used.\n\nFixes #4185\n\nReviewed By: martinbigio\n\nDifferential Revision: D2977169\n\nfb-gh-sync-id: e6ce8dd29d1b49aec49b309201141f5b2709da1d\nshipit-source-id: e6ce8dd29d1b49aec49b309201141f5b2709da1d","distinct":true,"url":"https://api.github.com/repos/xu6148152/react-native/commits/9d09efdd53017877328a9fbaef2fd2cfd31352fc"}]}