-
Notifications
You must be signed in to change notification settings - Fork 212
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]: No Module Found "OneSignalExtension" in NotificationService.swift #857
Comments
I am having same issue, with error on Podfile import: import UserNotifications
import OneSignalExtension // < Shows error No such modlue 'OneSignalExtension'
// rest of the swift code... I am using Xcode version 14.1 and flutter version 3.19.6 with Dart 3.3.4. I have repeated steps 3 times following guide. Only thing that isn't available in this Xcode is "Minimum Deployments" for iOS version. There is only "Deployment Target". @asadamatic have you managed to get it working? |
I am having the exact same problem. @markosole have you found a solution? |
Hi @elishae621 yes I have manged to sort it out and it works now. There are few things that I did:
flutter clean
flutter pub get
One last thing is to adjust settings in your project (you will run into issues if you don't.
It will probably be somewhere at the bottom, so drag and drop it above. Now your can built your app ;) |
Getting the same error when building. I followed the instructions from here: https://documentation.onesignal.com/docs/flutter-sdk-setup But still getting the Not sure how to fix this. |
same here |
What happened?
I followed this Flutter SDK setup guide. I used the provided swift code and my iOS build kept failing after it. I rebuilt my app using XCode, and it gave me this error in the
NotificaitonService
swift file.Steps to reproduce?
What did you expect to happen?
I expected the code from the official guide to work without any issues.
OneSignal Flutter SDK version
Release 5.1.2
Which platform(s) are affected?
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: