Skip to content

Conversation

@mikehardy
Copy link
Collaborator

Description

Today I learned (while updating react-native-google-mobile-ads):

info has no semantic meaning in Xcode build scripts, so they were not printed. But note does (as does error and warning, which were used correctly)

https://developer.apple.com/documentation/xcode/running-custom-scripts-during-a-build#Log-errors-and-warnings-from-your-script

Release Summary

semantic release, single fix commit

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
    • Yes
  • My change supports the following platforms;
    • Android
    • iOS
    • Other (macOS, web)
  • My change includes tests;
    • e2e tests added or updated in packages/\*\*/e2e
    • jest tests added or updated in packages/\*\*/__tests__
  • I have updated TypeScript types that are affected by my change.
  • This is a breaking change;
    • Yes
    • No

Test Plan

Search the build logs for RNFB build script and you should see it now. Before the build script was not logging any of it's useful information


Think react-native-firebase is great? Please consider supporting the project with any of the below:

@vercel
Copy link

vercel bot commented Oct 26, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
react-native-firebase Ready Ready Preview Comment Oct 29, 2025 11:28pm

info has no semantic meaning in Xcode build scripts, so they were
not printed. But note does (as does error and warning, which were
used correctly)
de-lints the file and solves a problem where locally you cannot test
the script if you have built both the release and debug version
previously I was confusing onConfigUpdate with onConfigUpdated... that 'd'
there were severe performance problems with remote-config testing on
iPhone 17 + macos-26 + Xcode 26, perhaps this will help
@mikehardy
Copy link
Collaborator Author

Had a really difficult time getting iOS e2e to run successfully and even now it's a bit flaky
But I got it from like 0% to around 80% which gives me enough confidence to merge this and move forward with development again

@mikehardy mikehardy merged commit df4a26d into main Oct 30, 2025
20 of 21 checks passed
@mikehardy mikehardy deleted the @mikehardy/ios-config-info-printouts branch October 30, 2025 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants