-
Notifications
You must be signed in to change notification settings - Fork 375
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
Warning The OneSignalNotificationServiceExtension [Debug]
target overrides the CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER
#1155
Comments
Same issue here for the native lib |
+1 |
+1 |
same issue here |
Howdy! In any case, we will investigate. Others on this thread, can you please provide environment information? Also to confirm, this is happening with M1 as well as other processors for all of you? |
It is not an M1 issue. Getting the same error on an Intel processor here. |
Howdy y'all, The reason this started happening is because XCode 12 now defaults this setting to |
Hi @rgomezp , Mac OS: 11.2.3 Any other solution? Thanks |
|
Closing due to inactivity. |
This was closed a while ago, but I recently started getting the same error: When I install pods the following warning is showing after installation:
After that, I'm setting "Quoted Include in Framework Header" to $(inherited) for both Pods and Target. When running the target on a simulator, I'm getting the following error:
My Flutter Doctor:
Also I would like to note that when installing pods, a few libraries are resolving back to version 0.0.1 which is strange as they are different from the version already set. Solutions I've already tried: rm -rf ~/Library/Developer/Xcode/DerivedData/ and Build setting -> Other Linker Flags -> add $(inherited) Still the error persists, let me know if anyone figured out a solutions for this issue |
I'm facing the same issue. |
I have the same issue |
I did as he said, then I had a problem with the order of the references: |
I'm getting this warning while I'm executing
pod install
it's not my first time using this library, but this is a new issue that happened on my new Macbook pro with Apple Silicon M1 chip
RN: 0.64.3
One-Signal: 4.0.3
any idea how to avoid this warning?
The text was updated successfully, but these errors were encountered: