-
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
No such module 'OneSignal' #1370
Comments
Hi. Trust you are well. Did you find a solution to this? I have the same problem and I can't find a solution that works. |
Also running into this after weeks of running this lib without issue. The error fully blocked our build process and unfortunately I had to remove OneSignal entirely. Would greatly appreciate a fix. Edit: things are working now but unfortunately I can't pinpoint what changed -- moving forward cautiously but concerned this bug will break things when moving into prod |
I haven't found a solution. I've been sending message with their support, and they sent this:
I tried what is in the documentation, but there may have been other issues wrong as well; they said that the target should not be added into the react native target, and instead be added by itself. I moved on to using firebase, but I may try and see if some of the other feedback they gave works. It's pretty frustrating. |
Thanks a lot. I removed all traces of OneSignal and redid the process in the documentation. It worked the second time. |
Same problem here, I followed the OneSignal documentation step by step but couldn't build my app yet! |
In my case this error appears to be related to my M1 Mac; I solved the issue by modifying my change:
to:
Not a huge fan of this as AFAIK it forces my iOS simulator to use Rosetta when running my app but at least things are building. |
In my case the error was M1 Mac In addition to this, @jesse-savary's comment is correct and is in fact one of the necessary steps to achieve OneSignal (or another Pod with the same issue) to compile, but I needed to add a post_install script into Podfile which force every single Pod to target This additional last step was necessary for me in order to make my project to compile. You simple need to add this to your Podfile:
There's an alternative to EXCLUDED_ARCHS which is not excluding architectures BUT limiting 'Any iOS Simulator SDK' to just be
All this information was extracted from this blog post(which saved my life), and explains everything in a very clear and direct way: https://blog.sudeium.com/2021/06/18/build-for-x86-simulator-on-apple-silicon-macs/ Of course this will forcing Simulator to run with Rosetta but there's no alternative which works in the time I'm writting this. This solution applies to every Happy coding! 🚀 |
Duplicate of #1260 |
I was able to get ride of the error. What I did you may ask !! . I use to open xcodeproj file but instead open xcworkspace file and it worked. |
Worked for me too. |
on an M1 and I'm attempting to build an archive, I can build the app on my machine and run but cannot archive. All solutions including the above have failed. |
after seeing Xcode give the No such module 'OneSignal' error, what worked for me is:
maybe xcode compiles differently than the |
if someone is facing this issue after installing watermelon db and have set use_frameworks option in podfile, try to install watermelon libs from static library.
|
Well, I'm having this issue, right now. Already tried a lot of different solutions, none worked. Does anyone else is experiencing this issue too? |
I encountered this issue yesterday when trying to build a target that was a duplicate of another one. This target was not present in our podfile. I created a shared config for the targets to use and the error went away. def sharedConfig
config goes here
end
def sharedOneSignal
config goes here
end
target 'Target'
sharedConfig
end
target 'Target Clone'
sharedConfig
end
target 'OneSignalNotificationServiceExtension' do
sharedOneSignal
end
target 'OneSignalNotificationServiceExtensionClone' do
sharedOneSignal
end |
this approach worked for me as well! 🤷♂️🙃 |
If you're using React Native, please open the iOS folder directly in Xcode, and don't open the .xcodeproj file in the iOS folder but instead open the .xcworkspace file. As long as you've correctly run 'pod install' in React Native, you should be able to successfully resolve the 'no module' issue. |
It worked for me: With OneSignal 5.0.0 (on Flutter) I had to use:
instead of
|
Description:
This is listed as a common issue: https://documentation.onesignal.com/docs/troubleshooting-ios
Resources that I have found have not been able to solve the issue. I've searched online and through the prior issues that people have listed on github.
In
OneSignalNotificationServiceExtension
, I receive the error:No such module 'OneSignal'
Environment
I am running Xcode 13.2.
I installed through npm:
This is my podfile:
Steps to Reproduce Issue:
I followed the React Native SDK Setup: https://documentation.onesignal.com/docs/react-native-sdk-setup
The text was updated successfully, but these errors were encountered: