* Moving the android specific changes to patch files and reverting them from the repo.
* Apply patches immediately after cloning
* Fixing the webpack config for the bundle to run correctly
* Removing an unwanted hunk from folly makefile hwich might be causing a build failure
* Reverting src/main/jni/third-party/folly/Android.mk hoping for the best. If this doesn't work then will look deeper
* Fixing the patch scripts
* Fixing a patch file with integrity failure.. and tightening the error handling.
* Adding more diagnostics
* More diagnostics
* Fixing line splitting of patch and source files while patching
* Cleaning up the diagnostics.. Patching should work this time.
* Reverting the change needed for MAC/iOS
* More diagnostics printed out ..
* Fixing MAC/iOS build
* yarn test -u
* Update .eslintignore
Update .eslintignore to ignore patching code and patch files.
* Fixing a couple of linking errors in JS'
* Adding prettierignore and making some fixes to the patches
* More fixes to the path
* Making required changes in Apple PR/Publish build pipelines to valiate/publish patched as well as unpatched code
* A fix in the patch application condition
* More fixes in the patch application condition
* Another attempt to fix the patching condition
* Yet Another attempt to fix the patching condition
* Yet Another attempt to fix the patching condition.. forcing the parameter to be strings
* Yet Another attempt to fix the patching condition.. forcing the parameter to be strings
* Making patches work on non-windows.. and more fixes for the condition in yaml
* Diagnostics for debugging conditions
* Diagnostics for debugging conditions 2
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Diagnostics for debugging conditions 3
* Workaround
* Workaround
* Workaround
* Workaround
* Fixing Apple build failure with patch applied ..
* Refactoring the patch application to template
* Fixing the template file relative URL when referenced from another template
* Fixing a mistake introduced while refactoring the patch creating steps.
* Fixing some formatting
* Fixing some formatting
Co-authored-by: Anandraj <anandrag@microsoft.com>
* Remove a stale ref to a deprecated file
* remove more unneeded recovered files- remove libs by ref
* add back lib refs as we get build failures with them out
* fix up blank space issues
* Fix manual merge error.
* Fix missing getters from react-native-implementation.macos.js.
Cherry pick https://github.com/facebook/react-native/pull/28147 into fork to Make RCTKeyWindow multi-window aware and add UIScene support to RCTRedBox.
* release _window now to ensure its UIKit ivars are dealloc'd on the main thread as the RCTRedBox can be dealloc'd on a background thread
* Miscellaneous cleanups
* Cleaning up dead code and unwanted edits and renames
* Bringing back some changes for devmain to work
* Reverting unnecessary changes in a couple of files.
* Fixing the MAC/iOS PR build by including unistd.h back
* Some cleanup to take our fork closer to FB repo
* More cleanups.. Cleaning up the docker file and the changes in the setup
bash script. We no longer run the docker based test in our PR/publish.
They are no longer kept in the FB reporitory as well.
* Cleaning up the unused code snippets in RNTester
* Clearing some more devmain build files.
In order to move to OSS React Native, Windows needs to define
ENUM_BITFIELDS_NOT_SUPPORTED. This causes warnings treated as errors on
the microsoft fork due to macro redefinition. Remove the code that
automatically adds this definiion.
This allows the removal of the YGStyle patch added to RNW. At item was
created to remove this entire chunk once we're off the fork.
* [RNTester] Check-in pod install artefacts
* [RNTester] Add CameraRoll pod dependency back
At least for now so we’re in sync with upstream v0.60.0
* [RNTester] First pass at adding CocoaPods based macOS target
* [RNTester] Add notifications pod to macOS target
* [CocoaPods] Make RCTText pod build for macOS
* [CocoaPods] make RCTLinking pod build for macOS
* [CocoaPods] Exclude more files from RCTText pod
* [CocoaPods] Make Core pod build for macOS
* [CocoaPods] Exclude turbomodule sample from macOS
* [RNTester] Update CocoaPods artefact
* [RNTester] Update macOS target to follow non-pods version
* [CocoaPods] Tag all macOS changes to ease updating
https://github.com/microsoft/react-native/issues/214
* [RNTester] Remove development team references
This change is already made upstream in commit
https://github.com/facebook/react-native/commit/9ece5bda, so when that
is merged in this commit can be skipped.
Until then, not making this change will just lead to file thrashing.
* [RNTester] Import Xcode artefact
This change is already made upstream in commit
https://github.com/facebook/react-native/commit/c1845810, so when that
is merged in this commit can be skipped.
Until then, not making this change will just lead to file thrashing.
* [RNTester] Start Metro on launch of macOS product
* [RCTRedBox] Fix -[RCTRedBoxWindow dismiss] on macOS
As per https://www.thecave.com/2015/08/10/dispatch-async-to-main-queue-doesnt-work-with-modal-window-on-mac-os-x/#update2
the main queue is already executing a block when we start the new
modal runloop and as the main queue is a serial queue it won’t perform
new work until the current block is finished. In short, the task is
queued, but will never be performed by GCD. This change side-steps GCD
and instead directly invokes -dismiss on the main thread.
There’s no real need for RNTester to use MS specific versions. So simply
removing those from the system will make the lockfile stable, as far as
versions go, just like the upstream version.
Closes https://github.com/microsoft/react-native/issues/218