Hi there
I have an error when try to execute my app in iOS phone or simulator.
I followed the instructions with the page (https://documentation.onesignal.com/docs/react-native-sdk-setup). But the error persists.


Also, I clean, build, set the commands pod Install, Pod deintegrate, delete Pod folder, PodFile.lockfile, delete files in ~/Library/Developer/Xcode/DerivedData, delete Target OneSignalNotificationServiceExtension and create it again. But the error continues.
I'm using the package react-native-onesignal: ^3.7.1
RN 60+
Thanks
I saw the same problem but got it to work. I noticed when running pod install it warned me about FRAMEWORK_SEARCH_PATHS being modified, so I added $(inherit) to that (search for 'Framework Search Paths' under your Target's Build Settings), and it worked. Seemed that Framework Search Paths was left blank.
The issue is not resolved..
The warning disappeared, but the error is still there.
Same here. As I noticed, It happened after OneSignal updates from 2.13.0 to 2.13.1.
I'm not sure that I have got the same issue. My OneSignal folder in Pods is empty.

I will get the same result if I use pod 'OneSignal', '>= 2.11.2', '< 3.0' instead of pod 'react-native-onesignal', path: "#{$npm_path}/react-native-onesignal" in my Podfile.
+1 please help.
Howdy,
We haven't been able to reproduce on our side.
Have y'all run pod deintegrate && pod install ???
pod cache clean --all helped me!
I have the same issue any update?
target 'OneSignalNotificationServiceExtension' do
pod 'OneSignal', '>= 2.9.3', '< 3.0'
end
helped me
Guys, go to "Build Settings" -> "Search Paths"
change the value of $(PROJECT_DIR) to recursive
and Wolla! now it should work!
Howdy,
It sounds like this issue is solved.
Enjoy!
Solution recommended by @tmaly1980 ultimately worked for me.
This post also helped me figure out exactly _where_ to make this change -> https://stackoverflow.com/questions/26445784/target-overrides-the-framework-search-paths-build-settings
This is not an issue unique to the One Signal SDK, rather it is a hurdle you can run into with any pod that uses a dynamic framework and not a static library. Still it might be helpful to add a note to the iOS & React Native getting started guides in case others run into this issue 馃檹
Most helpful comment
I have the same issue any update?