You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded our OneSignal SDK from 5.0.2 to 5.2.6 using CocoaPods.
After upgrading, I'm unable to compile our project due to errors in OneSignalFrame due to error No type or protocol named 'OSUser' / 'OSLiveActivities'
It seems to be related to using a Bridging Header, as the error seems to originate there. I've tried adding OneSignalLiveActivities and OneSignalOSCore to the Bridging Header as these files seem to live there; but to no avail.
Steps to reproduce?
1. Use version 5.2.6
2. Add `#import <OneSignalFramework/OneSignalFramework.h>` to your `SWIFT_OBJC_BRIDGING_HEADER`3. Try to run project
3. Get errors
What did you expect to happen?
I do not expect these errors to happen, as they did with the 5.0.2
OneSignal iOS SDK version
5.2.6
iOS version
15
Specific iOS version
Our project targets iOS 15
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
ndemie
changed the title
[Bug]: Importing OneSignalFramework.h in bridging header results in error - No type or protocol named 'OSUser' / 'OSLiveActivities'
[Bug]: Importing OneSignalFramework.h in bridging header results in error No type or protocol named 'OSUser' / 'OSLiveActivities'Nov 5, 2024
This issue only occurs for cross-platform projects, such as those containing .mm
For OneSignal team @nan-li
Could guys please consider addressing this issue in the next release? Currently, we’re unable to integrate the latest version of OneSignal in cross-platform projects, except for iOS native projects
Able to resolve this issue by adding OneSignal code in Swift file instead of Objective C.
i'm using the 5.1.3/5.1.6 workaround since 5.2.6/5.2.7 still has the No type or protocol named 'OSUser' / 'OSLiveActivities' error.
my appdelegate.mm didn't play nice when I tried to convert it to swift. is there any eta on when this will be fixed for objective c without having to downgrade?
What happened?
I upgraded our OneSignal SDK from 5.0.2 to 5.2.6 using CocoaPods.
After upgrading, I'm unable to compile our project due to errors in OneSignalFrame due to error
No type or protocol named 'OSUser' / 'OSLiveActivities'
It seems to be related to using a Bridging Header, as the error seems to originate there. I've tried adding
OneSignalLiveActivities
andOneSignalOSCore
to the Bridging Header as these files seem to live there; but to no avail.Steps to reproduce?
What did you expect to happen?
I do not expect these errors to happen, as they did with the 5.0.2
OneSignal iOS SDK version
5.2.6
iOS version
15
Specific iOS version
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: