Configuration confused on switch to new release

{
"robot_framework_workspace": "/Users/Scen/Develop/Robot/",

"path_to_python": "/usr/local/bin/python",

"robot_framework_module_search_path":
    [
        "/usr/local/bin",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python27.zip",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-mac/lib-scriptpackages",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-old",
        "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload",
        "/usr/local/lib/python2.7/site-packages",
        "/Library/Python/2.7/site-packages",
    ],

}

Above is my user-setting.json file. And when i run command "create database", error occurs in the sublime console, and the database could not be generated successful. Is there something i missed?
File "/Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/commands/scan_and_index.py", line 72, in add_builtin_vars
f_table = open(table_path, 'r')
FileNotFoundError: [Errno 2] No such file or directory: '/Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/database/scanner/BuiltIn-ca8f2e8d70641ce17b9b304086c19657.json'

I have also seen this error, now and then, but I haven't found a reason why it happens. The error is caused because it can't find the table, in this case the BuiltIn, when it creates a index for a test suite or a resource file. When I did investigate the error, each time the hash in the file name was not correctly calculated by the plugin. But I haven't got any further in my investigation because, for me, the error happens randomly only at the beginning when plugin is loaded and is therefore really hard to debug.
As a workaround, could you run the Robot Framework: Create Database Tables and then Robot Framework: Create Database Index From Active Tab. If that works then you could try run the Robot Framework: Create Database

When i try to call Create Database Tables:
Traceback (most recent call last):
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 574, in run_
return self.run(edit)
File "/Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/commands/scan.py", line 28, in run
file_
File "/Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework     Assistant/commands/scan.py", line 55, in run_scan
  startupinfo=startupinfo
File "./subprocess.py", line 824, in __init__
File "./subprocess.py", line 1386, in _execute_child
TypeError: Can't convert 'list' object to str implicitly

That occurs every time, and right now i could only run "Create Database Table From Active Tab" successfully.
Further information: OSX 10.11. Python 2.7.11

The Robot Framework: Create Database uses internally Robot Framework: Create Database Tables command and it if later fails the former should fail on the same problem. Therefore this kind a looks like a plugin loading problem.
Could you restart the Sublime, wait that plugins are loaded (time depends on the number of plugins) but 60s should be enough. And then rerun the Robot Framework: Create Database Tables and Robot Framework: Create Database Index From Active Tab commands.

I did look the original error message more closely:
File "/Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/commands/scan_and_index.py", line 72, in add_builtin_vars
f_table = open(table_path, 'r')
FileNotFoundError: [Errno 2] No such file or directory: '/Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/database/scanner/BuiltIn-ca8f2e8d70641ce17b9b304086c19657.json'

It seems that this is a new issue and not the same issue which I have encountered. The hash in the BuiltIn-ca8f2e8d70641ce17b9b304086c19657.json is actually correct and therefore it seems that the BuiltIn-ca8f2e8d70641ce17b9b304086c19657.json is not in the where it should be.
When the plugin creates or updates the internal database, it writes events to a log file. The log file is overwritten when Robot Framework: Create Database and Robot Framework: Create Database Tables command are run. So could you re-run the Robot Framework: Create Database command and perhaps post the log file from /Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/database/scan_index.log
Also this could be some OSX specific issue. To rule that one out, could you run the following commands from the Python (from same Python where Robot Framework is installed) prompt:
>>> from hashlib import md5
>>> md5('BuiltIn').hexdigest()

and send the output?
Also please make sure that the path_to_python in our user settings has been configured to point the Python binary where Robot Framework is installed.

I have tried your above steps but nothing help either.  What`s more, the scan_index.log is empty without any output.
Here are the outputs i run in terminal:
In [1]: from hashlib import md5
In [2]: md5('BuiltIn').hexdigest()
Out[2]: 'ca8f2e8d70641ce17b9b304086c19657'

Sorry did forget to ask but what is the error in the Sublime console then? Also from /Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/database/ folder, could you run command: find . to list all files and folders in that folder and subfolders.

The sublime console error is the same as before.
find .
.
./scan_index.log
./scanner

I will need to make you a modified /Users/Scen/Library/Application Support/Sublime Text 3/Packages/Robot Framework Assistant/commands/scan.py so that I can see what are the Popen arguments.

I have an idea, could you edit the user settings file, so that robot_framework_module_search_path contains only one path. Then run the Framework: Create Database command and could you send the console and log file output.

After some debugging, I have found at least one reason why the error happens. If one have multiple entries in the robot_framework_module_search_path setting, the list is not properly handled and causes an error. It should be reflective easy to fix the plugin code to properly support multiple entries in the robot_framework_module_search_path setting,

I have tried to limit robot_framework_module_search_path to only path, the issue still occurs. With empty scan_index.log

Because the setting is actually a list, there might be difference how OSX handles a list the Python subprocess argument. But I also get it fail, in windows, if there are more than one item in the setting. I will fix it and make a new release.

There was few other bugs when setting the robot_framework_module_search_path and https://github.com/andriyko/sublime-robot-framework-assistant/commit/db9afcb1925270309427d0667c5bb0d8da44ed5d should have fixed them all. I will create a new release and if you did install the package from package central you should get the update automatically.
If encounter the same problem again, please send a update we will reopen the issue.

The 3.0.2 now is released and available from the package control.


Scrolling slide index is breaking target slide

Hi, great slides, works well in mobile devices :-) I found a bug, wonder why no one else sees it. in IE10/Edge and Firefox (en/de) from 30+, but not in chrome 73.0.3683.86 on desktop (laptop) windows 7/10))
When you open the slides index and scroll down, e.g. 2. or 3. row, and click, then the target slide is also displaced up to this scoll amount. Even reload does not fix this. It is reproducable in the components.html too.

In order to keep the position of the actual webslide during the selection of a slide via the slide index (otherwise the slides move while scrolling down the slide index) the following additions are required: Find #webslides (line 400 (or so if already editet)) in webslides.css and add:
position: fixed;
top: 0;
left: 0;
width: 100%;
height: 100%;
I'm working with Firefox only and I hope this helps for any other browsers.

Intially, the body element has a height of 100% and has overflow set to hidden. By doing this, scrolling is not possible. When showing the slide index, the body is set to be scrollable, but the height is still 100%.
The problem here, when showing a particular slide, is that Firefox does not reset the body to its original position. Instead, it is moved upwards, but it still has a 100% height and it is not possible to scroll it back into view.
I solved this by adding position: absolute to the body element. In my opinion, this is the easiest solution. This also works in Chrome and Edge.
If I have time, I can try to create a pull request to solve this. I think that issue #143 has the same cause as this one.

Thanks, position:absolute on the body works, I added it to a separate CSS.


autorip web-optimized option?

Is it possible to include an environmental variable to set autorips as "web optimized"?  I've looked everywhere and can't find any option to set this during run/create.

found the solution: edit presets.json.


All channel lists are sorted in alphabetical order now.

Before I can merge this, we need to have some sort of action setup that will automatically sort each section. I don't think I can merge it until then. Otherwise new people that are adding their list will get frustrated on having to manually add their channels into the list. Or I'll end up having to do it manually each time.

Okey i got it . But if implementing such script is taking time, you can sort the readme.md  for now and i think when the contributors find the lists are already sorted then they will add list according to the sorted list and that will be easy for other people.

I'm making the script for sorting the list. It would've been done a long
time ago if I had the flexibility of Python, but since Bash is what we have
to work with it's getting tedious. Bash's inbuilt commands doesn't offer
file manipulation in a very portable way. If you want then I can make a
Python implementation of the script for now. It'll take two days since I
only get two hours a day of free time to do what I want.
On Thu, 27 Feb, 2020, 11:16 PM 5hifaT<EMAIL_ADDRESS>wrote:

Okey i got it . But if implementing such script is taking time, you can
sort the readme.md for now and i think when the contributors find the lists
are already sorted then they will add list according to the sorted list and
that will be easy for other people.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ErikCH/DevYouTubeList/pull/116?email_source=notifications&email_token=AHU4P64AC72TEAEIIXF43DLRE74ARA5CNFSM4K3R6WA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENFI77A#issuecomment-592089084,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHU4P62NZLTE5L7GTWCJ6RDRE74ARANCNFSM4K3R6WAQ
.


[0.75] The project cannot be successfully installed into the ios emulator - iOS build takes too long and never finishes

Description
I created a new react-native project using npx create-natice@latest init native752, using version 0.75.2, but after creating it, I followed the instructions and performed the dependencies installation successfully. But after the yarn ios executes, after opening the 8081 service of Metro v0.80.11, the output is Building the app......  And then it stays that way for a long time with no change.
Steps to reproduce
1、npx create-natice@latest init project
2、yarn ios
3、failed to install to ios emulator
4、I tried to add parameters to yarn ios --verbose to save the complete execution record as a log record
5、Stacktrace or Logs Detailed logging of reasons
React Native Version
0.75.2
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 13.5
  CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
  Memory: 268.12 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.0
    path: ~/.nvm/versions/node/v18.18.0/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v18.18.0/bin/yarn
  npm:
    version: 9.8.1
    path: ~/.nvm/versions/node/v18.18.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/zhaohb/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2411.12071903
  Xcode:
    version: 15.0/15A240d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.12
    path: /Users/zhaohb/.jenv/versions/system/bin/javac
  Ruby:
    version: 3.3.4
    path: /Users/zhaohb/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.2
    wanted: 0.75.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

### Stacktrace or Logs

```text
yarn run v1.22.19
$ react-native run-ios --verbose
info A dev server is already running for this project on port 8081.
info Found Xcode workspace "native752.xcworkspace"
info Found booted iPhone 15 Pro Max
info Building (using "xcodebuild -workspace native752.xcworkspace -configuration Debug -scheme native752 -destination id=B631493D-7DEB-499A-B565-1891F074CB7A")
debug Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace native752.xcworkspace -configuration Debug -scheme native752 -destination id=B631493D-7DEB-499A-B565-1891F074CB7A

User defaults from command line:
    IDEPackageSupportUseBuiltinSCM = YES

debug Prepare packages

debug

debug ComputeTargetDependencyGraph

debug note: Building targets in dependency order

debug note: Target dependency graph (70 targets)
    Target 'native752' in project 'native752'
        ➜ Implicit dependency on target 'Pods-native752' in project 'Pods' via file 'libPods-native752.a' in build phase 'Link Binary'
        ➜ Implicit dependency on target 'DoubleConversion' in project 'Pods' via options '-lDoubleConversion' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'RCT-Folly' in project 'Pods' via options '-lRCT-Folly' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'RCTDeprecation' in project 'Pods' via options '-lRCTDeprecation' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'RCTTypeSafety' in project 'Pods' via options '-lRCTTypeSafety' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-Core' in project 'Pods' via options '-lReact-Core' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-CoreModules' in project 'Pods' via options '-lReact-CoreModules' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-Fabric' in project 'Pods' via options '-lReact-Fabric' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-FabricComponents' in project 'Pods' via options '-lReact-FabricComponents' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-FabricImage' in project 'Pods' via options '-lReact-FabricImage' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-ImageManager' in project 'Pods' via options '-lReact-ImageManager' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-Mapbuffer' in project 'Pods' via options '-lReact-Mapbuffer' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-NativeModulesApple' in project 'Pods' via options '-lReact-NativeModulesApple' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTAnimation' in project 'Pods' via options '-lReact-RCTAnimation' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTAppDelegate' in project 'Pods' via options '-lReact-RCTAppDelegate' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTBlob' in project 'Pods' via options '-lReact-RCTBlob' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTFabric' in project 'Pods' via options '-lReact-RCTFabric' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTImage' in project 'Pods' via options '-lReact-RCTImage' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTLinking' in project 'Pods' via options '-lReact-RCTLinking' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTNetwork' in project 'Pods' via options '-lReact-RCTNetwork' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTSettings' in project 'Pods' via options '-lReact-RCTSettings' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTText' in project 'Pods' via options '-lReact-RCTText' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RCTVibration' in project 'Pods' via options '-lReact-RCTVibration' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RuntimeApple' in project 'Pods' via options '-lReact-RuntimeApple' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RuntimeCore' in project 'Pods' via options '-lReact-RuntimeCore' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-RuntimeHermes' in project 'Pods' via options '-lReact-RuntimeHermes' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-cxxreact' in project 'Pods' via options '-lReact-cxxreact' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-debug' in project 'Pods' via options '-lReact-debug' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-defaultsnativemodule' in project 'Pods' via options '-lReact-defaultsnativemodule' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-domnativemodule' in project 'Pods' via options '-lReact-domnativemodule' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-featureflags' in project 'Pods' via options '-lReact-featureflags' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-featureflagsnativemodule' in project 'Pods' via options '-lReact-featureflagsnativemodule' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-graphics' in project 'Pods' via options '-lReact-graphics' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-hermes' in project 'Pods' via options '-lReact-hermes' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-idlecallbacksnativemodule' in project 'Pods' via options '-lReact-idlecallbacksnativemodule' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-jserrorhandler' in project 'Pods' via options '-lReact-jserrorhandler' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-jsi' in project 'Pods' via options '-lReact-jsi' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-jsiexecutor' in project 'Pods' via options '-lReact-jsiexecutor' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-jsinspector' in project 'Pods' via options '-lReact-jsinspector' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-logger' in project 'Pods' via options '-lReact-logger' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-microtasksnativemodule' in project 'Pods' via options '-lReact-microtasksnativemodule' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-nativeconfig' in project 'Pods' via options '-lReact-nativeconfig' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-perflogger' in project 'Pods' via options '-lReact-perflogger' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-performancetimeline' in project 'Pods' via options '-lReact-performancetimeline' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-rendererconsistency' in project 'Pods' via options '-lReact-rendererconsistency' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-rendererdebug' in project 'Pods' via options '-lReact-rendererdebug' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-runtimescheduler' in project 'Pods' via options '-lReact-runtimescheduler' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'React-utils' in project 'Pods' via options '-lReact-utils' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'ReactCodegen' in project 'Pods' via options '-lReactCodegen' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'ReactCommon' in project 'Pods' via options '-lReactCommon' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'SocketRocket' in project 'Pods' via options '-lSocketRocket' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'Yoga' in project 'Pods' via options '-lYoga' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'fmt' in project 'Pods' via options '-lfmt' in build setting 'OTHER_LDFLAGS'
        ➜ Implicit dependency on target 'glog' in project 'Pods' via options '-lglog' in build setting 'OTHER_LDFLAGS'
    Target 'Pods-native752' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'FBLazyVector' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Foll
debug y' in project 'Pods'
        ➜ Explicit dependency on target 'RCTDeprecation' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-CoreModules' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-FabricComponents' in project 'Pods'
        ➜ Explicit dependency on target 'React-FabricImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-Mapbuffer' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTActionSheet' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTAnimation' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTAppDelegate' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTBlob' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTLinking' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTNetwork' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTSettings' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTText' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTVibration' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeCore' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeHermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-callinvoker' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-defaultsnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-domnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflagsnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-hermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-idlecallbacksnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-jserrorhandler' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsitracing' in project 'Pods'
        ➜ Explicit dependency on target 'React-logger' in project 'Pods'
        ➜ Explicit dependency on target 'React-microtasksnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-nativeconfig' in project 'Pods'
        ➜ Explicit dependency on target 'React-perflogger' in project 'Pods'
        ➜ Explicit dependency on target 'React-performancetimeline' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererconsistency' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-rncore' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'SocketRocket' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'boost' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-rncore' in project 'Pods' (no dependencies)
    Target 'React-RCTAppDelegate' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-CoreModules' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTNetwork' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeCore' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeHermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-defaultsnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-hermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-nativeconfig' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'React-defaultsnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-domnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflagsnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-idlecallbacksnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-microtasksnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        �
debug �� Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-microtasksnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-idlecallbacksnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-featureflagsnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-domnativemodule' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-FabricComponents' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-RuntimeApple' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-CoreModules' in project 'Pods'
        ➜ Explicit dependency on target 'React-Mapbuffer' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeCore' in project 'Pods'
        ➜ Explicit dependency on target 'React-RuntimeHermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-callinvoker' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-jserrorhandler' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-RuntimeHermes' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods
debug '
        ➜ Explicit dependency on target 'React-RuntimeCore' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-hermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsitracing' in project 'Pods'
        ➜ Explicit dependency on target 'React-nativeconfig' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-jsitracing' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
    Target 'React-RuntimeCore' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-jserrorhandler' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-jserrorhandler' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
    Target 'React-RCTFabric' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-FabricComponents' in project 'Pods'
        ➜ Explicit dependency on target 'React-FabricImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTText' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-nativeconfig' in project 'Pods'
        ➜ Explicit dependency on target 'React-performancetimeline' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererconsistency' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-nativeconfig' in project 'Pods' (no dependencies)
    Target 'React-Mapbuffer' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
    Target 'React-FabricComponents' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-logger' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-CoreModules' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTBlob' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'SocketRocket' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
    Target 'React' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTActionSheet' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTAnimation' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTBlob' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTLinking' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTNetwork' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTSettings' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTText' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTVibration' in project 'Pods'
    Target 'React-RCTVibration' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'React-RCTText' in project 'Pods'

debug       ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
    Target 'React-RCTSettings' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'React-RCTLinking' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'React-RCTImage' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTNetwork' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'React-RCTBlob' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-RCTNetwork' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-RCTNetwork' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'React-RCTAnimation' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
    Target 'ReactCodegen' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-FabricImage' in project 'Pods'
        ➜ Explicit dependency on target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-FabricImage' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-logger' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-ImageManager' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
    Target 'React-Fabric' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-logger' in project 'Pods'
        ➜ Explicit depende
debug ncy on target 'React-performancetimeline' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererconsistency' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-performancetimeline' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
    Target 'React-graphics' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
    Target 'React-NativeModulesApple' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'React-callinvoker' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'ReactCommon' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-callinvoker' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-logger' in project 'Pods'
        ➜ Explicit dependency on target 'React-perflogger' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-RCTActionSheet' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
    Target 'RCTTypeSafety' in project 'Pods'
        ➜ Explicit dependency on target 'FBLazyVector' in project 'Pods'
        ➜ Explicit dependency on target 'RCTRequired' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core' in project 'Pods'
    Target 'React-Core' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'RCTDeprecation' in project 'Pods'
        ➜ Explicit dependency on target 'React-Core-React-Core_privacy' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-hermes' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-perflogger' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'SocketRocket' in project 'Pods'
        ➜ Explicit dependency on target 'Yoga' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'Yoga' in project 'Pods' (no dependencies)
    Target 'SocketRocket' in project 'Pods' (no dependencies)
    Target 'React-runtimescheduler' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-callinvoker' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererconsistency' in project 'Pods'
        ➜ Explicit dependency on target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-utils' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-rendererdebug' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
    Target 'React-rendererconsistency' in project 'Pods' (no dependencies)
    Target 'React-hermes' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-perflogger' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-jsiexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-pe
debug rflogger' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-cxxreact' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-callinvoker' in project 'Pods'
        ➜ Explicit dependency on target 'React-cxxreact-React-cxxreact_privacy' in project 'Pods'
        ➜ Explicit dependency on target 'React-debug' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'React-logger' in project 'Pods'
        ➜ Explicit dependency on target 'React-perflogger' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'boost' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-perflogger' in project 'Pods' (no dependencies)
    Target 'React-logger' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
    Target 'React-jsinspector' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'React-featureflags' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'React-runtimeexecutor' in project 'Pods'
        ➜ Explicit dependency on target 'React-jsi' in project 'Pods'
    Target 'React-featureflags' in project 'Pods' (no dependencies)
    Target 'React-jsi' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'boost' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'hermes-engine' in project 'Pods'
    Target 'hermes-engine' in project 'Pods' (no dependencies)
    Target 'React-debug' in project 'Pods' (no dependencies)
    Target 'React-cxxreact-React-cxxreact_privacy' in project 'Pods' (no dependencies)
    Target 'React-callinvoker' in project 'Pods' (no dependencies)
    Target 'React-Core-React-Core_privacy' in project 'Pods' (no dependencies)
    Target 'RCTRequired' in project 'Pods' (no dependencies)
    Target 'RCTDeprecation' in project 'Pods' (no dependencies)
    Target 'RCT-Folly' in project 'Pods'
        ➜ Explicit dependency on target 'DoubleConversion' in project 'Pods'
        ➜ Explicit dependency on target 'RCT-Folly-RCT-Folly_privacy' in project 'Pods'
        ➜ Explicit dependency on target 'boost' in project 'Pods'
        ➜ Explicit dependency on target 'fmt' in project 'Pods'
        ➜ Explicit dependency on target 'glog' in project 'Pods'
    Target 'glog' in project 'Pods'
        ➜ Explicit dependency on target 'glog-glog_privacy' in project 'Pods'
    Target 'glog-glog_privacy' in project 'Pods' (no dependencies)
    Target 'fmt' in project 'Pods' (no dependencies)
    Target 'boost' in project 'Pods'
        ➜ Explicit dependency on target 'boost-boost_privacy' in project 'Pods'
    Target 'boost-boost_privacy' in project 'Pods' (no dependencies)
    Target 'RCT-Folly-RCT-Folly_privacy' in project 'Pods' (no dependencies)
    Target 'FBLazyVector' in project 'Pods' (no dependencies)
    Target 'DoubleConversion' in project 'Pods' (no dependencies)

GatherProvisioningInputs

* Execution stops at this point ......

Reproducer
https://github.com/react-native-community/reproducer-react-native/
Screenshots and Videos
The above warehouse can reproduce the problem I mention

I have same problem. They should help us. https://github.com/facebook/react-native/issues/46380

@zhaohongbo910 sorry to hear that the build time is taking too long.
Can you check a couple of things for me?

Can you try to build from Xcode and see if the build numbers increases or not?

Can you run bundle exec pod deintegrate and then reinstall pods? What I'm looking for is to understand whether you are using a prebuild version of Hermes or if you are trying to build hermes from source, as it is usually one of the pieces that takes most time (and that's why we are distributing prebuilds)

See the yellow line in the screenshot

@cipolleschi Hi，the first
I tried to build from xcode and it was successful ，The following is the Xcode build log

Build ReproducerApp_2024-09-11T10-13-57.txt
the second ，I executed the above command, and then re-installed the pod successfully, but the yarn ios still couldn't build, and as I mentioned above, it didn't move in the middle of the execution
Therefore, you may also need to help look at why the new version of yarn ios construction will be problematic, or every time some from xcode construction, slightly troublesome

Related to https://github.com/facebook/react-native/issues/46380

still ı have problem.

I have updated my environment to xcode 15.4 and iOS 17.5, this issue is gone. But don't know that happened....

I have also updated xcode to lates version but it didn't resolve the issue

After following the RN upgrade helper from 0.73 -> 0.75, I had the same issue.
One of the updates had me delete the file: react-native.config.js from the project which resulted in this error.
Only after restoring react-native.config.js did the build then work.

I had the same issue :(

I had the same issue ...

@hieuminh1810 @kvjp2209 have you tried the solution suggested by @davidmartindev here: https://github.com/facebook/react-native/issues/46352#issuecomment-2350911208 ?

I'm having the same problem.
“GatherProvisioningInputs” does not pass here even though I wait 20-30 minutes.
The profiles I created through Apple Developer are added to the application through Xcode.

I'm having the same problem.
“GatherProvisioningInputs” does not pass here even though I wait 20-30 minutes.
The profiles I created through Apple Developer are added to the application

@ugurdalkiran Hey 🙌
Have you tried what I mentioned, I had exactly what you experience.

I'm having the same problem.
“GatherProvisioningInputs” does not pass here even though I wait 20-30 minutes.
The profiles I created through Apple Developer are added to the application

@ugurdalkiran Hey 🙌
Have you tried what I mentioned, I had exactly what you experience.

There is no react-native.config.js file in my project.

@zhaohongbo910 in the steps to reproduce:
1、npx create-natice@latest init project

Can you confirm exactly how you're bootstrapping a React Native application?

Question
Can folks who are affected please try calling xcodebuild directly, and see if the it's related to this issue.
To find the correct arguments run yarn run ios --verbose.  For example on my system this is:
xcodebuild -workspace RN0752.xcworkspace -configuration Debug -scheme RN0752 -destination id=D282CE59-8F0C-4B72-B34C-AEA3C348D07F

See where I found this:

Control:
Run the command exactly as above.  In my case it is:
xcodebuild -workspace RN0752.xcworkspace -configuration Debug -scheme RN0752 -destination id=D282CE59-8F0C-4B72-B34C-AEA3C348D07F

Question: Does this freeze?
Variable:
If the control freezes, does adding -allowProvisioningUpdates affect this?  For example, my command now looks like this:
xcodebuild -workspace RN0752.xcworkspace -configuration Debug -scheme RN0752 -destination id=D282CE59-8F0C-4B72-B34C-AEA3C348D07F -allowProvisioningUpdates

Question: Does this freeze?

Notes:
I can't reproduce this locally in my environment.  I've tried with:

React Native: 0.75.2 & 0.75.3:
Simulator: 17.2 & 17.5
Hermes: enabled / disabled

$ npx react-native@latest init RNRepro   # or npx<EMAIL_ADDRESS>init RNRRepro
...
$ cd RNRepro/ios
$ bundle install
$ USE_HERMES=1 bundle exec pod install
$ cd ..
$ yarn run ios --verbose
...

I'm using:
 Xcode:
    version: 15.4/15F31d
 iOS SDK:
    Platforms:
      - iOS 17.5
      - macOS 14.5

@blakef
I tried this command and ** BUILD SUCCEEDED **
xcodebuild -workspace ./ios/t.xcworkspace -configuration Debug -scheme t -destination id=6FE03C09-529E-4485-8082-580EF098D093 -allowProvisioningUpdates

The build is successful but the application is not installed in the simulator. How should I proceed from this stage?

@ugurdalkiran to unblock you while we're figuring out if this is an issue we can reproduce, the simplest thing for you would be:

Open in Xcode
Select any Simulator
Press the "Start the Active Scheme" button

In your example:
open ./ios/t.xcworkspace

Then click #1 (pick a Simulator) and then #2:

From what I'm seeing here, this is an Xcode issue folks are having with their provisioning profiles.  We could ask the CLI folks to look at adding the -allowProvisioningUpdates argument, but I'm not sure it resolves the original issue raised.
But I don't think this is a react-native core issue from what I'm seeing. @cipolleschi thoughts?

@blakef this is happening in 0.75... aren't we using our new scripts, rather than deferring to the cli? 🤔
If not, yes, we should rerout this issue to https://github.com/react-native-community/cli

@blakef
I added the "-allowProvisioningUpdates" parameter in @react-native-community/cli-platform-apple/build/commands/buildCommand/buildProject.js with a bad code. :)

So I was expecting to see this parameter when I said run-ios and it was yes.

But again GatherProvisioningInputs stays here. :(

@ugurdalkiran adding the parameter is not enough, I believe. The CLI must handle the parameter in the code and I believe that that code is not there yet.
cc. @szymonrybczak and @thymikee as they maintain the CLI.

For me, upgrading Xcode to version 16.0 solved this problem. 🥲

Im my case, upgrading xcode to 16.0 doesn't help.
I have also tried to upgrade RN to 0.75.4. Problems still exists

@JedrekDabrowski could you try and build from Xcode?

@cipolleschi I have tried before and now, it doesn't solve the issue

@JedrekDabrowski can you show what's happening on Xcode? I don't think that Xcode is hanging. It should either keep building or failing with an error.

@cipolleschi
I have rn 0.75.4 and xCode 16.0, Build is finished without any error, metro is also running. I get modal with notification permission and than app freeze on the splash screen.
mainjs bundle is marked red but it is not related with rn upgrade because on previous version is the same. I guess it  is xCode 16.0 bug

@cipolleschi thanks for your response. I have managed to fix it by changing way we cache images on initial load in our commercial project.
I have also upgraded my RN template to 0.75.4 and after upgrading:

react-native-screens to 3.34.0 - fix type error during ios build
react-native-safe-area-context to 4.10.1 - fix deprecated warning during android build

every thing works fine.
Thanks for help one more time and sorry for confusion.


feat: add correct return type

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on:

npm package (@main dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


November 2020 release

This updates the version in code along with a pypi release.
See tag https://github.com/rsagroup/pyrsa/releases/tag/v3.0.0.post20201106

Codecov Report

Merging #161 (ef01d31) into master (316b984) will increase coverage by 5.93%.
The diff coverage is 70.26%.

@@            Coverage Diff             @@
##           master     #161      +/-   ##
==========================================
+ Coverage   75.63%   81.57%   +5.93%
==========================================
  Files          57       55       -2
  Lines        5335     4851     -484
==========================================
- Hits         4035     3957      -78
+ Misses       1300      894     -406

Impacted Files
Coverage Δ

pyrsa/inference/crossvalsets.py
91.20% <ø> (ø)

pyrsa/rdm/compare.py
94.11% <ø> (ø)

pyrsa/vis/model_plot.py
3.85% <0.00%> (-0.01%)
:arrow_down:

pyrsa/vis/rdm_plot.py
12.06% <0.00%> (-4.22%)
:arrow_down:

setup.py
100.00% <ø> (ø)

pyrsa/rdm/rdms.py
77.66% <16.00%> (-8.67%)
:arrow_down:

pyrsa/simulation/sim.py
76.82% <76.82%> (ø)

pyrsa/util/searchlight.py
79.10% <79.10%> (ø)

tests/test_simulation.py
96.66% <96.66%> (ø)

pyrsa/simulation/__init__.py
100.00% <100.00%> (ø)

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e85823b...ef01d31. Read the comment docs.


Allow using libjit-sys with Rust 1.0

This will provide low-level access to libjit-sys to people using Rust
1.0.  For the fun, high-level stuff, they'll still need to switch to the
nightly branch. :-)
To do this, I needed to do two things:

Use the cargo-ized version of libc, because the in-compiler version
probably won't be un-feature-gated in the immediate future.
Replace PathExt::exists with a Rust-1.0-compatible implementation.

I tested this using multirust:
cd jit.rs/sys
multirust override stable
cargo test

...and I tested the main library as usual using the nightly build:
cd ..
cargo test

Thank you for the merge! I also have a unit test and an example program for sys which will be along in a minute.


IP camera - rtsp - motion

Hi,
do you help me for connect stream rtsp of camera ip? is it detect motion?

Your problem is not a Vlc.Dotnet one but about VLC options syntax. You can find help on the VideoLAN Forums


Enable the gc/global.wast spec test

This involved queuing up table init expressions for later validation because:

Tables (and their init expressions) come before globals definitions in the binary format,
constant expressions can contain global.gets of defined globals now,
and therefore a table init can validly reference a global before it is defined.

This is not ideal, but is fine, since we have some other end-of-module checking already in validate_end. However, that alone isn't good enough. Because constant expressions can contain ref.func $f instructions, which need to insert $f into the "referenced function" set, we need mutable access to the Arc<Module> when processing constant expressions. So we need to drain the unchecked table init expressions before processing each code body, when we still have unique access to the Arc<Module>. But not all Wasm modules have code sections, so at the same time, we still need to do the checking inside validate_end. And when there was a code section, the queue of table init expressions will have already been drained by the time we are in validate_end, so it is okay that we no longer have unique access to the Arc<Module> in that case.

Aha, I guess that our copy of the test suite is a bit out of date, because they fixed this upstream so that the contex that table initializers are evaluated within do not have defined globals present anymore:

https://github.com/WebAssembly/gc/issues/433
https://github.com/WebAssembly/gc/issues/434

Just FYI, I started trying to update the testsuite and plumb that through to this repo, but I probably won't finish today and I go on vacation for three weeks starting tomorrow.

https://github.com/WebAssembly/testsuite/pull/71


[WIP] Feature Autoscaling: Enable organization runner autoscaler

This PR introduces a workaround for autoscaling your organization runners. At the moment, Github doesn't provide an API endpoint that gives you a number of how full your (organizational) queue is. This PR tries to implement a workaround for this, by checking all the repos in an organization for which Actions is enabled and subsequently checks the latest changed repositories. It does the latter by calculating how many minutes ago a repo got changed and compares this number with the SyncPeriod time.
Subsequently, the controller will watch the queues of these repositories and scale up/down.

Fixes https://github.com/summerwind/actions-runner-controller/issues/158

Currently blocked on this: https://github.com/summerwind/actions-runner-controller/issues/221

@ZacharyBenamram thank you again for your reviews! What do you think of the current change proposal? I haven't updated the tests yet, because I wanted to hear your opinion on the changes first.

@erikkn any update on this?

@erikkn any update on this?

@callum-tait-pbx , haven't really had the time to work on this. Are you waiting for this, or can you use TotalNumberOfQueuedAndInProgressWorkflowRuns ?

Tbh I haven't had a chance to get around to testing the the PercentageRunnersBusy metric. I am expecting it to work for our needs as we just want a single RunnerDeployment defined to scale for the whole GitHub org without the need to maintain a specific list of repositories for that runner. We're going to be doing most of the legwork of configuring the runner environment via actions themselves instead of baking tools into a container etc. I think the PercentageRunnersBusy metric will do exactly this but as I say, haven't had a chance to test it as I've been sorting out the stuff we need around this solution. Thought I'd bump this PR though just to see if an alternative was still in the pipeline just in case PercentageRunnersBusy doesn't work for us some reason.

Tbh I haven't had a chance to get around to testing the the PercentageRunnersBusy metric. I am expecting it to work for our needs as we just want a single RunnerDeployment defined to scale for the whole GitHub org without the need to maintain a specific list of repositories for that runner. We're going to be doing most of the legwork of configuring the runner environment via actions themselves instead of baking tools into a container etc so we don't have a need to segregate RunnerDeployments to specific repositories. I think the PercentageRunnersBusy metric will do exactly this but as I say, haven't had a chance to test it as I've been sorting out the stuff we need around this solution. Thought I'd bump this PR though just to see if an alternative was still in the pipeline just in case PercentageRunnersBusy doesn't work for us some reason.

Fair enough, but how will you deal with patching your image (and the binaries living in those images)? And how to make changes to your environment without changing XYZ number of repos?
I will try to work on this PR this week btw.

Fair enough, but how will you deal with patching your image (and the binaries living in those images)? And how to make changes to your environment without changing XYZ number of repos?

We intend to use actions themselves for environment setup rather than baking tools directly into the runner images. So to use a public action as an example, instead of having node baked into the runner image we will use https://github.com/actions/setup-node to configure the required node version as defined in the workflow rather than having it baked into the underlying container. Obviously there are some cons doing it that way but we believe it will be a net positive approach for multiple reasons. We may end up having to bake some tooling into the runner image; it should be very limited beyond some internal tooling. We'd rather build out GitHub Actions for things we can't find an appropriate open source action for than go down the other possible routes of lots of custom images or fewer but more complicated super custom images.
Actions can be version pinned so once we publish a new version of an action it’s a case of communicating and socialising internally. We’ll support X number of releases and then the actions will go into a deprecation process, basically a software house in a software house.
There are some good boilerplate templates to start from for creating actions e..g https://github.com/jacobtomlinson/python-container-action https://github.com/jacobtomlinson/go-container-action
I also imagine in reality this strategy will work for most of our workflows however there will be some legacy stuff that will get their own dedicated runners with more custom runner images. I’ve got a repository setup for creating custom images so we’ll be able to provide those easily enough. Because super custom images should be very limited for us

Unfortunately, I started working on other projects so it seems like I am not gonna have time to work on this PR any time soon. I will close the PR now because it is open for 3 months now and nobody showed interest in picking it up.


Add SPERR article to the publications page and a news post

Hi Sam,
Could you please add your SPERR article (when url is active) to the publications page.
This could also be a good topic for a news post. You just need an image and a short paragraph describing the topic. The contributors guid in the repository home page has information on how to add a news post. Lemme know if you have any questions.
Thanks!
Nihanth

Sure. I'll do it as soon as the complete information about this publication is available.

@shaomeng Hope your talk went well... If you think it is ready, should we revisit adding a short news article about SPERR to the VAST gallery? I say an article- but it is just a paragraph or two

also, could you add your IPDPS presentation to the 'presentation section' of this website. Thanks!

@NihanthCW Sure, I've submitted a presentation PR. Let's discuss what a post is going to look like; I'm not very sure ;)

@NihanthCW Sure, I've submitted a presentation PR. Let's discuss what a post is going to look like; I'm not very sure ;)

Sure, I am hoping this can also serve as an advert for your compression algorithm. So, maybe a paragraph outlining SPERR targeted towards an end-user along with a link to the project. I'll add this to tomorrow's meeting notes. Thanks!


Is is possible to train the rstar model using multiple GPUs?

I'm learning the theory and code of the rstar. But I find the training times takes a little longer.  Is is possible to train the action recognition rstar model using multiple GPUs?  Is the code support this parallelization?  If so, how can i modify the code?

The code as is does not support multi-GPU training. But it should be rather easy to incorporate it, using the Caffe multi-GPU implementation.
Training shouldn't be that slow. You should be able to train a PASCAL VOC model in less than a day. (Time is relative, so if you think <24h is slow then you're right, multi-GPU can speed it up!)


Fix pipeline detail doc typo

Fixed the gitlab_project_pipeline_detail doc missing the _detail suffix

Nice spot @embcla - thanks!


Added CompactH file

My first contribution !

Congratulations on creating your first GitHub contribution :sparkles::sparkles::sparkles:
Here's a bonus for you: GitHub Cheat Sheet
Do star :star: the repo and follow us on GitHub.
Join our FDC Group for more updates: https://www.facebook.com/groups/DevCVellore
Join FDC Vellore open community on WhatsApp: https://chat.whatsapp.com/IkD0qcCqvlo4hNlIMIzJ5q


Use strict null checks

Just to note: This is going to be a pest to work through but I genuinely believe it's necessary at the scale YesBot is at now.
https://github.com/Yes-Theory-Fam/yesbot-ts/blob/36dac2af9813c0863f4c789461fe4acf5b2a6a85/tsconfig.json#L14
The tsconfig defines "strictNullChecks": false which causes an absurd amount of potential runtime errors to not get picked up by the type checker. To fix this, delete that line from the tsconfig (strictNullChecks is enabled through strict in the line above) and go on a hunt for null/undefined errors and address them.

Suggestion: To not have to make the PR being gigantic and possibly have conflicts with other code changes, follow the incremental plan that VSCode used (or a similar approach) when they did the same for their codebase. https://code.visualstudio.com/blogs/2019/05/23/strict-null#_coming-up-with-an-incremental-plan
The whole article is a nice read. :-)


Update Examples.md

the strikethrough content maybe have already outdated.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: xp44mm:x: cuishenglicuishengli seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@CLAassistant

✅ xp44mm
❌ cuishengli
is same person. but cuishengli email is virtual. no way to add it.

Thanks for the PR / corrections :beers:!
Who is cuishengli?

Thanks for the changes :beers:!

maybe when i reset the commits, something was go wrong. my repo's file is as same as earlier.

maybe when i reset the commits, something was go wrong. my repo's file is as same as earlier, and i have reviewed myself. do you note that your window's top has yellow outdated?

Outdated on GitHub means that the review was done for an earlier version than the current state and that the respective position changed.
In this case all the review points I mentioned have changed, so all of these snippets are outdated.

thank you let my known those, next i will work correctly.


Add new parsec provider using ATECCx08 cryptochip via CryptoAuthentication Library

Definition of new structures and their interfaces.
Known issues
Version mismatch of psa-crypto
There is a version mismatch in a dependent library (psa-crypto) between parsec-interface and parsec on appropriate master/HEAD versions:

parsec-interface depends on git https://github.com/parallaxsecond/rust-psa-crypto#rev18dd4dda96d8b61d2e112b9e6ad83e90fe768d78
parsec depends on depends on official version 6.0.0 from crates.io

The solution is to

assign a new version to psa-crypto (git/hash) as discussed elsewhere
update the package meta-data on crates.io
use this new version in both parsec-interface and parsec

As a workaround this PR modifies parsec/Cargo.toml to have the same psa-crypto as a parsec-interface.
Wrong parsec-interface version number being used
The parsec-interface extension (add an CryptoAuthLib entry to providers' enumeration) was not followed by package version increase nor the package meta-data on crates.io was updated. This PR addressed an issue with parsec-interface version for parsec compilation purposes but there are still issues with e2e-tests.
Issues with e2e-tests
The e2e-tests depend on parsec-client that depends on parsec-interface and it is affected by the previously mentioned versioning issues.
Summary TODO points

[x] assign a new version to psa-crypto and update crate's meta-data on crates.io
[x] update both parsec and parsec-interface to use this new psa-crypto version
[x] assign a new version to parsec-interface and update its metadata on crates.io
[x] update parsec and parsec-client to use this new parsec-interface

Signed-off-by: Robert Drazkowski<EMAIL_ADDRESS>

Thanks for raising the PR - it's really exciting to see this stuff starting to arrive! And this is a perfectly-sized first change as well - just introducing the provider without its functions.
Before we can merge this in, I think we'll need to work a bit more on getting the dependency graph consistent. The CI actions are failing in this PR, and I think it's because there is a lack of consistency between how parsec-interface is being consumed into parsec and e2e_tests respectively. It's worth being aware that e2e_tests is an independent crate, even though its source code is nested within parsec. Like parsec, e2e_tests needs to consume parsec-interface, and it does so in a slightly disguised way, via its resurfacing through parsec-client-rust.
Confusing, I know!
The good news is that I think we can resolve the confusion quite easily by following some basic process. I think we need to create tagged releases of everything in the dependency chain, and then consume those releases in the Cargo.toml files instead of having specific Git references.
If we merge this PR as it is, it will cause the CI to fail, so it's worth sorting out ahead of time.
Starting from the ground up, and taking into account our Slack conversation as well as this PR. My proposal would be as follows, although I would also like to take advice on this from other engineers in the community, since I haven't been involved with the tagging/releasing process to date, and I want to make sure that what I'm proposing here is consistent with established practice.

Create a new tag/release on psa-crypto and set it as 0.6.1 since its functionality doesn't seem to have evolved significantly since the last tag.
Change parsec-interface-rs (via separate PR) to consume psa-crypto at 0.6.1 rather than its current git/hash reference.
Create a new tag/release on parsec-interface-rs and set it as 0.22.0.
Change parsec-client-rust (via separate PR) to consume parsec-interface-rs at its new tag level of 0.22.0.
Create a new tag/release on parsec-client-rust and set it as 0.12.0.
Update this PR with a new commit to consume psa-crypto at 0.6.1, parsec-interface-rs at 0.22.0 and parsec-client-rust at 0.12.0.

This should result in a cleanly-updated and consistent dependency graph, with everything consuming official versions rather than referencing commit hashes or head revisions. Referencing head revisions is a particular problem because it could mean that commits to other repos could actually randomly break things.

Yes, I fully agree, I was writing very similar proposal in PR top comment.
Is crates.io automatically updated after package version numbers are increased on github?

I'm not sure how the tagging process links with crates.io. Let me put out a query on the community channel and we'll find out. Ideally the process would be written up somewhere.

I have just pushed a newer version with updated dependencies version numbers as well as corrected config.toml contents as requested by Ionuț.

I have just pushed a newer version with updated dependencies version numbers as well as corrected config.toml contents as requested by Ionuț.

@paulhowardarm
You have requested a change, which I believe has already been addressed.
The only 'github' dependency is for "parsec-client' where github is updated but crates.io points on previous version.
I hope this is not an issue.

@paulhowardarm
You have requested a change, which I believe has already been addressed.
The only 'github' dependency is for "parsec-client' where github is updated but crates.io points on previous version.
I hope this is not an issue.


Top Level await parsing failes

Bug report
Enabling experiments.topLevelAwait and using the @babel/plugin-syntax-top-level-await for parsing .jsx files does not work, and throws error Error: Top-level-await is only supported in EcmaScript Modules

What is the current behavior?
With this config:
module.exports = {
    mode: 'production',
    entry: /* entries object, containing the .jsx files*/,
    output: {
        path: path.resolve(__dirname, `public/__js`),
        filename: '[name].js',
    },
    module: {
        rules: [{
            test: /(\.jsx|\.js)$/,
            include: path.resolve(__dirname, `src`),
            use: {
                loader: 'babel-loader',
                options: {
                    presets: ["@babel/preset-react", "@babel/preset-env"],
                    plugins: ["@babel/plugin-syntax-top-level-await"]
                }
            }
        },
       ]
    },
    resolve: {
        modules: [__dirname + '/node_modules'],
        extensions: ['.jsx', '.js'],
    },
    experiments: {
        futureDefaults: true,
        topLevelAwait: true
    },
    optimization: {
        mergeDuplicateChunks: true,
    }
}

using top-level await in the code throws an error
If the current behavior is a bug, please provide the steps to reproduce.
Since experiments.topLevelAwait is enabled, and the babel plugins are enabled, the error shouldn't appear

What is the expected behavior?
Webpack should not throw the Error: Top-level-await is only supported in EcmaScript Modules error and compile the files successfully

Other relevant information:
webpack version: 5.72.1
Node.js version: 18.2.0
Operating System: Debian 10
Additional tools:

Well I can say I solved the issue now, but with an unexpected outcome:
I noticed that the error was occurring only in files which did not have an import statement, so I went ahead and imported some random package in every file and now the error is gone. Still think that's a bug tho

Webpack by default considers a file without import or export statements to be commonjs module not EcmaScript Module.
You already found a way to mark each file individually, I recommend using export {}; because it's shorter.
Another way would be to set type: "javascript/esm" to your rule like so:
module.exports = {
    mode: 'production',
    entry: /* entries object, containing the .jsx files*/,
    output: {
        path: path.resolve(__dirname, `public/__js`),
        filename: '[name].js',
    },
    module: {
        rules: [{
            test: /(\.jsx|\.js)$/,
            include: path.resolve(__dirname, `src`),
            type: "javascript/esm",
            use: {

Beware, to set type: "javascript/esm" will, among other things, break any usage of CommonJS' require in those modules.

Yes, we considered to remove "javascript/auto" for webpck v5, but it will be big breaking change for developers, so we decide to postpone it

answered by @arthurdandrea 👍

if it is inside a "type": "module" package.json, I believe it effectively is a ES Module


fix(module): consider user tailwind configPath for module as string

🔗 Linked issue

Fixes #2035
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Conduct a sanitisation of configPath property before passing to defu.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks @ineshbose! 😊


Integration the Matrix room chat with StreamYard

This is not essential, but would be nice to have.
StreamYard has integrations for several chat systems, but not for Matrix.org

Did you manage to find documentation on how to integrate?

No. It seems we'd have to use one of the supported systems and replay chat entries there in order for StreamYard to pick them up. Not sure whether it's worth it.


ensure configuration interface uses consistent naming pattern

we want to make sure we're consistent in what we're naming our interfaces that application Configurations are implementing.
in this case, we're using the *Configurable pattern. in others, we're using *ConfigurationProvider.

+1 on *Configurable for shorter and simpler name. The problem with *ConfigurationProvider is that when multiple bundles are added to an app, the app configuration needs to implement multiple *ConfigurationProviders and it becomes harder to read.

i also believe the *Provider naming convention is a bit overloaded, especially if you end up adding some sort of DI framework.

Dropwizard's native bundle also uses the *Configurable Pattern, see
https://github.com/dropwizard/dropwizard/blob/d268137305915804a79d5cf2e42e6e03da44df10/dropwizard-views/src/main/java/io/dropwizard/views/ViewConfigurable.java

sticking to *Configurable


ci: upgrade cosmwasm-check according to latest upgrades

Make the contracts check linter align with the used VM & deps.

size-limit report 📦

Path
Size

target/wasm32-unknown-unknown/release/okp4_objectarium.wasm
438.71 KB (0%)

target/wasm32-unknown-unknown/release/okp4_law_stone.wasm
656.83 KB (0%)

target/wasm32-unknown-unknown/release/okp4_cognitarium.wasm
809.71 KB (0%)

target/wasm32-unknown-unknown/release/okp4_dataverse.wasm
226.24 KB (0%)