Skip to content
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]: Importing OneSignalFramework.h in bridging header results in error No type or protocol named 'OSUser' / 'OSLiveActivities' #1512

Open
1 task done
ndemie opened this issue Nov 5, 2024 · 5 comments

Comments

@ndemie
Copy link

ndemie commented Nov 5, 2024

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 and OneSignalOSCore to the Bridging Header as these files seem to live there; but to no avail.

Screenshot 2024-11-05 at 13 57 37

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
@ndemie 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
@ndemie
Copy link
Author

ndemie commented Nov 5, 2024

Similar, unsolved, issue in the react-native-onesignal repo; OneSignal/react-native-onesignal#1717

@ManjunathaReddyNS
Copy link

Any update on this issue?

@ManjunathaReddyNS
Copy link

ManjunathaReddyNS commented Nov 14, 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

@ManjunathaReddyNS
Copy link

Able to resolve this issue by adding OneSignal code in Swift file instead of Objective C.

@MrSco
Copy link

MrSco commented Nov 21, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants