-
Notifications
You must be signed in to change notification settings - Fork 198
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
[Bug]: Our iOS builds have started to fail without any code changes OneSignalExtension/OneSignalExtension.h' file not found
#972
Comments
OneSignalExtension/OneSignalExtension.h' file not found
OneSignalExtension/OneSignalExtension.h' file not found
We're also seeing the same issue. |
I don't know if it's relevant but the failed builds all seem to be using cocoapods 1.15.1 If I force 1.15.2 it builds again ok 🤷♀️ |
that works for us, thanks @kpturner! |
Thanks for reporting everyone, and that cocoapods update fixed it. Very strange since it doesn't seem you made any changes to your OneSignal SDK dependency? I see your post says you are on 5.0.4 @kpturner...Which day did your nightly builds start to fail? I wonder if your CI is actually pulling latest updates under the hood. We released Version 5.0.5 on January 30. Maybe it is doing this update automatically? |
Thanks for the update. We have been building every day since 30th without issue. It started failing on the 5th February I think - but it only failed in the CI (which is obviously a virgin install) but not locally. I will check the logs to see if there are clues regarding the version of the SDK in use. |
I have checked the logs and the failures (using cocoapods 1.15.1) still show: |
This probably explains a lot |
Ah, this makes sense. I'll close out this issue then! |
What happened?
Our overnight builds (that run on CircleCI) have started to fail, but we have not actually changed any code.
Steps to reproduce?
What did you expect to happen?
The build should not have started to just suddenly fail
OneSignal Cordova SDK version
5.0.4
Which platform(s) are affected?
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: