Building for arm64 Architecture
#1260
Assignees
Labels
Comments
|
did you find any solution to this issue ?? I am facing it as well |
Not yet, hoping for a dev reply that can help fix the issue. |
|
@Cryptobyte Can you show your podfile for the NotificationServiceExtension? |
Thanks for the reply, yes I'm still using |
|
I am having this problem as well, and I'm using And here's the error I'm getting: And here are the warnings/errors |
|
I am having the exact same issue above ^^^^ BUMP! |
|
Same issue here |
|
try this |
|
@piotrlo TY! this worked! It didnt work in xcode but when i ran |
Thanks for the suggestion, I tried this and updated my NotificationServiceExtension to this: and now I'm getting this issue via XCode and Tried Clean Project, Clean Project Folder and removing Derived Data none of which changed or solved the build error. |
So i didn't update my Podfile to the new OneSignalXCFramework. I omitted that step. Maybe try again without updating it and see if it works? shot in the dark to help you out. |
|
Howdy, |
Just tried all of these, still running in to the same issue. Here's what I have in my configuration right now:
I tried:
Not sure if it helps but I'm using XCode Version 12.5.1 (12E507) |
|
Facing the same issues as @Cryptobyte. None of the above mentioned solutions seems to work. Any ideas? |
|
@Cryptobyte @JoFlo07 & all others, |
|
@rgomezp Thank you for your reply. I updated the pods and I am using now the XCFramework as well as the latest npm distribution. I still got another error afterwards, but this was not related to OneSignal. Now it seems to work. |
Same here, updated and fixed OneSignal related issues. Thanks for the help everyone! |
|
I'm still having this issue, updating to the latest version didn't fix it. Anyone else having this issue after updating to the latest version? |
|
@danlupascu , It seems Cryptobyte was able to solve by cleaning the DerivedData folder (amongst other things mentioned above). Could you please give that a shot? |
|
@rgomezp I just removed DerivedData folder, tried again and it didn't help, I'm still having the same issue. Npm package version: We have this in Here's the error again: |
|
Howdy, (this should be at the same level as the main target) |
|
@rgomezp hey, it's outside, at the same level as the main target. Here's the full |
|
@danlupascu , Perhaps try Cheers |
|
@rgomezp still not working, I'm getting the same exact error. I removed the |
|
Howdy @danlupascu , Unfortunately, I think this is likely being caused by something specific to your setup. One thing you can try is building a test-app from scratch and trying to reproduce the issue. If you reproduce it, you can send it to us and we'll try taking a look to see what we can gather. |
|
@rgomezp unfortunately I don't have enough time to build a test up from scratch at the moment. Maybe someone that's having the same problem has a test app and can share it with you. Anyone? |
|
@danlupascu , |
|
Still now working. I updated the library, cleaned derived data folder and cleared pods cache as well |
|
Howdy folks thanks for your patience. So what we have found is that most likely this is being caused by using Swift in the NSE target. If that is the case, please switch to Objective-C. The other possibility is that the targets must match across targets (main and NSE). So if you're using swift on one, use swift on the other -- obj-c on one, use obj-c on the other. Hope this helps. |
|
Somebody can resolve this case |
|
Just throw in the towel and open Xcode in Rosetta. Right-click Xcode.app, select "Get Info" and check "Open using Rosetta".
|
It works. Thanks so much |
|
Hello guys, We tested pretty much all of the suggestions on this thread (except using Rosetta) and ended getting it to work with a few changes on an M1 MacBook.
which would result in the following error:
To fix this we added a post-install step to the Podfile to ensure that all Pods' targets are excluding arm64:
Hope this helps someone! Cheers |
|
Hi, @devmod I followed the steps and I've encountered this issue. Am I missing something here?
|
|
Same result. Did you fix it? @peter-indiola |
|
@peter-indiola I'm also running into the same issue reported here by @serdargun - Does anyone have a solution for the "No such module 'OneSignal'" error? |
|
Struggled a lot with this issue and I don't know why but here is what worked for me @trev91 :
|
|
still wasn't able to run this. Is OneSignal team saying this is fixed? |
|
Hi guys, I've got exactly the same issue as @danlupascu had. I use Objective-C as @rgomezp said and manage to make it working
Hope it help
|
|
Hi all, |
This was referenced Jun 3, 2022
|
Closing for now because of no response. Feel free to reopen if the issue persists. |
|
I'm on intel in a new project and I do get this error of 'no such module'. Pretty frustrating. I did follow their documentation, read some stack overflow and github issues. There is no clear answer on what to do to get this error away and be able to build. And this issue is open from a year ago. Wow. |
|
I do get the error of 'No such module'. It's funny or sad (for sure frustrating) that there is no clear solution on how to resolve that error. Switching to Objective-C because Swift does not work is not a good solution. |
|
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. |
Thanks, man! Works! |
|
Hey guys, I am also facing the same error(No such module 'OneSignal') and also (Stored properties cannot be marked potentially unavailable with '@available'). how I get rid of these errors: => firstly I update my Pod file version too (platform: ios, '13.0') after this I solve (No such module 'OneSignal') error like this; add this line in the pod filepod 'OneSignalXCFramework', '>= 3.0.0', '< 4.0' target 'OneSignalNotificationServiceExtension' do => run pod update && pod install in terminal |
|
sideways move suggestion, now I have |
|
Tried @RikoLogwirno's solution to switch the OneSignal target to Objective-C, and getting this error:
Tried @devmod's solution to exclude arm64 from build configurations, which allows for a successful build, but launching the app in the iOS simulator crashes with:
Of course it all works if I use Rosetta 2... Update: after migrating to RN 0.71 and disabling flipper, I'm able to build and launch, but the app is stuck on the splash screen and metro is never called. in iOS 16.2 simulator (arm64), I get: in iOS 13.7 simulator (x86), I get: Using Xcode 14.2 on a M2 Pro. |
|
any update with this? I got crazy... activating Rosetta leads to same error, I do hard clean between each run rm -rf ~/Library/Developer/Xcode/DerivedData |
|
this is what happened to me, I upgraded Xcode to 14.3.1 then downgraded to 14.2. |
|
Same problem since trying to upgrade React 0.63.3 to 0.72.4 ERROR : ld: library not found for -lPods-OneSignalNotificationServiceExtension In my Podfile I had : Then update it to suggested fix : Result : How to fix that please? |
|
https://documentation.onesignal.com/docs/ios-sdk-setup#4-notification-service-extension maybe in the objective-c file, write |
|
same issue here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Description:
Trying to build an existing RN app on
arm64intentionally as Monterey has introduced an issue with running non-arm64apps in the simulator. OneSignal XCode build is failing onarm64architecture. I have seen the other issues related toarm64however the solution seems to always be excluding thearm64architecture which is not an option in my case. Is there any way to makereact-native-onesignalwork onarm64?Environment
OneSignal React-Native SDK (
4.2.0) viayarnSteps to Reproduce Issue:
4.2.0) OneSignal React-Native SDKarm64simulatorAnything else:
The text was updated successfully, but these errors were encountered: