Open tibbe opened 1 day ago
Removing react-native-zip-archive
from the dependencies of my (large) project fixes the compilation issues and thus provides further evidence that there's a problem here.
@tibbe you mentioned in the react-native-firebase issue that there was perhaps a problem with messaging as well? I am unaware of a problem with messaging but wanted to confirm with you that you have things compiling now before I hide that comment.
I'm only aware of the need to:
dependencies
param from init provider (assuming you use crashlytics)I'm not aware of anything with messaging at the moment ?
@tibbe you mentioned in the react-native-firebase issue that there was perhaps a problem with messaging as well? I am unaware of a problem with messaging but wanted to confirm with you that you have things compiling now before I hide that comment.
I'm only aware of the need to:
- bump the firebase-ios-sdk (either with patch to @react-native-firebase/app/package.json or with a an override https://rnfirebase.io/#ios)
- patch @react-native-firebase/firestore to remove the transitive dep on nanopb (assuming you use firestore)
- patch @react-native-firebase/crashlytics to remove
dependencies
param from init provider (assuming you use crashlytics)I'm not aware of anything with messaging at the moment ?
I managed to get it to compile by cleaning/recompiling harder so no issue with messaging I believe.
Great, thanks for replying, I'm going to hide that comment then to make the issue as easy to digest for people that need the workaround since build breaks are typically "panic mode" for people, but hiding the comment isn't "with prejudice" or anything. I think we've got the full set of workarounds in there but if you see anything else that is a build break obviously + please post it up. Cheers
It's not clear to me where '-G'
sneaks in. When I do my react native build there's a very long list of EXPORT
statements logged somewhere near the top of the build output and one of these contains GCC_WARN_INHIBIT_ALL_WARNINGS
. I'm not sure how it gets there. That identifier isn't anywhere in my code base and I can't find it in react-native-zip-archive
's either.
I had the same issue. I think this is due to the GCC_PREPROCESSOR_DEFINITIONS
compiler flags that was removed in the latest 7.0.1 version. It was removed in this commit: https://github.com/mockingbot/react-native-zip-archive/commit/9ea64067b2aa56f339ee0b642ff20f8d97b27d49 If you are using version 6.1.0, it is still in the pod spec.
Note that updating to 7.0.1 might require you to raise the minimum iOS version to 15.5 as per this repos README.md.
@kptp Do you think upgrading to 7.0.1 will resolve this issue?
@ankitjpk I think it is worth trying, if you are able to upgrade it. The release note specifically mentions the XCode 16 issue: https://github.com/mockingbot/react-native-zip-archive/releases/tag/v7.0.1
@kptp
Upgrading it causes Invalid react-native-config.podspec file: undefined method
visionos' for #
@ankitjpk Are you using the react-native-config
library? It sounds like an issue with that library, but I don't know anything about it
Describe the bug After upgrading to Xcode 16 the library doesn't seem to build:
The issue might be similar to https://github.com/invertase/react-native-firebase/issues/8020.
To Reproduce Steps to reproduce the behavior:
Expected behavior No compilation error.
Env (please complete the following information):
Additional context Add any other context about the problem here.