Everything has been going well but 2 days ago I was forced to update my Xcode version and now everything is broken. After updating from 14.2 to 14.3 I have been unable to remove an error in "YogaKit.private.swiftinterface" and "YogaKit.swiftinterface". Both of these headers give the same issues as follows: Failed to verify module interface of 'YogaKit' due to the errors above; the textual interface may be broken by project issues or a compiler bug Underlying Objective-C module 'YogaKit' not found no such module 'yoga' SO FAR I HAVE: ++ Deleted DerivedData ++ Added Yoga as an explicit path in Podfile via pod 'Yoga',:path => '../node_modules/react-native/ReactCommon/yoga' ++ Tried each variation again with using lowercase yoga ++ Verified Yoga is in the Pods ++ Verified YogaKit is in the Pods ++ rm -rf pods, podlock, and node_modules and reinstalled numerous times ++ Verified the exact same build works perfectly on 14.2 ++ Googled + ChatGPT couldn't find solution ^-------------------------^---------------------------^ I can read from the provided issues that there is likely a mismatch of some sort with Yoga/YogaKit/React Native. I am confused as to why an xCode version update would have breaking changes like this in it but regardless I could compile and archive just fine before this xCode version update so it's hard to imagine what else could have caused this at the exact same time as an Xcode version update. Do you have the same problem? Were you able to fix it? Please help!

I have an app that uses a secure certificate to communicate with the node server. I have been using openssl to create a pem file and then convert that pem file to a .cer which is used in the app. This method has been working for months but all of a sudden yesterday all iOS versions became locked out and iOS now claims the certificate is invalid. The certificate is valid until Apr. 11th and the app and website are working as expected on other platforms. I updated the certificate using the same methods I have been in the past: openssl s_client -servername DOMAIN -connect DOMAIN:443 </dev/null | sed -n -e '/-.BEGIN/,/-.END/ p' > mycert.pem  then openssl x509 -in mycert.pem -outform der -out mycert.cer and the .cer says it is valid until Apr 10 but when I run the app it still says it's invalid and there could be a man in the middle. I even added the domain as an exception to allow insecure http payloads but I am still getting an error saying it's invalid. Has there been a recent update to ssl standards in iOS or are other people experiencing this as well?