[Bug]: Onesignal SDK is not supported with iOS Xcode 15 Beta #1274
Comments
|
I tested Xcode 15 Beta 5 today and seems like the issue is no longer occurring? We had the described issue during beta 1, 2, 3 and 4 of Xcode 15, but without any change in our app it now builds using beta 5. Maybe Apple changed something? |
|
Hello! Please help :) |
|
@pawellazarew Hello what package manager are you using to integrate OneSignal and which version are you using? |
|
closing due to inactivity |
|
@emawby I don't think this issue must be closed as it is not fixed or resolved. OneSignal team has not asked any question related to the original question, rather only commented for a different issue to @pawellazarew. You must at least give some effort to fix the original bug, rather closing it due to inactivity of other members who only had commented some different issues faced |
|
I got the same issue when compiling. XCode 15 beta 8. ReactNative 0.68.2 Please reopen the issue cause this bug makes the app unbuildable --- We have a deadline and we should publish it without OneSignal support. The only way to get the app build is to remove OneSignal from the bundle. |
|
I would try the following: 
It should now look like this |
|
@emawby i am able to fix the issue by removing OneSignalNotificationServiceExtension from my app's main target, and still having OneSignal framework in both my app's main target and in OneSignalNotificationServiceExtension target. notification's are working fine without including OneSignalNotificationServiceExtension in my app's main target |
|
@kmrinmoy07 If you do not include the NotificationServiceExtension you are able to receive push, but you will be missing many features such as images, custom buttons, confirmed deliveries, etc. |
|
@emawby i am still able to find images in my notifications. as you have suggested this is not a preferred solution, so what should i do to fix this issue, when i have added onesignal framework into both my app's main target and also to NSE's target, and also have added NSE into my app's main target |
|
@kmrinmoy07 It looks like there are similar issues reported on other frameworks. Could you try this workaround from the firebase version of this issue? |
Tried to apply your solution, but still got a crash on startup, seems that can't find the file, what I'm missing?
|
|
@bertidesign How do you import OneSignal in your main App target? Also what are your runpath search paths? |
|
Bump this is blocking us |
|
I had the same issue on Xcode 15 with one signal 5.0.2 |
I have resolved this issue by moving the Embed Foundation Extension from below to under Copy Bundle Resources. It is the relevant issue, you may found something useful here. |
|
Hi everyone reporting, checking if if this is still an issue? |
What happened?
The OneSignal SDK is not supported with latest Xcode 15 Beta versions. It gives error - Cycle inside MYAPPTARGET; building could produce unreliable results. I have checked with 5.0.0 beta version and 3.12.5 versions of the library but same result in both, I have tested including the library both using CocoaPods and Swift Package Manager but still the same.
Totally removing the library from framework, libraries and embedded content and also removing the OneSignalNotificationServiceExtension.appex from my embedded app extension of my main app's target, is the only way to run my project currently.
It didn't work even deleting the DerivedData folder or cleaning the project.
Steps to reproduce?
What did you expect to happen?
I expected the project to get build, but it fails building
OneSignal iOS SDK version
3.12.5
iOS version
15
Specific iOS version
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: