{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":29028775,"defaultBranch":"main","name":"react-native","ownerLogin":"facebook","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2015-01-09T18:10:16.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/69631?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1721149123.0","currentOid":""},"activityList":{"items":[{"before":"8d0cbbf0e6435e0a29d1d5d218b93c9eef1a2dcd","after":"db16a7895ee2642ec5f7f517c008973a0be3b8a1","ref":"refs/heads/main","pushedAt":"2024-07-16T21:39:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"jsinspector: Vendor base64 encoding, remove folly::base64 dependency (#45445)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45445\n\nRoll our own base64 encoding and revert D59685218, which fixed the missing Folly dependency implied by D54309633.\n\nI assumed Folly base64 was already elsewhere in RN but given it isn't, and we only need simple, non-perf-sensitive encoding for the debugger (not the SIMD or delegated implementations, or decoding), it might be best to just include our own encoder.\n\nChangelog: [Internal]\n\nReviewed By: cipolleschi\n\nDifferential Revision: D58323859\n\nfbshipit-source-id: 5ce98561e9ced82765e8e7c18e5d2ebfa8148c8c","shortMessageHtmlLink":"jsinspector: Vendor base64 encoding, remove folly::base64 dependency (#…"}},{"before":"892c8352cae25db8e5b5df27451e1bc0290a9558","after":"8d0cbbf0e6435e0a29d1d5d218b93c9eef1a2dcd","ref":"refs/heads/main","pushedAt":"2024-07-16T21:02:10.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Make build_android publish to the staging repositories (#45468)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45468\n\nThis should greatly reduce the time spent on build_npm_package\nbecause we're moving all the publishing logic to build_android.\n\nI need to do a bit more testing with nightlies to make sure that everything is published correctly.\n\nChangelog:\n[Internal] [Changed] - Make build_android publish to the stating repositories\n\nReviewed By: cipolleschi\n\nDifferential Revision: D59804015\n\nfbshipit-source-id: be3f0b6e16f5fdbf760ec7a5e16c8e258e06dd28","shortMessageHtmlLink":"Make build_android publish to the staging repositories (#45468)"}},{"before":"c085180264ea68f71b050cbb6b9a8274e36c3fbf","after":"892c8352cae25db8e5b5df27451e1bc0290a9558","ref":"refs/heads/main","pushedAt":"2024-07-16T20:46:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Use more accurate type in LinkingManager spec file (#45450)\n\nSummary:\nThe `LinkingModule.getInitialURL` method is declared as returning a `Proimise` but looking at the implementation it can also return null:\n\nhttps://github.com/facebook/react-native/blob/a96272e27eeee0c7a26e73bb32e55d3ef8d741aa/packages/react-native/Libraries/LinkingIOS/RCTLinkingManager.mm#L166\nwhich is returned by\nhttps://github.com/facebook/react-native/blob/a96272e27eeee0c7a26e73bb32e55d3ef8d741aa/packages/react-native/Libraries/Linking/Linking.js#L96\nwhich happens to expand the type to the correct type for most external users.\n\nReact-native-window's turbomodule codegen is more type strict, and so cannot return null with the current spec.\n\n## Changelog:\n\n[INTERNAL] [FIXED] - Use more accurate type in LinkingManager spec file\n\nPull Request resolved: https://github.com/facebook/react-native/pull/45450\n\nTest Plan:\nType change only, so should only affect build time change which will be caught by CI.\nHave verified that this type change allows react-native-windows to return null.\n\nReviewed By: robhogan\n\nDifferential Revision: D59816089\n\nPulled By: zeyap\n\nfbshipit-source-id: 9810f150ce84b503883e72b1f29518d2e62258b6","shortMessageHtmlLink":"Use more accurate type in LinkingManager spec file (#45450)"}},{"before":"0f051f603492f97a85e051f112d96180352bba77","after":"c085180264ea68f71b050cbb6b9a8274e36c3fbf","ref":"refs/heads/main","pushedAt":"2024-07-16T19:40:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"jsinspector: Support UTF-8 responses to CDP's IO.read (#45426)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45426\n\nThe initial implementation of `Network.loadNetworkResource` and the accompanying `IO.read` (D54202854) base64-encodes all data as if it is binary. This is the more general case, and we'll continue to base64-encode non-text resources.\n\nIn the common case of text resources (particularly JS and JSON), it'd be preferable to do as Chrome does and send UTF-8 over the wire directly. This has a few performance benefits:\n - Less CPU and RAM footprint on device (UTF-8 truncation is constant-time, fast, and in-place), similarly less decoding for the frontend.\n - 25% less data per chunk (base64 encodes 3 bytes as 4 characters), implies up to 25% fewer network round trips for large resources.\n\nIt also has the benefit of being human-readable in the CDP protocol inspector.\n\n## Determining whether data is text\nWe use exactly Chromium's heuristic for this (code pointers in comments), which is based only on the `Content-Type` header, and assuming any text mime type is UTF-8.\n\n## UTF-8 truncation\nThe slight implementation complexity here is that `IO.read` requests may specify a maximum number of bytes, and so we must slice a raw buffer up into valid UTF-8 sequences. This turns out to be fairly simple and cheap:\n 1. Naively truncate the buffer, inspect the last byte\n 2. If the last byte has topmost bit =0, it's ASCII (single byte) and we're done.\n 3. Otherwise, look back at most 3 bytes to find the first byte of the code point (topmost bits 11), counting the number of \"continuationBytes\" at the end of our buffer. If we don't find one within 3 bytes then the string isn't UTF-8 - throw.\n 4. Read the code point length, which is encoded into the first byte.\n 5. Resize to remove the last code point fragment, unless it terminates correctly exactly at the end of our buffer.\n\n## Edge cases + divergence from Chrome\nChrome's behaviour here in at least one case is questionable and we intentionally differ:\n - If a response has header \"content-type: text/plain\" but content eg`0x80` (not valid UTF-8), Chrome will respond to an `IO.read` with `{ \"data\": \"\", \"base64Encoded\": false, \"eof\": false }`, ie an empty string, but will move its internal pointer such that the next or some subsequent `IO.read` will have `\"eof\": true`. To the client, this is indistinguishable from a successfully received resource, when in fact it is effectively corrupted.\n - Instead, we respond with a CDP error to the `IO.read`. We do not immediately cancel the request or discard data, since not all `IO.read` errors are necessarily fatal. I've verified that CDT sends `IO.close` after an error, so we'll clean up that way (this isn't strictly guaranteed by any spec, but nor is `IO.close` after a resource is successfully consumed).\n\nChangelog:\n[General][Added] Debugger: Support text responses to CDP `IO.read` requests\n\nReviewed By: hoxyq\n\nDifferential Revision: D58323790\n\nfbshipit-source-id: def8bf8426266f16bb305d836a6efe8927a9dfc4","shortMessageHtmlLink":"jsinspector: Support UTF-8 responses to CDP's IO.read (#45426)"}},{"before":"fb9ce762f7658afec3339e05162e920c15f15e7d","after":"0f051f603492f97a85e051f112d96180352bba77","ref":"refs/heads/main","pushedAt":"2024-07-16T19:35:22.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Add missing lock around assignment of cancellation handler in `RCTImageLoader` (#45454)\n\nSummary:\nWhen running the entire unit test suite of `RNTesterPods` with `TSan`, I saw that occasionally a data race was detected on line 843 of `RCTImageLoader`. It seems the completion handler that does contain the lock around `cancelLoad` is called concurrently with the value being assigned on line 843. Here there is no lock in place.\n\nHere is the output of `TSan` when I comment out my fix:\n```\nWARNING: ThreadSanitizer: data race (pid=72490)\n Write of size 8 at 0x000144151ce8 by main thread:\n #0 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:priority:attribution:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16e8030)\n https://github.com/facebook/react-native/issues/1 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:priority:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16df8dc)\n https://github.com/facebook/react-native/issues/2 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16df534)\n https://github.com/facebook/react-native/issues/3 -[RCTImageLoaderTests testImageLoaderUsesImageURLLoaderWithHighestPriority] (RNTesterUnitTests:arm64+0x7cb8)\n https://github.com/facebook/react-native/issues/4 __invoking___ (CoreFoundation:arm64+0x13371c)\n\n Previous write of size 8 at 0x000144151ce8 by thread T4 (mutexes: write M0):\n #0 __140-[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:priority:attribution:progressBlock:partialLoadBlock:completionBlock:]_block_invoke_2 (RNTesterUnitTests:arm64+0x16e8894)\n https://github.com/facebook/react-native/issues/1 __139-[RCTImageLoader _loadImageOrDataWithURLRequest:size:scale:resizeMode:priority:attribution:progressBlock:partialLoadBlock:completionBlock:]_block_invoke (RNTesterUnitTests:arm64+0x16e3430)\n https://github.com/facebook/react-native/issues/2 __139-[RCTImageLoader _loadImageOrDataWithURLRequest:size:scale:resizeMode:priority:attribution:progressBlock:partialLoadBlock:completionBlock:]_block_invoke_3 (RNTesterUnitTests:arm64+0x16e52a8)\n https://github.com/facebook/react-native/issues/3 __75-[RCTImageLoaderTests testImageLoaderUsesImageURLLoaderWithHighestPriority]_block_invoke_2 (RNTesterUnitTests:arm64+0x7f24)\n https://github.com/facebook/react-native/issues/4 -[RCTConcreteImageURLLoader loadImageForURL:size:scale:resizeMode:progressHandler:partialLoadHandler:completionHandler:] (RNTesterUnitTests:arm64+0x6c470)\n https://github.com/facebook/react-native/issues/5 __139-[RCTImageLoader _loadImageOrDataWithURLRequest:size:scale:resizeMode:priority:attribution:progressBlock:partialLoadBlock:completionBlock:]_block_invoke.172 (RNTesterUnitTests:arm64+0x16e4964)\n https://github.com/facebook/react-native/issues/6 __tsan::invoke_and_release_block(void*) (libclang_rt.tsan_iossim_dynamic.dylib:arm64+0x77ee0)\n https://github.com/facebook/react-native/issues/7 _dispatch_client_callout (libdispatch.dylib:arm64+0x3974)\n\n Location is heap block of size 48 at 0x000144151cc0 allocated by main thread:\n #0 malloc (libclang_rt.tsan_iossim_dynamic.dylib:arm64+0x4fa48)\n https://github.com/facebook/react-native/issues/1 _malloc_type_malloc_outlined (libsystem_malloc.dylib:arm64+0xf3ec)\n https://github.com/facebook/react-native/issues/2 _call_copy_helpers_excp (libsystem_blocks.dylib:arm64+0x10b4)\n https://github.com/facebook/react-native/issues/3 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:priority:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16df8dc)\n https://github.com/facebook/react-native/issues/4 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16df534)\n https://github.com/facebook/react-native/issues/5 -[RCTImageLoaderTests testImageLoaderUsesImageURLLoaderWithHighestPriority] (RNTesterUnitTests:arm64+0x7cb8)\n https://github.com/facebook/react-native/issues/6 __invoking___ (CoreFoundation:arm64+0x13371c)\n\n Mutex M0 (0x000108f316e8) created at:\n #0 pthread_mutex_init (libclang_rt.tsan_iossim_dynamic.dylib:arm64+0x2cc98)\n https://github.com/facebook/react-native/issues/1 -[NSLock init] (Foundation:arm64+0x5ca14c)\n https://github.com/facebook/react-native/issues/2 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:priority:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16df8dc)\n https://github.com/facebook/react-native/issues/3 -[RCTImageLoader loadImageWithURLRequest:size:scale:clipped:resizeMode:progressBlock:partialLoadBlock:completionBlock:] (RNTesterUnitTests:arm64+0x16df534)\n https://github.com/facebook/react-native/issues/4 -[RCTImageLoaderTests testImageLoaderUsesImageURLLoaderWithHighestPriority] (RNTesterUnitTests:arm64+0x7cb8)\n https://github.com/facebook/react-native/issues/5 __invoking___ (CoreFoundation:arm64+0x13371c)\n\n Thread T4 (tid=10935088, running) is a GCD worker thread\n```\n\n## Changelog:\n\n[iOS][Fixed] Data race in `RCTImageLoader` related to assignment of cancellation block.\n\nPull Request resolved: https://github.com/facebook/react-native/pull/45454\n\nTest Plan: There are already tests in place for `RCTImageLoader`. I hope these will cover the fix.\n\nReviewed By: realsoelynn\n\nDifferential Revision: D59816000\n\nPulled By: zeyap\n\nfbshipit-source-id: f959d472eb60f83f39ced6711ee395949ab37e7c","shortMessageHtmlLink":"Add missing lock around assignment of cancellation handler in `RCTIma…"}},{"before":"c47b04b07e98ee015d936476a1c2669d7db787a9","after":"fb9ce762f7658afec3339e05162e920c15f15e7d","ref":"refs/heads/main","pushedAt":"2024-07-16T17:48:05.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Enable add-job-summary-as-pr-comment for failed jobs (#45479)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45479\n\nThis just prints a summary on PRs if the Gradle task fails so it's easier to jump directly\nto the failure.\n\nChangelog:\n[Internal] [Changed] - Enable add-job-summary-as-pr-comment for failed jobs\n\nReviewed By: cipolleschi\n\nDifferential Revision: D59812845\n\nfbshipit-source-id: 2069a1c8db7d264ca1af3c1182fa443cb0a69646","shortMessageHtmlLink":"Enable add-job-summary-as-pr-comment for failed jobs (#45479)"}},{"before":"c7a5a70bf0a98e17cad74a686704ac17aaacd5b6","after":"aefe61dee66a87db4b78fbd88f93a5f36cdc675c","ref":"refs/heads/export-D58323859","pushedAt":"2024-07-16T17:44:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"robhogan","name":"Rob Hogan","path":"/robhogan","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/2590098?s=80&v=4"},"commit":{"message":"jsinspector: Vendor base64 encoding, remove folly::base64 dependency (#45445)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45445\n\nRoll our own base64 encoding and revert D59685218, which fixed the missing Folly dependency implied by D54309633.\n\nI assumed Folly base64 was already elsewhere in RN but given it isn't, and we only need simple, non-perf-sensitive encoding for the debugger (not the SIMD or delegated implementations, or decoding), it might be best to just include our own encoder.\n\nChangelog: [Internal]\n\nReviewed By: cipolleschi\n\nDifferential Revision: D58323859","shortMessageHtmlLink":"jsinspector: Vendor base64 encoding, remove folly::base64 dependency (#…"}},{"before":"12f58a64520997edb527cd9605f43690ddf5b357","after":"c47b04b07e98ee015d936476a1c2669d7db787a9","ref":"refs/heads/main","pushedAt":"2024-07-16T17:20:10.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Enable Fusebox by default (#45469)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45469\n\nEnables React Native DevTools by default on `main`, ahead of the 0.76 release. We've observed no new bug reports internally over the last two weeks, and are moving forward with our rollout plan.\n\nChangelog: [Internal]\n\nReviewed By: blakef\n\nDifferential Revision: D59804882\n\nfbshipit-source-id: 0cb6302f4d940718786db2e5d8fb652fae6a8c54","shortMessageHtmlLink":"Enable Fusebox by default (#45469)"}},{"before":"c0b288ca3fedfd58f332876d0677eca5feedab73","after":"12f58a64520997edb527cd9605f43690ddf5b357","ref":"refs/heads/main","pushedAt":"2024-07-16T17:06:36.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Split the rntester APK artifacts in 4 (#45475)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45475\n\nInstead of zipping all the RNTester's APK together, let's\nupload them per buildVariant so it's easier to retrieve them later.\n\nChangelog:\n[Internal] [Changed] - Split the rntester APK artifacts in 4\n\nReviewed By: cipolleschi\n\nDifferential Revision: D59809721\n\nfbshipit-source-id: 2d375475d5cee71c212f4d1f3a4a9edf3442358f","shortMessageHtmlLink":"Split the rntester APK artifacts in 4 (#45475)"}},{"before":"4eb22cc10eeda9eccd4183c5db7ac6dd73576484","after":null,"ref":"refs/heads/nc/debug-signing","pushedAt":"2024-07-16T16:58:43.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"cortinico","name":"Nicola Corti","path":"/cortinico","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3001957?s=80&v=4"}},{"before":"2098806c2207f376027184329a7285913ef8d090","after":"c0b288ca3fedfd58f332876d0677eca5feedab73","ref":"refs/heads/main","pushedAt":"2024-07-16T16:26:39.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Use weak ptr for runtime shadow node reference (#45463)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45463\n\nChangelog: [Internal]\n\nState updates will clone shadow nodes for an shadow tree revision that is outdated.\n\nThis can lead to accessing deallocated shadow node references because the JS renderer committed a newer revision and deallocated the one used by the pending state update.\n\nBy using a weak pointer to hold a reference to the runtime shadow node reference, we can only update references for wrappers that are still valid.\n\nReviewed By: javache\n\nDifferential Revision: D59804999\n\nfbshipit-source-id: 89c9967d139d3cac7d7252994beae419bc591e79","shortMessageHtmlLink":"Use weak ptr for runtime shadow node reference (#45463)"}},{"before":"050006a7a78fee0d54950e7ef672c73f8d680053","after":"2098806c2207f376027184329a7285913ef8d090","ref":"refs/heads/main","pushedAt":"2024-07-16T14:47:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Unbreak RNTester instacrashing on main (#45467)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45467\n\nThis unbreaks RNTester instacrashing on main.\n\nChangelog:\n[Internal] [Changed] - Unbreak RNTester instacrashing on main\n\nReviewed By: javache\n\nDifferential Revision: D59806826\n\nfbshipit-source-id: 6d5246cd02e2c364068d047b973b2954b459df1e","shortMessageHtmlLink":"Unbreak RNTester instacrashing on main (#45467)"}},{"before":"7fd6c2c45e532417d7ebb3fbeba3360cb6905ab3","after":"050006a7a78fee0d54950e7ef672c73f8d680053","ref":"refs/heads/main","pushedAt":"2024-07-16T14:25:34.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Add example for Pressability with Native Driver in RNTester (#45413)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45413\n\n## Changes\nAdd an example in RNTester to test that pressability with NativeDrivers works properly.\n\n## Context\nThe pressability handling is a bit peculiar.\nWe have to handle 3 main behaviors:\n* `PressIn` -> `PressOut` => triggers the `onPress`\n* `PressIn` -> move inside the rectangle -> `PressOut` => triggers the `onPress`\n* `PressIn` -> move outside the rectangle -> `PressOut` => cancel `onPress`.\n\nFor the first case, we detect whether the press happens inside a component in the Native layer only. And everything works.\n\nWhen a move is involved, we:\n1. Detect the initial press in the Native layer\n2. We move the coursor and we delegate the detection of whether we are inside of a rect or not to the JS layer\n3. The JS layer asks the C++ layer about the layout and decide whether we are in case 2 (move but still inside the rect) or in case 3 (move but outside the rect).\n\nThe problem is that with `nativeDriver` and animations, the C++ layer doesn't know about where the receiver view actually is.\nThis results in issues like the one shown by [#36504](https://github.com/facebook/react-native/issues/36504), where the onMove is not handled correctly.\n\n## Solution\nThe solution is to keep detecting whether we are in the receiver view or not in the Native layer and pass the receiver view position and size back to JS so that the JS layer don't have to jump to C++ to make this decision.\n\nWe decided to pass the frame information because the JS layer is adding some padding and configurations to the final rectangle and we don't want to lose those configurations.\n\n## Changelog\n[General][Added] - Add example in RNTester to show that pressability works properly with NativeDrivers\n\nReviewed By: sammy-SC\n\nDifferential Revision: D58182480\n\nfbshipit-source-id: 9ca4fb9a3ca1a8af52ccbe208cbfe8434175f87d","shortMessageHtmlLink":"Add example for Pressability with Native Driver in RNTester (#45413)"}},{"before":"46b269dd4683a133cb83f5f600cdd16cbc22fdf0","after":"7d0ec89498384856afb3fe332a0f6f92babe0b6d","ref":"refs/heads/0.75-stable","pushedAt":"2024-07-16T14:12:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"blakef","name":"Blake Friedman","path":"/blakef","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/49578?s=80&v=4"},"commit":{"message":"Update Podfile.lock\n\nChangelog: [Internal]","shortMessageHtmlLink":"Update Podfile.lock"}},{"before":"5bb57eb2b3884ef0c60551ee80880d95814eb71c","after":"7fd6c2c45e532417d7ebb3fbeba3360cb6905ab3","ref":"refs/heads/main","pushedAt":"2024-07-16T13:31:49.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Fix CCI cache issues (#45460)\n\nSummary:\nCCI on main is broken. We suspect that's due to cache issues which restore a wrong layout for the Folly pod.\nThis PR is an attempt to fix it\n\n## Changelog:\n[Internal] - Fix missing folly base 64\n\nPull Request resolved: https://github.com/facebook/react-native/pull/45460\n\nTest Plan: CCI and GHA are green\n\nReviewed By: sammy-SC, huntie\n\nDifferential Revision: D59804748\n\nPulled By: cipolleschi\n\nfbshipit-source-id: 44d6b169cf3319f4d7ee9e0a5833f07bc6ba4bb3","shortMessageHtmlLink":"Fix CCI cache issues (#45460)"}},{"before":"3fa5362a483420ed1307a77e6669e30130e93011","after":"e74d83d605db565f4620605be613caf50eca9240","ref":"refs/heads/fix-linting-noise","pushedAt":"2024-07-16T13:19:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"blakef","name":"Blake Friedman","path":"/blakef","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/49578?s=80&v=4"},"commit":{"message":"[RN] Fix linting warnings\n\nSummary:\nEvery has a list of these linting warnings, which is just creating\nnoise.\n\nChangelog: [General][Fixed] resolved linting warning polluting everyone's PRs","shortMessageHtmlLink":"[RN] Fix linting warnings"}},{"before":null,"after":"3fa5362a483420ed1307a77e6669e30130e93011","ref":"refs/heads/fix-linting-noise","pushedAt":"2024-07-16T13:09:23.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"blakef","name":"Blake Friedman","path":"/blakef","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/49578?s=80&v=4"},"commit":{"message":"[RN] Fix linting warnings\n\nSummary:\nEvery has a list of these linting warnings, which is just creating\nnoise.\n\nChangelog: [General][Fixed] resolved linting warning polluting everyone's PRs","shortMessageHtmlLink":"[RN] Fix linting warnings"}},{"before":"b243d343fa741de94537d8535f76714ff2985101","after":"5bb57eb2b3884ef0c60551ee80880d95814eb71c","ref":"refs/heads/main","pushedAt":"2024-07-16T12:23:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"Ignore PackagerStatusCallback on invalidated ReactInstanceManager (#45458)\n\nSummary:\nPull Request resolved: https://github.com/facebook/react-native/pull/45458\n\nChecking for packager is an async operation, which may return when we've already destroyed the ReactInstanceManager. Prevent the CatalystInstance from being created if the ReactInstanceManager has been invalidated.\n\nChangelog: [Internal]\n\nReviewed By: cortinico\n\nDifferential Revision: D59753247\n\nfbshipit-source-id: e3ac2b6dd142330e2d4051519b9863584b33f8a6","shortMessageHtmlLink":"Ignore PackagerStatusCallback on invalidated ReactInstanceManager (#4…"}},{"before":"3856a49e3b59cadc4803a015a498c0b9774d9c75","after":"fbf6da259cdb88976e04468a5279b169228e1ab4","ref":"refs/heads/cipolleschi/fix-ci-after-folly-base64","pushedAt":"2024-07-16T11:54:29.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"cipolleschi","name":"Riccardo Cipolleschi","path":"/cipolleschi","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11162307?s=80&v=4"},"commit":{"message":"[RN][CI] Fix CCI cache issues","shortMessageHtmlLink":"[RN][CI] Fix CCI cache issues"}},{"before":null,"after":"4eb22cc10eeda9eccd4183c5db7ac6dd73576484","ref":"refs/heads/nc/debug-signing","pushedAt":"2024-07-16T11:50:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"cortinico","name":"Nicola Corti","path":"/cortinico","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/3001957?s=80&v=4"},"commit":{"message":"Debugging publish.gradle for missing GPG key","shortMessageHtmlLink":"Debugging publish.gradle for missing GPG key"}},{"before":"e02ca334b17a8abbdc51bc38fa0e517a9e7d1969","after":"b243d343fa741de94537d8535f76714ff2985101","ref":"refs/heads/main","pushedAt":"2024-07-16T11:48:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"facebook-github-bot","name":"Facebook Community Bot","path":"/facebook-github-bot","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6422482?s=80&v=4"},"commit":{"message":"fix: background color fix when border is dotted and dashed (#45430)\n\nSummary:\nThis PR fixes these issues: https://github.com/facebook/react-native/issues/42289, https://github.com/facebook/react-native/issues/45368\n\n## Changelog:\n\n[IOS] [FIXED] - Message\n\nIn iOS for old/new architecture when we are trying to pass borderStyle other than 'solid' then in this\n**Old Arch file**\nhttps://github.com/facebook/react-native/blob/2eb7bcb8d9c0f239a13897e3a5d4397d81d3f627/packages/react-native/React/Views/RCTView.m#L807\n**New Arch file**\nhttps://github.com/facebook/react-native/blob/2eb7bcb8d9c0f239a13897e3a5d4397d81d3f627/packages/react-native/React/Fabric/Mounting/ComponentViews/View/RCTViewComponentView.mm#L652\n file useCoreAnimationBorderRendering is coming as nil since borderStyle passed is not **solid**. Due to which else case block executes and there we are applying backgroundColor as nil.\n\nI just removed that hardcoded check for sold style and make sured that it is now working now with all three borderStyle 'dotted' | 'solid' | 'dashed' for Text and View both\n\n