Minimise losing out on connection status updates when tab is not visible

Private link to related issue: https://microbit-global.monday.com/boards/1550536443/pulses/1687691747
Expected behaviour
When CreateAI tab is hidden we set the user-visible connection status as reconnecting. This is because the connection library currently disconnects when tab is hidden, and reconnects when tab is shown for radio connection (see delegatStatusListener). When the user returns to the tab, the user-visible connection status should reflect the latest status from the connection library and be back in sync.
Current behaviour
Currently, if the connection is lost whilst the tab is hidden and the user returns to the tab, the user-visible connection status is out of sync with the connection library's connection status.
Issue
The related issue occurs because we ignore connection status updates from the connection library when the tab is hidden (see here for where we don't update the connection status when isBrowserTabVisible is false).
We ignored the connection status when browser is hidden to address the issue of the radio connection loss dialog being visible when user returns to the CreateAI tab having switched away (see Rob's comment in https://github.com/microbit-foundation/ml-trainer/pull/341 and subsequent commit).
The fix in this PR involves:

Only ignoring connection status updates when it is a radio connection and the browser tab is hidden instead of ignoring connection status even when it is a bluetooth connection and browser tab is hidden

Updating to latest connection status from the connection library when user returns to the tab if radio connected

I find this change hard to understand. Can you write a bit more explanation (on the PR in the first instance) ?
Do you think there's something different we could do in the connection library to simplify the code here / remove special cases?

I find this change hard to understand. Can you write a bit more explanation (on the PR in the first instance) ?

Have added more explanation in the PR description. Hope that helps!

Do you think there's something different we could do in the connection library to simplify the code here / remove special cases?

Possibly? One way I can think of is if we introduced new connection status(es) that can distinguish between reason behind different disconnected states maybe (e.g. disconnected explicitly by user, connection loss, connect error, tab switching)? But on the other hand, I'm not sure if the connection library should be aware of these reasons if it was a general-use library

Possibly can handle another tab visibility issue as well (private link to issue: https://microbit-global.monday.com/boards/1550536443/pulses/1696956864)

Thanks for working through this one.


Cannot use primaryKeys to pass into bulkDelete in Angular 11

I am writing a generic function in Angular 11 to delete records based on a where clause. However, I am unable to pass the results of a .where(where).primaryKeys() to a bulkDelete:

Based on the docs, it seems like I should be able to use the primary keys array as the parameter for the bulk delete?
Currently working around it by setting keys to any[] which seems to work in Chrome.

This is a typing issue. PR welcome.


List tools and integrations that work with Flux

Not sure where to best place this, but we should list integrations and tools like

https://github.com/kaizentm/gitops-connector
https://github.com/fidelity/kraan

somewhere.

Also https://github.com/telekom/das-schiff

Also https://github.com/microsoft/fabrikate & https://github.com/microsoft/bedrock

https://github.com/weaveworks/weave-gitops

https://github.com/pelotech/jsonnet-controller


feat: subsequent identifies without passing identifier

Adds support for identify(body: [String:Any]) {} and identify(body: Encodable) {} which can be used after an initial identify has been called

:tada: This PR is included in version 1.0.0-alpha.22 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-beta.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Tasks in pending state get start event

Issue
The v2/app_usage_events API returns a start event for tasks in a pending state. If a client of cloud controller wishes to calculate the duration a task has been running, this results in an inaccurate answer.
Context
Normally, this isn't a problem, as typically tasks transition from the pending to running state quickly. However, in cases where a fast transition does not take place (typically an error), this means the runtime of a task as calculated by looking at the time of the start and stop events could be very off. Our system has sometimes had tasks stuck in a pending state for upwards of 90 days.
Steps to Reproduce
Create a task

curl v2/app_usage_events
Expected result
Should not return a TASK_STARTED event for the task.
Current result
It is returning a TASK_STARTED event for the task

I believe this was fixed by https://github.com/cloudfoundry/cloud_controller_ng/pull/1459.  Please reopen if that is not the case.


Allow php nightly build to fail

It's often interesting to see the code running against nightly but I'm not sure if there's much value to considering it as a "failure"

Good call! Thanks :)


Update .gitignore

Update .gitignore by using https://www.gitignore.io/api/c%2Cvim%2Cpython
This is useful to us because when I use virtual environments, I don't have to use git add in every files.
Also, there are many companies use gitignore.io https://github.com/joeblau/gitignore.io#companies.
I think this will good for this repo.
Thanks.

Thanks! 🍡

Thank you :)


MathML basic support

MathML is supported by default in the following browsers.

Mozilla Firefox
Safari

It is useful for several libraries not just related to browsers, so I include an example script to directly generate files. As a general rule, you can embed MathML within SVG, so you should define it in the SVG grammar.

I signed it!

IMO the best thing is to just leave it as it is (simple). If it is included by default, you will waste resources generating samples in other browsers such as Edge, Chrome or Brave. I have quite a few grammars (in my own fuzzer) and integrating them all is tedious, it is always better that each user decides how to integrate it if they target some specific browser (for example, being able to embed it within SVG or SVG within MathML or standalone).

OK, that's fine by me.
Please add the includes and fix the filename in parse_from_file as indicated in the inline comments and I'll merge it then.


Fixed : Added contribution section to Readme.md file.

Fixed #899
Added contributors to the Readme.md file.
@erikspears  @sid-swirl  kindly review it and merged the PR. Thank You!!

@erikspears please review my PR!

Thank you for the contribution, @Kalyanimhala  !
It turns out we cannot take it at this time.
Thank you,
--Erik


Fix broken tests when in GH actions

This is just a personal note to fix it tomorrow, it’s a known dependency issue I’ve had with another package of mine as well, so it’s a quick fix I’ll patch with a PR in the morning.

I was just looking at those - thank you!


Bug: Context menu more option text is not fully shown

What feature or improvement do you think would benefit Files?

The second dropdown menu is not displaying the full text, see attachment, the correct text is: Meer opties weergeven and it only displays: Meer opties weergever - the last letter is not displayed.
Requirements

This proposal will accomplish X
This proposal will accomplish Y
This proposal will accomplish Z

Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.4169
Comments
No response

Thanks for the report, What language are you using?

I am using Dutch (Netherlands/Netherlands).
Met vriendelijke groet,
Lawrence Vasseur |<PHONE_NUMBER>

Van: Josh65-2201 @.>
Verzonden: maandag 16 september 2024 15:09
Aan: files-community/Files @.>
CC: lfrvasseur @.>; Author @.>
Onderwerp: Re: [files-community/Files] Bug: Context menu more option text is not fully shown (Issue #16204)
Thanks for the report, What language are you using?
—
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/16204#issuecomment-2352875572, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BLKSBTXAXGILUAFCTVSTS53ZW3KBHAVCNFSM6AAAAABOJHZR76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSHA3TKNJXGI.
You are receiving this because you authored the thread.Message ID: @.***>

The problem is solved if you select one item but still exists if you select more than one item, see attachment.https://github.com/user-attachments/assets/2ac44f0f-1422-4753-a3c7-0b9540664d78


Use TransactionFailureReason as semantic validation error

FYI this is also done by #2046

We cool with the few instances of SemanticValidationFailed?

Yeah it's just failsafe but it should actually never happen


Base64-decoded secrets should not contain strictly ANSI alphanumeric, etc. data

This very likely indicates a false positive, eg., we have uncovered a base64-encoded URL that is provided as a query string parameter in an HTTP request (a real world case we encountered).
We should create a helper and call it during the static analysis phase for all relevant rules, returning 'no match' in cases where conditions aren't met (i.e., detecting one or more characters outside the latin unicode range).

@eddynaka


chore(build): fix system spec so that the current working directory is reset

Fixes issue with mocha-multi-reporter not being able to find options file - caused by system.spec.js not resetting the current working directory.

Coverage remained the same at 93.469% when pulling 1eaf2c8c25600d2a627a744bb0653a876e5f40c6 on fix/mocha-multi-reporters into f3f66be644692830d2b48a6f6ec2da7d8f1334c2 on master.


CI: start HA, test client-cli, without macos

duplicated from #43 but without macos because I already spent two evenings on it

once this is happy on ubuntu and still builds on macos, I need to squash massively

ready


Fixed bug in properties configuration.

The property flyway.placeholderReplacement wasn't being handled correctly in flyway-core.
If we use the maven plugin the property is set and the behaviour is the expected. Otherwise, don't.

Duplicate of #1233


Changes to SC election process for 2022

We got a late start on the election process this year, and I'd like to propose some other changes as well.

For nominations, I would like for the nominee to provide some background information that is available for voters as they make their decision. Maybe things like: Bio / background. OSPO role. Why you are running for the SC. What you want to accomplish as part of the SC. This year, I felt like I was voting blind without enough understanding of people's motivations and skills.
The charter states "nominations and voting during the month of September" for elections, so we should start talking about the process and what information we need from the nominees at the SC meetings in July / August.

We should also ask them to describe their previous contributions to the TODO Group.

+1 to both of these suggestions.

I also think that next year we should wait to announce the results of the election until we can also announce the appointed folks. One announcement of the full SC would probably be better, since we sometimes nominate people who ran in the election. It also cuts down on email noise and potential confusion.

For nominations, I would like for the nominee to provide some background information that is available for voters as they make their decision. Maybe things like: Bio / background. OSPO role. Why you are running for the SC. What you want to accomplish as part of the SC. This year, I felt like I was voting blind without enough understanding of people's motivations and skills

The charter states "nominations and voting during the month of September" for elections, so we should start talking about the process and what information we need from the nominees at the SC meetings in July / August.

LGTM. I've added an event at TODO Calendar for:

Start the SC Discussion (what info do the nominees need in order to participate, election days, etc) in the SC July monthly meeting

Make sure to have everything ready by September

Hey there, team. Looks like there's been a merge on this issue. Is there any more work to be done or can we close it?

nudge

Hey there, team. Looks like there's been a merge on this issue. Is there any more work to be done or can we close it?

@vmbrasseur -- https://github.com/todogroup/governance/pull/161 merged the waybackwhen content from https://github.com/todogroup/governance/pull/90, but does not include proposed changes from this issue.
Still on my plate! :)

Since the work's still in progress I'll move this issue to that column rather than Needs Review.

This is already being done via:

https://github.com/todogroup/governance/issues/221
https://github.com/todogroup/governance/issues/222

This is already being done (see my last comment) Closing this issue 🙂


Shift-Cmd-Z to redo on a Mac with a Dvorak keyboard layout doesn't redo

Hi Marijn!
To reproduce:

Go to codemirror.net
Enable the Dvorak keyboard layout.
Type some characters into the example CodeMirror editor on the homepage.
Press Cmd-Z to undo.
Press Shift-Cmd-Z to redo.  (Nothing happens.)
Select Redo from the Chrome Edit. (Nothing happens.)

Extra notes:

Mac OS X 10.11.1 (El Capitan).
Chrome 46.
Pressing Cmd-Y redoes correctly.
Using a US QWERTY keyboard layout stops the bug from occurring.

Thanks!

Are you pressing the key labeled Z or the one that Dvorak maps to Z? I'm guessing the former, since that seems to be how keydown event keycodes work.
The mapping from key events to bindings is relatively straightforward. Have you checked whether a sensible event is generated in this case? What does CodeMirror.keyName return when called on the event?

Thanks a lot for your response!
For your first question: I'm pressing the key Dvorak maps to z (on a keyboard with US QWERTY keycap markings, this is marked as /).
I can't answer your second question, I'm afraid.  See below for why!
I went to the CodeMirror homepage in Chrome and executed the following code in the console:
window.onkeydown = function(e) {
  console.log(e)
};

I then put the caret into the CodeMirror textarea near the top of the page and pressed the key combos below.
If I press the key bound to z on it's own (on a keyboard with US Qwerty keycap markings this is marked with /), a KeyboardEvent is logged that has a keyCode attribute of 90 (which is reported by http://keycode.info to be the keyCode for z.  All as expected.
However, if I press Shift-Command-Z I get two events (not the expected three):
KeyboardEvent 1: keyCode of 16 (keycode.info reports this as the shift key).
KeyboardEvent 2: keyCode of 91 (keycode.info reports this an the left command key).
Note that no event for the z key being pressed was emitted.
As an experiment, I pressed Shift-Command-V and got the expected three events:
KeyboardEvent 1: keyCode of 16 (keycode.info reports this as the shift key).
KeyboardEvent 2: keyCode of 91 (keycode.info reports this as the left command key).
KeyboardEvent 3: keyCode of 86 (keycode.info reports this as v).
Is this helpful?

Yes, but it suggests that Chrome is not firing an event at all for the Z press in Shift-Cmd-Z, which means CodeMirror also can't handle any event. (I expect you'll see the same if you don't focus or even load CodeMirror).
Does a key event get fired when you disable Dvorak layout and then press Shift-Cmd-Z? What about Shift-Cmd-slash?

I switched from Dvorak to a US QWERTY keyboard mapping and tried the key combos.

For Shift-Command-Z, the expected three events get fired.
For Shift-Command-/, a event gets fired for Shift and an event gets fired for command, but no event gets fired for the /.  Instead, the Chrome Help menu appears!

Further, I think you're right that no key event gets fired for the z in Shift-Command-Z in Dvorak. I made a test textarea (without CodeMirror) here: http://maryrosecook.com/textareaexample.html It includes code that binds to keydown events on the textarea.  In Dvorak mode, when I press Shift-Command-Z, only the events for shift and command get fired.
Should I file a bug on Chrome?

This does indeed sound like a Chrome bug (or even an OS X bug -- did you test another browser?). So reporting it elsewhere sounds like a good idea. As for CodeMirror -- I'm closing this, since it sounds like  there really is no way to fix this on my side.

Yes I tested in Safari and it works fine.  It may just be Chrome.  Thanks a lot for looking into it!


Question regarding recommended contig lengths

Just wondered if there is any guidance on what to aim for as far as contig sizes for using AGOUTI. This applies more specifically to the ab initio gene predictions, which will obviously be worse with smaller contig sizes, but is also a consideration with using these models to run AGOUTI. Any insights are much appreciated.

Hello Daren,
This is a great and definitely an open question.
Assemblers create many these small contigs from 100bp to 1kb, sometimes even less than 100bp. In my opinion, the smallest contigs for AGOUTI needs to be at least longer than the read length just for the sake of reliable read-mapping. However, this requires a bit caution to do, as the many of these small floating pieces in the assemblies are products of genomic regions of high heterozygosity, low complexity, etc. This means that you can have two copies of the same gene: one on a larger contigs, and the other one on a smaller one (in case of one heterozygous loci being split into two loci because the assemblers cannot distinguish). If such case happens, AGOUTI will erroneously merge these two split gene models into one. So far for all the simulated and real datasets I have been playing with, I use AGOUTI on contigs with a minimum of 1kb long. This choice follows what ALLPATHSLG uses.
I have had one immature idea (and a pretty naive one) for a while to benchmark on this. Instead of making the hard cut at a certain length and ignore all the contigs shorter than the cutoff, I think it would be better to choose multiple cutoffs. Please see the following procedure:
For (cutoff=200; cutoff<=1kb, cutoff+=100)
do
take the set of sequences no more than 200;
align these sequences to the rest sequences in the assembly;
examine how many of them have hits on the rest of the assembly;
End loop
Then I'd say to pick the cutoff that have the lowest number of hits, and therefore running gene prediction on these sequences is less likely to have the same gene models somewhere else in the assembly.
I hope this makes a bit sense. Let me know.
Also thanks for using AGOUTI.
Simo

hello @darencard, feel free to reopen this if you have further questions.


RCTAppDelegate.h file not found

Description
I have updated my RN app from 0.70.6 to 0.71.4. The pod install working well. But when I'm trying to run the app it gave me the error saying RCTAppDelegate.h file not found.
But I hadn't problems with android running
React Native Version
0.71.4
Output of npx react-native info
System:
OS: macOS 13.2.1
CPU: (10) arm64 Apple M1 Max
Memory: 732.19 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.14.1 - /usr/local/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.5.0 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.2 AI-212.5712.43.2112.8609683
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 11.0.15 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.4 => 0.71.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
just need to run run ios
Snack, code example, screenshot, or link to a repository
Sorry it's a private repo, and I can't share the code with you

I found the issue, it was connected with an m1 chip, on intel, and on a real device it works normally

I found the issue, it was connected with an m1 chip, on intel, and on a real device it works normally

having the same issue here, did you figure out how to fix with an M1 or just worked with Intel?

yea I'm not sure what was the real problem, but deleting podfile.lock, pods, build and removing cache helped

thanks for answering! unfortunately here no way to make it work, tried all that and still with problems 😭

same problem, hope to find help...

I give a try again following these steps again and using Xcode that build was still failing, but when trying to run directly the react-native run-ios command it has built successfully and worked.

This solution on stackoverflow helped me solve this problem. https://stackoverflow.com/questions/71933392/react-native-ios-undefined-symbols-for-architecture-x86-64

I was getting this error. I had created a new target, and that target wasn't in my Podfile. It disappeared after adding
target 'MyNewTarget' do
  inherit! :complete
end

within the larger target.

same issue 🥲

Same issue on M1
"react": "18.2.0",
"react-native": "0.71.7"

I'm getting this issue as well

I got it fixed by following a console warning when building with scratch configuration on my Podfile,
Instead of adding
use_frameworks! :linkage => :static (as suggested on react native firebase package docs)
I added
use_modular_headers!
just above the target initialization line,
Hope this works for you too

I was able to fixed this issue with by making sure use_frameworks! :linkage => :static was above use_react-native
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
$RNFirebaseAsStaticFramework = true

platform :ios, min_ios_version_supported
deployment_target = '13.0'
prepare_react_native_project!
# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'AppName' do
  config = use_native_modules!

  # Flags change depending on the env values.
  flags = get_default_flags()

  # This has to come before use_react_native or you get AppDelegate or RCTEventEmitter not found
  use_frameworks! :linkage => :static

  use_react_native!(
    :path => config[:reactNativePath],
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

end

I added
use_modular_headers!
just above the target initialization line,

@callmesilva Is this use_modular_headers safe to use? Could it be away to get around the fact that use_frameworks is not supported on the new architecture?

I was able to fixed this issue with by making sure use_frameworks! :linkage => :static was above use_react-native
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
$RNFirebaseAsStaticFramework = true

platform :ios, min_ios_version_supported
deployment_target = '13.0'
prepare_react_native_project!
# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'AppName' do
  config = use_native_modules!

  # Flags change depending on the env values.
  flags = get_default_flags()

  # This has to come before use_react_native or you get AppDelegate or RCTEventEmitter not found
  use_frameworks! :linkage => :static

  use_react_native!(
    :path => config[:reactNativePath],
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

end

I added
use_modular_headers!
just above the target initialization line,

@callmesilva Is this use_modular_headers safe to use? Could it be away to get around the fact that use_frameworks is not supported on the new architecture?

I tried the use_frameworks! :linkage => :static way but it was causing my app to miss the RCTAppDelegate.h file. Perhaps it is supported because it allowed me to install Firebase related pods, but somehow it was messing with the actual React Native package

Facing the same issue, Any Workaround is there yet?

same issue 🥲
upgraded from 0.63.5  to 0.71.7,

I am still getting the same error  can anyone please suggest? my react-native version is 0.71.7

Me too, same issue!
Although, I see React-RCTAppDelegate on Development Pods

But still not found.
Already do this https://github.com/facebook/react-native/issues/35818#issuecomment-1536291846, but still same issue.
I'm using https://github.com/invertase/react-native-firebase, and my RN version is 0.71.8

@keshav-raj  @Prathameshlabde @riyan10dec
Please, try the following steps:

Update to the most recent version of React Native (0.71.11).
Run yarn install in the root folder of your app
In the ios folder, run bundle install. This ensure that you have the right versions of Cocoapods and should make sure that cocopods works with both Intel and M1 chips
Reinstall your pods:

If you are using firebase, use USE_FRAMEWORKS=static bundle exec pod install
If you are not using firebase, use bundle exec pod install

Open your <app>.xcworkspace
Try to build and run the app

I hope these steps may help solving your issues.

Hi @cipolleschi ,
thanks for your response.
after I try your steps, when I build on XCode, I'm getting this error:
Command PhaseScriptExecution failed with a nonzero exit code

This is my Podfile, in case you need to see
source 'https://cdn.cocoapods.org/'

require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
$RNFirebaseAsStaticFramework = true

platform :ios, min_ios_version_supported
prepare_react_native_project!
# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'Influence' do
  config = use_native_modules!
  # permissions_path = '../node_modules/react-native-permissions/ios'
  # pod 'Permission-AppTrackingTransparency', :path => "#{permissions_path}/AppTrackingTransparency"
  # pod 'Permission-MediaLibrary', :path => "#{permissions_path}/MediaLibrary"
  # pod 'Permission-PhotoLibrary', :path => "#{permissions_path}/PhotoLibrary"
  # pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"

  # Flags change depending on the env values.
  flags = get_default_flags()

  use_frameworks! :linkage => :static
  # $RNFirebaseAsStaticFramework = true
  use_react_native!(
    :path => config[:reactNativePath],
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
    # Hermes is now enabled by default. Disable by setting this flag to false.
    # Upcoming versions of React Native may rely on get_default_flags(), but
    # we make it explicit here to aid in the React Native upgrade process.
    # :hermes_enabled => false,
    # :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    # :flipper_configuration => flipper_config,
  )

  target 'InfluenceTests' do
    inherit! :complete
    # Pods for testing
  end

  post_install do |installer|
    react_native_post_install(
      installer,
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

#   # Fix Xcode 14 warnings like:
#   # warning: Run script build phase '[CP] Copy XCFrameworks' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'ATargetNameHere' from project 'YourProjectName')
#   # Ref.: https://github.com/CocoaPods/CocoaPods/issues/11444
#   post_integrate do |installer|
#     main_project = installer.aggregate_targets[0].user_project
#     pods_project = installer.pods_project
#     targets = main_project.targets + pods_project.targets
#     targets.each do |target|
#       run_script_build_phases = target.build_phases.filter { |phase| phase.is_a?(Xcodeproj::Project::Object::PBXShellScriptBuildPhase) }
#       cocoapods_run_script_build_phases = run_script_build_phases.filter { |phase| phase.name.start_with?("[CP]") }
#       cocoapods_run_script_build_phases.each do |run_script|
#         next unless (run_script.input_paths || []).empty? && (run_script.output_paths || []).empty?
#         run_script.always_out_of_date = "1"
#       end
#     end
#     main_project.save
#     pods_project.save
#   end
end

Hi @riyan10dec, just to understand, the error:
line 3: $(CURRENT_PROJECT_VERSION) + 1: syntax error: operand expected (error token is "$(CURRENT_PROJECT_VERSION) + 1")
Command PhaseScriptExecution failed with a nonzero exit code

Is local to your configuration, right? I have never seen the $(CURRENT_PROJECT_VERSION) + 1 anywhere in the React Native codebase...

@cipolleschi
Maybe from this lib (I'm using this lib to auto increment the build number, everytime i build APK and IPA file):
https://github.com/stovmascript/react-native-version
My solution is to revert CURRENT_PROJECT_VERSION and MARKETING_VERSION on Info.plist to hardcoded version number

any updates on this?
here's my Podfile. I tried with use_frameworks first but then I get other errors. With the current Podfile, I get this one RCTAppDelegate.h file not found. I also tried installing pods from scratch, with cleaned everything.
# Resolve react_native_pods.rb with node to allow for hoisting
# .../ios/Pods/Headers/Private/RCT-Folly/folly/portability/Time.h:52:17: Typedef redefinition with different types ('uint8_t' (aka 'unsigned char') vs 'enum clockid_t') -
# https://developer.apple.com/forums/thread/719022?answerId=736411022#736411022

require Pod::Executable.execute_command('node', ['-p',
  'require.resolve(
    "react-native/scripts/react_native_pods.rb",
    {paths: [process.argv[1]]},
  )', __dir__]).strip

platform :ios, min_ios_version_supported
prepare_react_native_project!

# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'MyApp' do
  config = use_native_modules!

  # Flags change depending on the env values.
  flags = get_default_flags()

  # use_frameworks!
#  use_frameworks! :linkage => :static
  use_modular_headers!

  # exquisite PODS
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec', :modular_headers => false
#   pod 'RCT-Folly', :podspec => '../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec', :modular_headers => false
#   pod 'libevent', :git => 'https://github.com/libevent/libevent.git', :commit => 'e339880'

   dynamic_frameworks = ['CustomerlySDK', 'ObjectMapper', 'Kingfisher', 'Socket.IO-Client-Swift', 'Starscream' ]
    pre_install do |installer|
      installer.pod_targets.each do |pod|
        if !dynamic_frameworks.include?(pod.name)
          puts "Overriding the static_framework method for - #{pod.name}"
          def pod.static_framework?;
            true
          end
          def pod.build_type;
            Pod::BuildType.static_library
          end
        end
      end
    end

  # react-native-permissions
  permissions_path = '../node_modules/react-native-permissions/ios'
  pod 'Permission-Camera', :path => "#{permissions_path}/Camera"
  pod 'Permission-Notifications', :path => "#{permissions_path}/Notifications"
  pod 'Permission-PhotoLibrary', :path => "#{permissions_path}/PhotoLibrary"
  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  $RNFirebaseAsStaticFramework = true

  post_install do |installer|
     # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
	 `sed -i -e  $'s/__IPHONE_10_0/__IPHONE_12_0/' Pods/RCT-Folly/folly/portability/Time.h`
      react_native_post_install(
      	installer,
      	config[:reactNativePath],
      	:mac_catalyst_enabled => false
     )
      installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = min_ios_version_supported
  		# config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET'
          config.build_settings['DEVELOPMENT_TEAM'] = 'KUY7D29958'
          config.build_settings['CODE_SIGN_STYLE'] = 'Manual'
          config.build_settings['CODE_SIGN_IDENTITY'] = 'Apple Development'
        end
       end
  	installer.pods_project.build_configurations.each do |config|
  		config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = min_ios_version_supported
  	end
    end

  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    :hermes_enabled => true,
    :fabric_enabled => flags[:fabric_enabled],
 	# Enables Flipper.
	# Note that if you have use_frameworks! enabled, Flipper will not work and
	# you should disable the next line.
	#   :flipper_configuration => flipper_config,
	# An absolute path to your application root.
	:app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  target 'MyAppTests' do
    inherit! :complete
    # Pods for testing
  end

  # Enables Flipper.
  #
  # Note that if you have use_frameworks! enabled, Flipper will not work and
  # you should disable these next few lines.
#   use_flipper!()

end

target 'ImageNotification' do
#   use_frameworks! :linkage => :static
  use_modular_headers!
  pod 'Firebase', :modular_headers => true
  pod 'FirebaseCore', :modular_headers => true
  pod 'GoogleUtilities', :modular_headers => true
  $RNFirebaseAsStaticFramework = true
  pod 'Firebase/Messaging'
end

For those who still have this issue, first make sure you opened "projectName".xcworkspace and not "projectName".xcodeproj with XCode.

If after trying all of the above and you are able to run on a real device, but not the simulator; try checking that the project, targets and pods build settings Excluded Architectures - Any iOS Simulator SDK are set to i386.
My project build settings had it set to i386, but targets build settings had it set to arm64. I changed it to i386 for all and was able to run on a simulator.
Also you might have this in your Podfile if you are upgrading from an older react native project. This sets it back to arm64 after each pod install. Remove this as well.
installer.pods_project.build_configurations.each do |config|
  config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end

If you are using React Native Config, please check the Podfile.
You must define the target inside the abstract_target
ex:
`abstract_target 'YourProjectNameCommonPods' do
config = use_native_modules!
...
target 'YourTargetName' do
end
...
post_install do |installer|...
`

@cipolleschi  hi, all the solution3 above i tried but still has the issue。can you help me fix it, here is my podfile
`# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
platform :ios, '14.0'
source 'https://github.com/CocoaPods/Specs.git'
prepare_react_native_project!
If you are using a react-native-flipper your iOS build will fail when NO_FLIPPER=1 is set.
because react-native-flipper depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude react-native-flipper using a react-native.config.js
```js
module.exports = {
dependencies: {
...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'AuthCoreWalletDemo' do
config = use_native_modules!
use_frameworks! :linkage => :static
Flags change depending on the env values.
flags = get_default_flags()
use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
:hermes_enabled => false,#flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
# :flipper_configuration => flipper_config,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
  pod 'AuthCoreAdapter', '0.1.9'
  pod 'ParticleAuthCore', '0.1.9'
  pod 'ParticleMPCCore', '0.1.9'
  pod 'Thresh', '0.1.9'

  pod 'ParticleWalletGUI', '1.0.2'
  pod 'ParticleWalletAPI', '1.0.2'
  pod 'ParticleNetworkBase', '1.0.2'
  pod 'ParticleAuthService', '1.0.2'
  pod 'ParticleWalletConnect', '1.0.2'
  pod 'ParticleBiconomy', '1.0.2'

  pod 'ParticleConnect',  '0.2.8'
  pod 'ConnectWalletConnectAdapter',  '0.2.8'
  pod 'ConnectEVMAdapter',  '0.2.8'
  pod 'ConnectSolanaAdapter',  '0.2.8'
  pod 'ConnectPhantomAdapter',  '0.2.8'
  pod 'ConnectCommon',  '0.2.8'
  pod 'ParticleAuthAdapter',  '0.2.8'

  pod 'SkeletonView', :git => 'https://github.com/SunZhiC/SkeletonView.git', :branch => 'main'
  pod 'SwiftMessages', :git => 'https://github.com/SunZhiC/SwiftMessages', :branch => 'master'

target 'AuthCoreWalletDemoTests' do
inherit! :complete
# Pods for testing
end
post_install do |installer|
# https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
react_native_post_install(
installer,
config[:reactNativePath],
:mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
  config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
    end
  end

# This is necessary for Xcode 14, because it signs resource bundles by default
# when building for devices.
installer.target_installation_results.pod_target_installation_results
.each do |pod_name, target_installation_result|
  target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
    resource_bundle_target.build_configurations.each do |config|
      config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
    end
  end
end

  installer.generated_projects.each do |project|
    project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '14.0'
         end
    end
  end

    installer.pods_project.build_configurations.each do |config|
      config.build_settings['VALID_ARCHS'] = 'arm64, arm64e, x86_64'
    end
end

end`

@cipolleschi  hi, all the solution3 above i tried but still has the issue。can you help me fix it, here is my podfile
# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
  'require.resolve(
    "react-native/scripts/react_native_pods.rb",
    {paths: [process.argv[1]]},
  )', __dir__]).strip

platform :ios, '14.0'
source 'https://github.com/CocoaPods/Specs.git'
prepare_react_native_project!

# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'AuthCoreWalletDemo' do
  config = use_native_modules!
  use_frameworks! :linkage => :static
  # Flags change depending on the env values.
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    :hermes_enabled => false,#flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    # :flipper_configuration => flipper_config,
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

      pod 'AuthCoreAdapter', '0.1.9'
      pod 'ParticleAuthCore', '0.1.9'
      pod 'ParticleMPCCore', '0.1.9'
      pod 'Thresh', '0.1.9'

      pod 'ParticleWalletGUI', '1.0.2'
      pod 'ParticleWalletAPI', '1.0.2'
      pod 'ParticleNetworkBase', '1.0.2'
      pod 'ParticleAuthService', '1.0.2'
      pod 'ParticleWalletConnect', '1.0.2'
      pod 'ParticleBiconomy', '1.0.2'

      pod 'ParticleConnect',  '0.2.8'
      pod 'ConnectWalletConnectAdapter',  '0.2.8'
      pod 'ConnectEVMAdapter',  '0.2.8'
      pod 'ConnectSolanaAdapter',  '0.2.8'
      pod 'ConnectPhantomAdapter',  '0.2.8'
      pod 'ConnectCommon',  '0.2.8'
      pod 'ParticleAuthAdapter',  '0.2.8'

      pod 'SkeletonView', :git => 'https://github.com/SunZhiC/SkeletonView.git', :branch => 'main'
      pod 'SwiftMessages', :git => 'https://github.com/SunZhiC/SwiftMessages', :branch => 'master'

  target 'AuthCoreWalletDemoTests' do
    inherit! :complete
    # Pods for testing
  end

  post_install do |installer|
    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
    react_native_post_install(
      installer,
      config[:reactNativePath],
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)

    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
      config.build_settings['BUILD_LIBRARY_FOR_DISTRIBUTION'] = 'YES'
        end
      end

    # This is necessary for Xcode 14, because it signs resource bundles by default
    # when building for devices.
    installer.target_installation_results.pod_target_installation_results
    .each do |pod_name, target_installation_result|
      target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
        resource_bundle_target.build_configurations.each do |config|
          config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    end

      installer.generated_projects.each do |project|
        project.targets.each do |target|
            target.build_configurations.each do |config|
                config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '14.0'
             end
        end
      end

        installer.pods_project.build_configurations.each do |config|
          config.build_settings['VALID_ARCHS'] = 'arm64, arm64e, x86_64'
        end
    end
end

@tuguilin1 from your podfile, I can see you have a lot of custom Pod dependencies.
Are they react native dependencies or iOS only ones?
RN dependencies must be installed through yarn add <dependency name> as, otherwise, the autolinking mechanism may fail.
Secondly, can you show the Xcode error you are encountering?

Got the same issue as soon as I enable static linking. I did everything as described here but could not manage to make it build on iOS. Always get 'React-RCTAppDelegate/RCTAppDelegate.h' file not found. I'm on react native 0.72.4 btw.

@uloco, can you please provide a repro using this repo as a template?

Looks like it was some import order problem. We also import another dependency in AppDelegate.h, called #import <UserNotifications/UNUserNotificationCenter.h>, which was imported before #import <RCTAppDelegate.h>  (It's from this repo: https://github.com/react-native-push-notification/ios.
After putting RCTAppDelegate.h to the very top, it started working again.
Also I replaced React-RCTAppDelegate/RCTAppDelegate.h with just <RCTAppDelegate.h>, don't know if this made any difference though.

target 'MyNewTarget' do
inherit! :complete
end

Thank you so much for this... It worked perfectly

Currently, I'm facing this too, and I have compared a new project vs. https://github.com/mikehardy/rnfbdemo/tree/main vs. my project.
I'm noticing something that may cause the issue, but not sure what this means, when checking the section "General" -> "Frameworks, Libraries, and Embedded Content", normally, it uses libPods-[project_name].a but mine has Pods_[project_name].framework.
I was wondering, what do you have there and what's the difference, how does this was created?
I've tried using RN 0.72.3 and 0.72.4, not sure about previous releases

Hi @jackfiallos!
The reason why you have .framework instead of a .a is because you are configuring your project to run with use_frameworks! rather than static libraries.
So, Cocoapods creates frameworks instead of libraries (.a) and therefore the linking of external libraries is done using those.

Thanks for clarifying @cipolleschi, that's what I thought ..
In the end, I could manage the error, tried different things and finally, it's working again, I believe my error was in the Podfile because it wasn't updated correctly. Also, I had a mix of different setups from other libraries that weren't updated so had configs from different versions. I think one of the misconfigurations was causing the issue with the project compilation.
I'm not sure what the issue was, but I'll suggest anybody having this problem, to check all your custom libraries and see if the configuration still applies to your current RN version.
Something to add is, the most important thing to verify is your Gemfile.lock file that effectively has:
DEPENDENCIES
  cocoapods (~> 1.12)

and before testing, remove from your root project, /vendor folder Gemfile.lock file and from ios folder, /Pods and Podfile.lock.
execute the bundle install and the pod install --repo-update (arch -x86_64 pod install --repo-update for M1/2 processors).

same issue. upgrading from 0.66.5 to 0.72.4

@feedthedevil it is likely that it depends on your Podfile or on some 3rd party dependency.
Have a look at the conversation, there are various fixes, depending on different podfile setups and libraries involved.
As a first step, try to have your Podfile as close as possible to this one

@cipolleschi thank you for reply. The problem was on my side. I was upgrading by changing files finding differences via upgrade-helper and somehow in my AppDelegate.h i was importing RCTAppDelegate.h as React/RCTAppDelegate.h ;) Leaving just RCTAppDelegate.h helped to resolve the issue)

I am experiencing the same issue, RN 0.70.6 --> 0.72.5
Apple Silicon M1
here is my podfile
`# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
platform :ios, min_ios_version_supported
prepare_react_native_project!
If you are using a react-native-flipper your iOS build will fail when NO_FLIPPER=1 is set.
because react-native-flipper depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude react-native-flipper using a react-native.config.js
```js
module.exports = {
dependencies: {
...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'WolffMobile' do
config = use_native_modules!
Flags change depending on the env values.cd ..
flags = get_default_flags()
use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
:hermes_enabled => flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
:flipper_configuration => flipper_config,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
target 'WolffMobileTests' do
inherit! :complete
# Pods for testing
end
target 'WolffMobileDev' do
inherit! :complete
end
target 'WolffMobileStg' do
inherit! :complete
end
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = "arm64"
end
end
# https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
react_native_post_install(
installer,
config[:reactNativePath],
# Set mac_catalyst_enabled to true in order to apply patches
# necessary for Mac Catalyst builds
:mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end
end`

I am experiencing the same issue, RN 0.70.6 --> 0.72.5
Apple Silicon M1
I have tried every recommendation in this thread with no luck.
Any suggestions would be greatly appreciated
here is my podfile:
# Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
  'require.resolve(
    "react-native/scripts/react_native_pods.rb",
    {paths: [process.argv[1]]},
  )', __dir__]).strip

platform :ios, min_ios_version_supported
prepare_react_native_project!

# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...) that will be excluded
#
# To fix this you can also exclude `react-native-flipper` using a `react-native.config.js`
# ```js
# module.exports = {
#   dependencies: {
#     ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# ```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

target 'WolffMobile' do
  config = use_native_modules!

  # Flags change depending on the env values.cd ..
  flags = get_default_flags()

  use_react_native!(
    :path => config[:reactNativePath],
    # Hermes is now enabled by default. Disable by setting this flag to false.
    :hermes_enabled => flags[:hermes_enabled],
    :fabric_enabled => flags[:fabric_enabled],
    # Enables Flipper.
    #
    # Note that if you have use_frameworks! enabled, Flipper will not work and
    # you should disable the next line.
    :flipper_configuration => flipper_config,
    # An absolute path to your application root.
    :app_path => "#{Pod::Config.instance.installation_root}/.."
  )

  target 'WolffMobileTests' do
    inherit! :complete
    # Pods for testing
  end
  target 'WolffMobileDev' do
    inherit! :complete
  end
  target 'WolffMobileStg' do
    inherit! :complete
  end

  post_install do |installer|
    installer.pods_project.targets.each do |target|
      target.build_configurations.each do |config|
          config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.4'
          config.build_settings['EXCLUDED_ARCHS[sdk=iphonesimulator*]'] = "arm64"
        end
    end
    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
    react_native_post_install(
      installer,
      config[:reactNativePath],
      # Set `mac_catalyst_enabled` to `true` in order to apply patches
      # necessary for Mac Catalyst builds
      :mac_catalyst_enabled => false
    )
    __apply_Xcode_12_5_M1_post_install_workaround(installer)
  end

end

I am also trying to fix this error, followed all steps but bug still exists. Occurred when upgrading rn 0.72.5.
here is my pod file:
`$RNFirebaseAsStaticFramework = true
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/react-native-unimodules/cocoapods.rb'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '13.0'
deployment_target = '13.0'
require 'json'
podfile_properties = JSON.parse(File.read('./Podfile.properties.json')) rescue {}
Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
If you are using a react-native-flipper your iOS build will fail when NO_FLIPPER=1 is set.
because react-native-flipper depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude react-native-flipper using a react-native.config.js
```js
module.exports = {
dependencies: {
...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'prmassist' do
use_expo_modules!
config = use_native_modules!
flags = get_default_flags()
use_frameworks! :linkage => :static
use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
:hermes_enabled => flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
#:flipper_configuration => flipper_config,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."

)
Uncomment the code below to enable Flipper.

You should not install Flipper in CI environments when creating release
builds, this will lead to significantly slower build times.

Note that if you have use_frameworks! enabled, Flipper will not work.

use_flipper!
post_install do |installer|
flipper_post_install(installer)
end
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-async-storage/async-storage'
pod 'BVLinearGradient', :path => '../node_modules/react-native-linear-gradient'
add the Firebase pod for Google Analytics
pod 'Firebase/Analytics'
Add the pod for Firebase Cloud Messaging
pod 'Firebase/Messaging'
pod 'lottie-react-native', :path => '../node_modules/lottie-react-native'
pod 'lottie-ios', :path => '../node_modules/lottie-ios'
pod 'RNSVG', :path => '../node_modules/react-native-svg'
pod 'RCT-Folly', :podspec => '../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec'
options
pod 'Permission-AppTrackingTransparency', :path => "#{permissions_path}/AppTrackingTransparency"
pod 'Permission-BluetoothPeripheral', :path => "#{permissions_path}/BluetoothPeripheral"
pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
post_install do |installer|
# https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
react_native_post_install(
  installer,
  config[:reactNativePath],
  :mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)

installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
    config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
    config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
  end
end

# Workaround `Cycle inside FBReactNativeSpec` error for react-native 0.64
# Reference: https://github.com/software-mansion/react-native-screens/issues/842#issuecomment-812543933
installer.pods_project.targets.each do |target|
  if (target.name&.eql?('FBReactNativeSpec'))
    target.build_phases.each do |build_phase|
      if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
        target.build_phases.move(build_phase, 0)
      end
    end
  end
end

end
post_integrate do |installer|
begin
expo_patch_react_imports!(installer)
rescue => e
Pod::UI.warn e
end
end
end
`

I am also trying to fix this error, followed all steps but bug still exists. Occurred when upgrading rn 0.72.5.
`
$RNFirebaseAsStaticFramework = true
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/react-native-unimodules/cocoapods.rb'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '13.0'
deployment_target = '13.0'
require 'json'
podfile_properties = JSON.parse(File.read('./Podfile.properties.json')) rescue {}
Resolve react_native_pods.rb with node to allow for hoisting
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
If you are using a react-native-flipper your iOS build will fail when NO_FLIPPER=1 is set.
because react-native-flipper depends on (FlipperKit,...) that will be excluded

To fix this you can also exclude react-native-flipper using a react-native.config.js
```js
module.exports = {
dependencies: {
...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
```
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'prmassist' do
use_expo_modules!
config = use_native_modules!
flags = get_default_flags()
use_frameworks! :linkage => :static
use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
:hermes_enabled => flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
#:flipper_configuration => flipper_config,
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."

)
Uncomment the code below to enable Flipper.

You should not install Flipper in CI environments when creating release
builds, this will lead to significantly slower build times.

Note that if you have use_frameworks! enabled, Flipper will not work.

use_flipper!
post_install do |installer|
flipper_post_install(installer)
end
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-async-storage/async-storage'
pod 'BVLinearGradient', :path => '../node_modules/react-native-linear-gradient'
add the Firebase pod for Google Analytics
pod 'Firebase/Analytics'
Add the pod for Firebase Cloud Messaging
pod 'Firebase/Messaging'
pod 'lottie-react-native', :path => '../node_modules/lottie-react-native'
pod 'lottie-ios', :path => '../node_modules/lottie-ios'
pod 'RNSVG', :path => '../node_modules/react-native-svg'
pod 'RCT-Folly', :podspec => '../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec'
options
pod 'Permission-AppTrackingTransparency', :path => "#{permissions_path}/AppTrackingTransparency"
pod 'Permission-BluetoothPeripheral', :path => "#{permissions_path}/BluetoothPeripheral"
pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
post_install do |installer|
# https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
react_native_post_install(
  installer,
  config[:reactNativePath],
  :mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)

installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
    config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
    config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
  end
end

# Workaround `Cycle inside FBReactNativeSpec` error for react-native 0.64
# Reference: https://github.com/software-mansion/react-native-screens/issues/842#issuecomment-812543933
installer.pods_project.targets.each do |target|
  if (target.name&.eql?('FBReactNativeSpec'))
    target.build_phases.each do |build_phase|
      if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
        target.build_phases.move(build_phase, 0)
      end
    end
  end
end

end
post_integrate do |installer|
begin
expo_patch_react_imports!(installer)
rescue => e
Pod::UI.warn e
end
end
end
`

I am also trying to fix this error, followed all steps but bug still exists. Occurred when upgrading rn 0.72.5.
`$RNFirebaseAsStaticFramework = true
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/react-native-unimodules/cocoapods.rb'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '13.0'
deployment_target = '13.0'
require 'json'
podfile_properties = JSON.parse(File.read('./Podfile.properties.json')) rescue {}
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'prmassist' do
use_expo_modules!
config = use_native_modules!
flags = get_default_flags()
use_frameworks! :linkage => :static
use_react_native!(
:path => config[:reactNativePath],
:hermes_enabled => flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],

:app_path => "#{Pod::Config.instance.installation_root}/.."

)
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-async-storage/async-storage'
pod 'BVLinearGradient', :path => '../node_modules/react-native-linear-gradient'
pod 'Firebase/Analytics'
pod 'Firebase/Messaging'
pod 'lottie-react-native', :path => '../node_modules/lottie-react-native'
pod 'lottie-ios', :path => '../node_modules/lottie-ios'
pod 'RNSVG', :path => '../node_modules/react-native-svg'
pod 'RCT-Folly', :podspec => '../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec'
pod 'Permission-AppTrackingTransparency', :path => "#{permissions_path}/AppTrackingTransparency"
pod 'Permission-BluetoothPeripheral', :path => "#{permissions_path}/BluetoothPeripheral"
pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
post_install do |installer|
react_native_post_install(
  installer,
  config[:reactNativePath],
  :mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)

installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
    config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
    config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
  end
end

installer.pods_project.targets.each do |target|
  if (target.name&.eql?('FBReactNativeSpec'))
    target.build_phases.each do |build_phase|
      if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
        target.build_phases.move(build_phase, 0)
      end
    end
  end
end

end
post_integrate do |installer|
begin
expo_patch_react_imports!(installer)
rescue => e
Pod::UI.warn e
end
end
end
`

I am experiencing same issues after upgrading to rn 0.72.5
`$RNFirebaseAsStaticFramework = true
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/react-native-unimodules/cocoapods.rb'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '13.0'
deployment_target = '13.0'
require 'json'
podfile_properties = JSON.parse(File.read('./Podfile.properties.json')) rescue {}
require Pod::Executable.execute_command('node', ['-p',
'require.resolve(
"react-native/scripts/react_native_pods.rb",
{paths: [process.argv[1]]},
)', dir]).strip
flipper_config = ENV['NO_FLIPPER'] == "1" ? FlipperConfiguration.disabled : FlipperConfiguration.enabled
linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
use_frameworks! :linkage => linkage.to_sym
end
target 'prmassist' do
use_expo_modules!
config = use_native_modules!
flags = get_default_flags()
use_frameworks! :linkage => :static
use_react_native!(
:path => config[:reactNativePath],
:hermes_enabled => flags[:hermes_enabled],
:fabric_enabled => flags[:fabric_enabled],

:app_path => "#{Pod::Config.instance.installation_root}/.."

)
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-async-storage/async-storage'
pod 'BVLinearGradient', :path => '../node_modules/react-native-linear-gradient'
pod 'Firebase/Analytics'
pod 'Firebase/Messaging'
pod 'lottie-react-native', :path => '../node_modules/lottie-react-native'
pod 'lottie-ios', :path => '../node_modules/lottie-ios'
pod 'RNSVG', :path => '../node_modules/react-native-svg'
pod 'RCT-Folly', :podspec => '../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec'
pod 'Permission-AppTrackingTransparency', :path => "#{permissions_path}/AppTrackingTransparency"
pod 'Permission-BluetoothPeripheral', :path => "#{permissions_path}/BluetoothPeripheral"
pod 'Permission-LocationAlways', :path => "#{permissions_path}/LocationAlways"
pod 'Permission-LocationWhenInUse', :path => "#{permissions_path}/LocationWhenInUse"
post_install do |installer|
react_native_post_install(
  installer,
  config[:reactNativePath],
  :mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)

installer.pods_project.targets.each do |target|
  target.build_configurations.each do |config|
    config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= ['$(inherited)', '_LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION']
    config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '12.0'
  end
end

installer.pods_project.targets.each do |target|
  if (target.name&.eql?('FBReactNativeSpec'))
    target.build_phases.each do |build_phase|
      if (build_phase.respond_to?(:name) && build_phase.name.eql?('[CP-User] Generate Specs'))
        target.build_phases.move(build_phase, 0)
      end
    end
  end
end

end
post_integrate do |installer|
begin
expo_patch_react_imports!(installer)
rescue => e
Pod::UI.warn e
end
end
end
`

@thornec is this an Expo app? If yes, please open the issue to expo.
For all the others, please redirect the questions to #38283 which is the same root cause of missing search patch. I'll try to address this issue next week, with high priority.

Not an expo app,  just have some expo packages installed. should I refer to #38283 for a fix?

Yes, the root cause is probably the same: one dependency that is not perfectly setup to work with use_frameworks! which is required by Firebase (or by another dependency).
I'm going to systematically test the most common dependencies to look for failures. I already found one with react-native-gesture-handler (and opened a PR here: https://github.com/software-mansion/react-native-gesture-handler/pull/2635)

hi is there any update on a fix for this?

If after trying all of the above and you are able to run on a real device, but not the simulator; try checking that the project, targets and pods build settings Excluded Architectures - Any iOS Simulator SDK are set to i386. My project build settings had it set to i386, but targets build settings had it set to arm64. I changed it to i386 for all and was able to run on a simulator.
Also you might have this in your Podfile if you are upgrading from an older react native project. This sets it back to arm64 after each pod install. Remove this as well.
installer.pods_project.build_configurations.each do |config|
  config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end

This solution solved this AppDelegate issue but caused another issue with react-native-zego-zim
The following build commands failed:
	Ld /Users/username/Library/Developer/Xcode/DerivedData/Healthy-ajctxzurqyzyjzdpvbtoafkxnpux/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/react-native-zego-zim.build/Objects-normal/x86_64/Binary/react_native_zego_zim normal x86_64 (in target 'react-native-zego-zim' from project 'Pods')
(1 failure)

The following build commands failed:
Ld /Users/username/Library/Developer/Xcode/DerivedData/Healthy-ajctxzurqyzyjzdpvbtoafkxnpux/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/react-native-zego-zim.build/Objects-normal/x86_64/Binary/react_native_zego_zim normal x86_64 (in target 'react-native-zego-zim' from project 'Pods')
(1 failure)

Sorry, but this message contains no specific error, so I can't help here.

I was getting this error. I had created a new target, and that target wasn't in my Podfile. It disappeared after adding
target 'MyNewTarget' do
  inherit! :complete
end

within the larger target.

In my case, this is works. But I don't have idea why it should be added in Podfile. Before updating Xcode version, there was no script for the new target

I resolved it by opening the .xcworkspace file instead of the .xcodeproj. Then, the build was successful.

I'm getting the same error -- and I have a brand-new project with only TWO libraries: firebase and Vision Camera. Latest versions all around; this is a test app I've spent a while putting together.

In my case the same error was caused by cocoapods when I updated the version to 1.15.2 so, I installed the version 1.14.2, and I ran:
cd ios
npx po-install

and my problem was solved.

In my case, after testing all the solutions of this thread, it was uninstalling Xcode and reinstall it. I lost one day of work with this issue.

I Found Soulution
This problem happens when xcode-select developer directory was pointing to /Library/Developer/CommandLineTools when a full regular Xcode was required (happens when CommandLineTools are installed after Xcode)
Solution:

Install Xcode (get it from https://appstore.com/mac/apple/xcode) if you don't have it yet.
Accept the Terms and Conditions.
Ensure Xcode app is in the /Applications directory (NOT /Users/{user}/Applications).
Point xcode-select to the Xcode app Developer directory using the following command:
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

Note: Make sure your Xcode app path is correct.
Xcode: /Applications/Xcode.app/Contents/Developer
Xcode-beta: /Applications/Xcode-beta.app/Contents/Developer
Refer link StackOverFlow : [https://stackoverflow.com/questions/17980759/xcode-select-active-developer-directory-error]

I found my solution here:
https://github.com/CocoaPods/CocoaPods/issues/9239#issuecomment-557579931
Hope it helps

Getting this issue
The following build commands failed:
CompileC /Users/aneesh/Library/Developer/Xcode/DerivedData/halofi_rn_sb-eovebeieudgfuxakvbnvilzbtryl/Build/Intermediates.noindex/halofi_rn_sb.build/Debug-iphonesimulator/halofi_rn_sb.build/Objects-normal/x86_64/halofi_rn_sb_vers.o /Users/aneesh/Library/Developer/Xcode/DerivedData/halofi_rn_sb-eovebeieudgfuxakvbnvilzbtryl/Build/Intermediates.noindex/halofi_rn_sb.build/Debug-iphonesimulator/halofi_rn_sb.build/DerivedSources/halofi_rn_sb_vers.c normal x86_64 c com.apple.compilers.llvm.clang.1_0.compiler (in target 'halofi_rn_sb' from project 'halofi_rn_sb')
(1 failure)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@aneesh-dasari that's not a valuable error message. It only tells us which command failed, but not why.
Can you provide a reproducer using this template?

@DeveloperMCD please make sure of:

Run USE_FRAMEWORKS=static bundle exec pod install to install the pods. Firebase requires that specific flag
Open the xcworkspace file, not the xcodeproj file.

Thanks. Work in my case

If after trying all of the above and you are able to run on a real device, but not the simulator; try checking that the project, targets and pods build settings Excluded Architectures - Any iOS Simulator SDK are set to i386. My project build settings had it set to i386, but targets build settings had it set to arm64. I changed it to i386 for all and was able to run on a simulator.
Also you might have this in your Podfile if you are upgrading from an older react native project. This sets it back to arm64 after each pod install. Remove this as well.
installer.pods_project.build_configurations.each do |config|
  config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end

Yes had this left and that was causing it for me. Thank you!

For me its simply missing 'arm64' form pod build setting.
After I install pod that Pod always missing that 'arm64' text

This is what you see when you install pod

Click on it and you can add it

So this is how it should look like the 'arm64' should be in both place the the Debug and the Release

I hope this helps, sometimes very little things missing and ruin everything

What worked for me was, in ios/Podfile, add:
target 'YourTargetName' do
    inherit! :complete
  end

Seems like there's an issue with XCode finding the location of RCTAppDelegate.h without it.

Sometimes, it just because you open .xcodeproj instead of .xcworkspace

I solved it by https://github.com/facebook/react-native/issues/35818#issuecomment-1604110706

For those who still have this issue, first make sure you opened "projectName".xcworkspace and not "projectName".xcodeproj in XCode.

you saved my life 🤣

If after trying all of the above and you are able to run on a real device, but not the simulator; try checking that the project, targets and pods build settings Excluded Architectures - Any iOS Simulator SDK are set to i386. My project build settings had it set to i386, but targets build settings had it set to arm64. I changed it to i386 for all and was able to run on a simulator.
Also you might have this in your Podfile if you are upgrading from an older react native project. This sets it back to arm64 after each pod install. Remove this as well.
installer.pods_project.build_configurations.each do |config|
  config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end

this helped me solve my build issue

I was able to fix this after a fair bit of pain.
I followed all the steps listed in Stack Overflow, google, chatGpt so....
rm -rf ios/Pods ios/Podfile.lock
rm -rf ~/Library/Developer/Xcode/DerivedData
CRUCIALLY for me anyway, remember to add arm64 to excluded architectures in the build settings of the project and the Pods in Xcode

And remember to re-add to Pods every time you delete them. I would have saved a lot of time after the first time I deleted those pods if I had have remembered that.

is issue, first make sure you opened "projectName".xcworkspace and not "projectName".xcodeproj in XCode.

check this it is solved in above comment , go to link https://github.com/facebook/react-native/issues/36611#issuecomment-1961259608


ARPACK-NG is not deterministic

Reproducing code example:
import numpy as np
from scipy.sparse.linalg.eigen.arpack.arpack import _arpack

_arpack_solver = _arpack.__dict__['dsaupd']

for i in range(2):
	x1 = _arpack_solver(
		0, 'I', 'LM', 2, 0.0001,
		np.array([0, 0, 0, 1]),
		np.zeros((4, 4), np.float64),
		np.array([1, 0, 40, 1, 0, 0, 3, 0, 0, 0, 0], dtype = np.int32),
		np.zeros(11, np.int32), np.zeros((12,)), np.zeros((48,)), 1,
	)[2]
	x2 = _arpack_solver(
		1, 'I', 'LM', 2, 0.0001,
		np.array([0, 0, 0, 1]),
		np.zeros((4, 4), np.float64),
		np.array([1, 0, 40, 1, 0, 0, 3, 0, 0, 0, 0], dtype = np.int32),
		np.zeros(11, np.int32), np.zeros((12,)), np.zeros((48,)), 1,
	)[2]
	print(x1, x2)

The same line should be printed twice, but instead it prints:
[0. 0. 0. 1.] [ 3.95742464e-01  8.64960398e-04 -9.22720579e-01 -9.16567150e-01]
[0. 0. 0. 1.] [ 0.11759638 -0.29962625  0.90382696 -0.25045105]

Scipy/Numpy/Python version information:
1.3.0 1.16.2 sys.version_info(major=3, minor=6, micro=7, releaselevel='final', serial=0)

More Info
I also tried called the ARPACK function directly in C, and got the same result. Same problem on ARPACK-NG 3.4.0 and 3.5.0, but 3.6.0 gives correct (deterministic) output:
[0. 0. 0. 1.] [0. 0. 0. 0.]
[0. 0. 0. 1.] [0. 0. 0. 0.]

C code:
#include <stdio.h>

void dsaupd_(
	int *ido, char *bmat, int *n, char *which,
	int *nev, double *tol, double *resid, int *ncv,
	double *v, int *ldv, int *iparam, int *ipntr,
	double *workd, double *workl, int *lworkl, int *info
);

int main(int argc, char** argv) {
	for (int i = 0; i < 2; ++i) {
		{
			int    ido = 0;
			char*  bmat = "I";
			int    n = 4;
			char*  which = "LM";
			int    nev = 2;
			double tol = 0.0001;
			double resid[4] = { 0, 0, 0, 1 };
			int    ncv = 4;
			int    ldv = 4;
			double v[16] = { 0.0 };
			int    iparam[11] = { 1, 0, 40, 1, 0, 0, 3, 0, 0, 0, 0 };
			int    ipntr[11] = { 0 };
			double workd[12] = { 0 };
			double workl[48] = { 0 };
			int    lworkl = 48;
			int    info = 1;

			dsaupd_(
				&ido, bmat, &n, which, &nev, &tol, resid,
				&ncv, v, &ldv, iparam, ipntr, workd, workl, &lworkl, &info
			);

			printf("[%f %f %f %f]", resid[0], resid[1], resid[2], resid[3]);
		}

		{
			int    ido = 1;
			char*  bmat = "I";
			int    n = 4;
			char*  which = "LM";
			int    nev = 2;
			double tol = 0.0001;
			double resid[4] = { 0, 0, 0, 1 };
			int    ncv = 4;
			int    ldv = 4;
			double v[16] = { 0.0 };
			int    iparam[11] = { 1, 0, 40, 1, 0, 0, 3, 0, 0, 0, 0 };
			int    ipntr[11] = { 0 };
			double workd[12] = { 0 };
			double workl[48] = { 0 };
			int    lworkl = 48;
			int    info = 1;

			dsaupd_(
				&ido, bmat, &n, which, &nev, &tol, resid,
				&ncv, v, &ldv, iparam, ipntr, workd, workl, &lworkl, &info
			);

			printf(" [%f %f %f %f]\n", resid[0], resid[1], resid[2], resid[3]);
		}
	}

	return 0;
}

Right, arpack 3.6.0 has some fixes for the initial vector generation whereas scipy is at 3.3.0. Unfortunately, some tests that worked with arpack<3.5.0 seem to fail with 3.6.0, which needs to be resolved before upgrading... #10375
Note that the results are generally in principle always nondeterministic, because if you don't explicitly specify the initial vector, ARPACK will generate a random initial vector.

Also: why do you say the same line should be printed twice? You are not calling the function with the same parameters.

This example specifies the initial vector (resid, info = 1) so it should be deterministic.
There are two calls to dsaupd_ because it takes two iterations for the non-deterministic result to show up. Not that the two calls are in a loop; which is why both lines in the output (each produced from two iterations of dsaupd_) should be the same.

Right --- however, ARPACK still appears to intentionally generate and use random vectors in certain cases, not just for the initial vector. This is not something that has been addressed in ARPACK 3.7.0, see https://github.com/opencollab/arpack-ng/blob/master/SRC/dsaitr.f#L409
The difference in behavior between the 3.5.0 and 3.6.0 versions is then incidental --- the changes made are unrelated to this issue. I guess if you want the random seed behavior in arpack to be controllable, this should be raised with arpack-ng people.

Thanks, I was stuck figuring out where it was coming from!

Just wondering if this is fixed.

@mdhaber Is this the same behavior we saw here?

This has been addressed by the bump in the ARPACK version to 3.9.1. Now the main is giving
[0. 0. 0. 1.] [0. 0. 0. 0.]
[0. 0. 0. 1.] [0. 0. 0. 0.]

Hence closing this one.


Upgrade cert-manager to 1.12.13 to get upstream patches for CVE-2024-25620 and CVE-2024-26147

Upgrade cert-manager to 1.12.13 to get upstream patches for CVE-2024-25620 and CVE-2024-26147
Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary
CVE-2024-26147 is fixed in Helm 3.14.2, CVE-2024-25620 is fixed in Helm 3.14.1. Helm is a vendored package used by cert-manager package. The current version of cert-manager 1.12.12 carries Helm 3.12.0. 1.12.13 of cert-manager carries Helm 3.14.2, hence fixing both CVEs. As such, this PR is also removing the custom patch for CVE-2024-25620 that was added into the cert-manager spec file.
Change Log

Fixes CVE-2024-26147 by updating to 1.12.13
Removes need for a custom patch for CVE-2024-25620 by updating to 1.12.13

Does this affect the toolchain?
NO
Links to CVEs

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-25620
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26147

Test Methodology

Local build with RUN_CHECK=y

The failing ptests is for nbdkit and it's a known failing tests. No regressions, good to merge.

Auto cherry-pick results:

3.0-dev :x: -> https://github.com/microsoft/azurelinux/pull/10478

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=642232&view=results


Add StompMessenger to send msg via STOMP.

Adds sample config in settings.py;
Requires stomp.py to be installed.

As for the decreased test coverage, I think we should just ignore it. Unless we provide a mock messaging server to the test, we can not reasonably test the messengers themselves.

The _request will block message middleware, so I included it in this PR.
And I'll change the __init__ to make code more simple.

Looks good to me.


capitaine-cursors: fix build with inkscape => 1.0

Motivation for this change
Without this, all cursors are empty resulting in X to fall back to the default cursors.
As shown on hydra, there were a bunch of warnings about a function being deprecated, and xcursorgen failed to read the PNG files generated.
Things done
I've added a patch which is already merged upstream, but barely didnt make it into an release which fixes all of these problems. Also did some minor formatting changes.
The build now spams the following warning which I'm not sure how to fix:
Fontconfig error: Cannot load default config file

Everything does seem to work though, so i think that's fine.

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

The error comes from a missing fonts.conf file if I remember correctly, which can be fixed using FONTCONFIG_FILE = makeFontsConf { fontDirectories = [ ]; }; if I copied the right line.

The error comes from a missing fonts.conf file if I remember correctly, which can be fixed using FONTCONFIG_FILE = makeFontsConf { fontDirectories = [ ]; }; if I copied the right line.

That worked, thanks!

Result of nixpkgs-review pr 102526 run on x86_64-linux 1

1 package built:

capitaine-cursors


STAC Repositories and OGC configuration

Overview
This is a placeholder PR to parellilize the dev and track the progress.
Addresses:

https://github.com/azavea/geotrellis/issues/266
https://github.com/azavea/geotrellis/issues/267
https://github.com/azavea/geotrellis/issues/269
https://github.com/azavea/geotrellis/issues/271

@CloudNiner no, we don't have tests yet, it is some test code that can be removed later during the branch cleanup (i think).


comment typo of  is_fully_defined function

comment typo of  is_fully_defined function

We will not be encouraging one liner grammatical changes as this is expensive process, thank you for your interest.
CC @mihaimaruseac @chanshah

Furthermore, this is not a typo. iff means "If and only if"

Thank you, that's very nice of you ~


Feature/set line height

@riccardoscalco can you please merge master to resolve conflicts?

Tested locally, looks cool


master to main

Proposed changes
With the branch name change, some of the links in the docs had to be changed as well.
Types of changes
Please put an x in the boxes related to your change.

[ ] Minor Issues and Typos
[ ] Major Content Contribution
[ ] Others

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to reach out. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING GUIDELINES
[ ] I have signed the CLA
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Related issues

Please leave the issue numbers or links related to this PR here.

Further comments
If this is a relatively large content contribution, kick off the discussion by explaining why you would suggest the content contribution, etc...

@aidan-kwon @kjhman21 이거 승인 좀 해주세요 ㅠ.ㅠ


Broken functionality after the upgrade to 2.4.3

I have a test infrastructure (POC) with Rancher. I upgraded the Rancher and now I am not able to edit the custom created clusters I have. When I press "Save" on YAML editor or in the form the "Save" button goes dimmed and I see the turning wheel, but it never ends. I need that functionality as I need to enable ipvs proxy mode for example and few more things.
The creation of the custom cluster with:
rancher clusters create --rke-config my_prepared.yaml
does not work as well. The cluster is created but with all the default values and no any of the additional ones.
I also notice that on CIS testing page when I click "Run Scan" I can not chose the scan profile: the drop-down is empty.
I recreate the similar setup but skip the upgrade - directly install the latest stable version: 2.4.3. So far the above problems are missing: I am able to edit the custom cluster yaml and I am able to run CIS scan and choose the profile.
Could you help me to find what is wrong with the "old" setup?
In case I find a time will recreate the setup with 2.3.6 or 2.3.7 (it is not a good candidate as it was listed as latest stable for only few days before 2.4.3) and test the upgrade again.
The 3 nodes in the rancher cluster was upgraded to the latest Ubuntu 18.04 and rebooted one by one. Doesn't solve the problems.
OS is Ubuntu 18.04 LTS in Digital Ocean. VMs are 2 CPU/4GB RAM with internal networking.
Docker is 19.3.5 - upgraded to 19.3.8 (at the moment)
On test with pristine install I use Docker 18.9.9 as I have some problems with our app and want the whole environment with the same version.
I test both 4.15 and 5.3 kernels (HWE)
|Versions|Rancher v2.4.3 UI: v2.4.22 |
|Route|undefined|

I guess this happens if the network is not well.
Can you try to click Refresh Kubernetes Metadata button in global menu > Drivers ?
It will force rancher to fetch the cis profiles.
We need to fix the UI to make it still work even there is no cis profile. Also backend should consider this case.

I can confirm that using custom cluster creation from the command line is not working (returns OK but the config is the default one in the UI):
rancher clusters create --rke-config my_prepared.yaml
Technically I'm having an issue launching RKE with external etcd. Could be related to the above.

I guess this happens if the network is not well.
Can you try to click Refresh Kubernetes Metadata button in global menu > Drivers ?
It will force rancher to fetch the cis profiles.
We need to fix the UI to make it still work even there is no cis profile. Also backend should consider this case.
Unfortunately it does not solve the problem. And this problem (CIS scan not working) is a very small part of the broken functionality. Inability to change the kubelet or kubeproxy settings hurts a lot more. The fact that CLI (rancher cli tool) have also problems lead me to the conclusion it is not in the UI.

Hi @nikinaydenov  It will be great if you could provide the detailed reproduce steps. Thanks :)

Two attempts to reproduce was made. I can not hit the problem again and can not recognize what can be the reason. I create a new RKE 3 node cluster and rancher custom cluster with 2.3.6. Test upgrade to 2.3.7. Test upgrade of the kubernetes to 1.17.5 (on custom cluster with edit form) and finally upgrade to 2.4.3. The second attempt was with added firewalls. Why? On broken cluster initially the cattle-cluster-agent was giving some errors that it is unable to resolve the rancher cluster URL. When I remove the FWs it pass. Now even with FWs enabled I am able to upgrade without problems. Will continue to add part by part hoping will hit the problem. I am in test phase so mistakes are acceptable.
FW worker:
ufw allow ssh
ufw allow http
ufw allow https
ufw allow 8472/udp
ufw allow in on eth1 from <IP_ADDRESS>/8

FW etcd + controlplane:
ufw allow ssh
ufw allow 2379:2380/tcp
ufw allow 6443/tcp
ufw allow 8472/udp
ufw allow in on eth1 from <IP_ADDRESS>/8

Setup is with internal and external networks (internal on eth1) and external TCP load balancer in front of rancher-ha nodes (3 node cluster especially for Rancher). There is no FW at the moment on this 3 nodes.
My plan is to add FW there as well and to add storage solution I use together with some test deployments. In fact the broken cluster was created a long time ago and it is upgraded several times already: from 2.2.x


a default HTTPS ingress rule should be injected in cluster_primary_security_group to allow node-group security group

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

No 🛑: please wait to file a request until the functionality is avaialble in the AWS provider
Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

Amazon EKS created SG (aka cluster_primary_security_group) needs a inbound rule to allow traffic from node-group instances; otherwise it fails to join the node group, with the below error:

[ERROR]: The cluster Security Group sg-020b0c1fexxxxxxxx is not allowing traffic from the worker node.

Describe the solution you'd like.

in the main.tf we should have a default rule allowing https traffic from node node_security_group, something like this:
resource "aws_security_group_rule" "traffic_from_nodes" {
  for_each                 = var.service_enabled ? toset([var.service_name]) : []
  type                     = "ingress"
  from_port                = 443
  to_port                  = 443
  protocol                 = "tcp"
  source_security_group_id = aws_security_group.node[0].id
  security_group_id        = aws_eks_cluster.this[0].vpc_config[0].cluster_security_group_id
  description              = "Allow traffic from the worker nodes"
}

Describe alternatives you've considered.

Using this repo as the child-module, this thing can be done doe now i the parent module, as a work around:
resource "aws_security_group_rule" "traffic_from_nodes" {
  for_each                 = var.service_enabled ? toset([var.service_name]) : []
  type                     = "ingress"
  from_port                = 443
  to_port                  = 443
  protocol                 = "tcp"
  source_security_group_id = module.cluster.node_security_group_id
  security_group_id        = module.cluster.cluster_primary_security_group_id
  description              = "Allow traffic from the worker nodes"
}

Additional context

closing due to lack of reproduction

can you explain what does it mean - due to lack of reproduction ?
Using this module, the nodes are constantly failing to join the node group and using TroubleshootEKSWorkerNode Runbook, it reports that the above security group rule is missing. I provided the actual error and also the code that I'm using to work around it - what exactly it's lacking?

You should not close anything within 20 mins, without giving any proper reason, IMO

rather strong words to use on something that is provided to you for free
I gave a reason - you intentionally deleted the required section from the issue template and did not provide the required reproduction so how can I even begin to triage?


CODEOWNERS: fix jonringer entry

Motivation for this change
Fix entry added in:  #158267
thanks @zowoq for pointing out the error
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#example-of-a-codeowners-file
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I'm merging fast.  We already had the policy discussion, and the syntax now seems fairly certain as well.