-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hermes macCatalyst framework signing issue ("bundle format is ambiguous") in 0.75.0-rc.5 #390
Comments
Build rnfbdemo_2024-07-18T17-13-10.txt That's the build log. I'm going to attempt to re-do a build on rc.2 (which I remember working for macCatalyst but with some patches for iOS config scripts in react-native-config.js as used in react-native-firebase) and get it to succeed then fail again on rc.5 so I can prove this is reproducible In the meantime if anyone else can successfully do repeated builds of macCatalyst and report, that would be informative |
Hi Mike, I'm trying to repro this, but so far I couldn't. The steps I'm following:
Do you know if perhaps something changed in Firebase? |
I suspect this must be local then, as I feared. I work pretty hard to be repeatable+reproducible but this won't be the first time some local thing has crept in. Will continue checking on my side - haven't had a chance since initial post |
Closing as not reproducible on my end. Let's reopen if we have a better repro. |
Old Version
0.75.0-rc.2
New Version
0.75.0-rc.3+ ?
Description
I am unable to run my typical react-native-firebase release qualification script to completion as it fails to build macCatalyst with a signing issue.
It appeared to work in 0.75.0-rc.3 I thought, it appears to fail first in 0.75.0-rc.5, however my test results are very confusing.
Specifically, I believe this worked in 0.75.0-rc.2 and rc.3 but after attempting a build with 0.75.0-rc.5 I can no longer get it to work, so perhaps there is some state that is corrupted between runs related to hermes and it's downloaded tarball?
Note that this is macCatalyst, which is "sort of" iOS, it is not really macos (that is, it is not react-native-macos)
You will need to have an Apple Developer Account and certificate installed on your machine to test this.
Steps to reproduce
I have a build reproducer for react-native-firebase that I use to demonstrate how builds should work for end users, and also to pre-qualify react-native RCs. I have a branch for rn75, so you should clone it and run it:
git clone [email protected]:mikehardy/rnfbdemo
cd rnfbdemo
git checkout rn75
XCODE_DEVELOPMENT_TEAM=2W4T2B656C ./make-demo.sh
(but replace with your own development team that you have a valid certificate installed for...)It will first run iOS in debug and Release mode, then it will attempt to do the macCatalyst build
(it will continue and also do android debug and release - feel free to comment all of that out and just focus on macCatalyst if you like)
Affected Platforms
Other (please specify)
Output of
npx react-native info
Stacktrace or Logs
The text was updated successfully, but these errors were encountered: