React-native 0.60 -lPods-OneSignalNotificationExtension not found #838

jamesone · 2019-09-02T04:58:21Z

Description:

I've upgraded to React-native 0.60 and have followed the onesignal installation steps as shown here: https://documentation.onesignal.com/docs/react-native-sdk-setup

When I goto run the xcode application, I get an error relating to the OnesignalNotificationExtension.
Error: ld: library not found for -lPods-OneSignalNotificationServiceExtension

The OneSignalNotificationServiceExtension target has the following settings:

Header search paths: "${PODS_ROOT}/Headers/Public/react-native-onesignal"
Framework search paths: "${PODS_ROOT}/OneSignal/iOS_SDK/OneSignalSDK/Framework"

Environment

react-native-onesignal version: 3.3.2
react-native: 0.60.5

Steps to Reproduce Issue:

Followed the RN setup: https://documentation.onesignal.com/docs/react-native-sdk-setup
Run xcode project
Expect to see: ld: library not found for -lPods-OneSignalNotificationServiceExtension

The text was updated successfully, but these errors were encountered:

rgomezp · 2019-09-11T01:37:17Z

Howdy,
We released a new version yesterday. Can you please update and try again? Also try clearing your DerivedData folder located at /Users//Library/Developer/Xcode/DerivedData

Last thing to try is pod update from your ios directory

andreymyssak · 2019-09-14T05:18:42Z

@jamesone did you solve this problem? The answer from @rgomezp does not help.

mtannerfors · 2019-09-18T07:13:31Z

@rgomezp none of the above suggestions worked, using the latest release 3.4.1. Could do with some attention on this issue. Forced to remove OneSignalNotificationExtension until resolved, happy to try other suggestions/releases.

rizwanatta · 2019-09-19T18:28:52Z

+1 following !

rgomezp · 2019-09-19T18:53:58Z

Howdy,
Please try running pod deintegrate && pod install from the ios directory in your project

anniewey · 2019-10-01T01:47:55Z

Above suggestions are not working. Already updated to latest release v3.4.1, clean derived data, clean pods and reinstall but still getting error:

Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_RCTOneSignalExtensionService", referenced from:
      objc-class-ref in NotificationService.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Podfile.lock

  - react-native-onesignal (3.4.1):
    - OneSignal (= 2.11.0)
    - React (< 1.0.0, >= 0.13.0)

UPDATE:
My bad. Turns out I need to replace the NotificationService.m contents with the latest code in DOC. I was still using RCTOneSignalExtensionService.h. Upon updating, the error is gone.

rgomezp · 2019-10-01T23:22:54Z

Great to hear! Please comment if you are still struggling with this issue and I can reopen

Dhanraj-bidchat · 2019-12-15T12:57:04Z

Its still issue in RN:0.60.10 with pod.
how to use pod with it ?

jsellam · 2020-01-08T13:50:35Z

Hi,
I have same issue ld: library not found for -lPods-OneSignalNotificationServiceExtension
I'm using react-native 0.61.4 and onesignal 3.6.1

with pod deintegrate and cleaning and DerivedData

jsellam · 2020-01-08T16:19:43Z

I have found, but I don't know why, when I don't have a "Release" configuration in my configurations list, the "archive" fail with library not found.

archive fail :

archive succeed 👍

For your informations, Dev, Preprod & Prod are based on Release. It was working without "Release" on my olders projects with onesignal

Update @rgomezp :

Create a new react-native project
Add Onesignal
build & archive > it's ok
Rename "Release" configuration to an other name (like Dev)
build & archive > ld: library not found for -lPods-OneSignalNotificationServiceExtension

madun · 2020-02-13T04:06:13Z

Above suggestions are not working. Already updated to latest release v3.4.1, clean derived data, clean pods and reinstall but still getting error:
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_RCTOneSignalExtensionService", referenced from:
      objc-class-ref in NotificationService.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Podfile.lock
  - react-native-onesignal (3.4.1):
    - OneSignal (= 2.11.0)
    - React (< 1.0.0, >= 0.13.0)
UPDATE:
My bad. Turns out I need to replace the NotificationService.m contents with the latest code in DOC. I was still using RCTOneSignalExtensionService.h. Upon updating, the error is gone.

This not working for me

one-signal (3.6.2)
react-native (0.60.0)

MrAlekhin · 2020-02-18T19:50:32Z

Having the same issue right now. -lPods-OneSignalNotificationServiceExtension failed when i've added new schemes. Any updates on that?

roysG · 2020-04-15T12:58:17Z

same

Yassir4 · 2020-05-30T11:01:38Z

I had the same problem after upgrading react-native
This fixed my issue #651 (comment)

hamaron · 2020-07-28T18:32:11Z

I had the same problem when upgrading the RN version to 0.63.2 and trying to archive the app and I got fixed
by this.

It was a version mismatch between the version I specified in Podfile and the Target version that
I set for the OneSignal extension. As soon as I modified those two values to match each other,
the problem was gone.

Podfile

OneSignalNotificationExtension (or whatever you named to the notification extension)

scesbron · 2020-09-11T08:58:50Z

I have the same problem but none of the tips above solved my problem.

I have 2 projects that are quite similar : one that works and other that does not work.

In xcode build and archive steps are ok but on my CI or on my computer the command below succeeds on one project but fails on the other

xcodebuild "-workspace" "/Users/vagrant/git/packages/mobile-pro/ios/WecasaPro.xcworkspace" "-scheme" "WecasaPro" "-configuration" "Staging" "COMPILER_INDEX_STORE_ENABLE=NO" "archive" "-archivePath" "/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/__archive__581470914/WecasaPro.xcarchive" "-destination" "generic/platform=iOS" | xcpretty

If I look at the logs of the command. For the project that works I have

▸ Building Pods/Pods-OneSignalNotificationServiceExtension [Staging]
▸ Check Dependencies
▸ Compiling Pods-OneSignalNotificationServiceExtension-dummy.m
▸ Compiling Pods-OneSignalNotificationServiceExtension-dummy.m
▸ Building library libPods-OneSignalNotificationServiceExtension.a
▸ Building library libPods-OneSignalNotificationServiceExtension.a
▸ Building WecasaPro/OneSignalNotificationServiceExtension [Staging]
▸ Check Dependencies
▸ Processing Info.plist
▸ Running script '[CP] Check Pods Manifest.lock'
▸ Compiling NotificationService.m
▸ Linking OneSignalNotificationServiceExtension
▸ Generating 'OneSignalNotificationServiceExtension.appex.dSYM'
▸ Touching OneSignalNotificationServiceExtension.appex
▸ Signing /Users/vagrant/Library/Developer/Xcode/DerivedData/WecasaPro-fuytaarwfdjqjucxpzvnzgjrhcvd/Build/Intermediates.noindex/ArchiveIntermediates/WecasaPro/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/OneSignalNotificationServiceExtension.appex
▸ Touching OneSignalNotificationServiceExtension.appex.dSYM

For the project that does not work I have

▸ Compiling Pods-OneSignalNotificationServiceExtension-dummy.m
▸ Compiling Pods-OneSignalNotificationServiceExtension-dummy.m
▸ Running script 'Copy generated compatibility header'
▸ Building library libPods-OneSignalNotificationServiceExtension.a

I checked the config of both projects several times and they seem to be similar.

Does anyone have a clue on what can cause this ?

scesbron · 2020-09-11T10:35:15Z

After comparing my logs for the two projects I found that the one that succeeds uses the legacy build system but the other one uses the new build system.

I switched the projet to legacy build system but the problem is still there.

On the project that succeeds I have

CompileC /Users/scesbron/Library/Developer/Xcode/DerivedData/WecasaPro-guwmidkqvxjubvhfovvxnfhourjd/Build/Intermediates.noindex/ArchiveIntermediates/WecasaPro/IntermediateBuildFilesPath/Pods.build/Staging-iphoneos/Pods-OneSignalNotificationServiceExtension.build/Objects-normal/arm64/Pods-OneSignalNotificationServiceExtension-dummy.o Target\ Support\ Files/Pods-OneSignalNotificationServiceExtension/Pods-OneSignalNotificationServiceExtension-dummy.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler

and then

Libtool /Users/scesbron/Library/Developer/Xcode/DerivedData/WecasaPro-guwmidkqvxjubvhfovvxnfhourjd/Build/Intermediates.noindex/ArchiveIntermediates/WecasaPro/IntermediateBuildFilesPath/Pods.build/Staging-iphoneos/Pods-OneSignalNotificationServiceExtension.build/Objects-normal/armv7/libPods-OneSignalNotificationServiceExtension.a normal armv7

but on the other project after the compile I have a Ld command

Ld /Users/scesbron/Library/Developer/Xcode/DerivedData/wecasa-hcsnerxmdxdzhhhetgrrfvjexliq/Build/Intermediates.noindex/ArchiveIntermediates/wecasa/IntermediateBuildFilesPath/wecasa.build/Release-iphoneos/OneSignalNotificationServiceExtension.build/Objects-normal/armv7/OneSignalNotificationServiceExtension normal armv7

I don't know what is the difference between these commands and I don't know why the sequence is not the same

scesbron · 2020-09-11T13:45:45Z

Last comment on my problem. I removed the OneSignalNotificationServiceExtension target, the related objective-c files and the reference to OneSignal in my podfile. The xcodebuild command succeeds.

I've added back one signal by doing all the steps described in the doc https://documentation.onesignal.com/docs/react-native-sdk-setup

After that my xcodebuild command still fails on

Ld /Users/scesbron/Library/Developer/Xcode/DerivedData/wecasa-hcsnerxmdxdzhhhetgrrfvjexliq/Build/Intermediates.noindex/ArchiveIntermediates/wecasa/IntermediateBuildFilesPath/wecasa.build/Release-iphoneos/OneSignalNotificationServiceExtension.build/Objects-normal/armv7/Binary/OneSignalNotificationServiceExtension` normal armv7

the /Users/scesbron/Library/Developer/Xcode/DerivedData/wecasa-hcsnerxmdxdzhhhetgrrfvjexliq/Build/Intermediates.noindex/ArchiveIntermediates/wecasa/IntermediateBuildFilesPath/wecasa.build/Release-iphoneos/OneSignalNotificationServiceExtension.build/Objects-normal/armv7/Binary folder is empty, it does not contain a OneSignalNotificationServiceExtension file.

pellarboss · 2020-09-19T06:13:00Z

I have the same issue

zanechua · 2021-06-04T13:09:22Z

So...

This was a really hard one to trace down, I had to recreate a new RN 064.1 project to really find the fix to my issues. I am using schemes in my projects and I was applying fixes so that it'll build properly on M1.

Since the project has updated to using the new OneSignalXCFramework instead of the old fat framework, I decided to update the NSE to use that too in Podfile.

Was facing a ton of issues where the module was not found, including this one during build a release build or building to the simulator or a device

Turns out the part that was screwing with my code and causing the whole issue to not work is this following section in the Podfile

installer.pods_project.build_configurations.each do |config|
    config.build_settings["EXCLUDED_ARCHS[iphonesimulator=*]"] = "arm64"
end

In the end I had to only apply it to debug builds and not release builds. I'm not an iOS dev, so I don't know the intricacies on how excluding a simulator from an architecture would cause Pods to not be detected for the NSE but that was my issue.

Removing the entire block was what fixed it for me. Seems like it's not needed anymore for my project at least.

agungs17 · 2021-09-03T19:21:49Z

same issue!

aeliusventure · 2021-09-03T21:40:33Z

We tried with

post_install do |installer|
flipper_post_install(installer)
installer.pods_project.build_configurations.each do |config|
config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end
end

in podfile

and

OneSignalNotificationServiceExtension -> deployment Info

iOS 13.0

and set in same group, we tested and succesfully build and run well.

lurdharry · 2021-12-01T12:27:37Z

I had the same problem when upgrading the RN version to 0.63.2 and trying to archive the app and I got fixed by this.

It was a version mismatch between the version I specified in Podfile and the Target version that I set for the OneSignal extension. As soon as I modified those two values to match each other, the problem was gone.

Podfile

OneSignalNotificationExtension (or whatever you named to the notification extension)

this solution works for me react-native-onesignal (4.3.3) and react-native": "0.64.2

rgomezp added the Help Wanted label Sep 16, 2019

rgomezp closed this as completed Oct 1, 2019

scesbron mentioned this issue Sep 11, 2020

React-native 0.62 -lPods-OneSignalNotificationExtension not found #1042

Closed

naveenPaulsingh mentioned this issue Dec 20, 2021

OneSignal.h not found when updating from 3.x to 4.x [iOS] #1236

Closed

jparksecurity mentioned this issue Jan 10, 2022

ld: library not found for -lPods-OneSignalNotificationServiceExtension OneSignal/onesignal-expo-plugin#42

Closed

nan-li mentioned this issue Mar 11, 2022

ld: library not found for -lPods-OneSignalNotificationServiceExtension #1369

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

React-native 0.60 -lPods-OneSignalNotificationExtension not found #838

React-native 0.60 -lPods-OneSignalNotificationExtension not found #838

jamesone commented Sep 2, 2019

rgomezp commented Sep 11, 2019 •

edited

andreymyssak commented Sep 14, 2019

mtannerfors commented Sep 18, 2019 •

edited

rizwanatta commented Sep 19, 2019

rgomezp commented Sep 19, 2019

anniewey commented Oct 1, 2019 •

edited

rgomezp commented Oct 1, 2019

Dhanraj-bidchat commented Dec 15, 2019

jsellam commented Jan 8, 2020 •

edited

jsellam commented Jan 8, 2020 •

edited

madun commented Feb 13, 2020

MrAlekhin commented Feb 18, 2020

roysG commented Apr 15, 2020

Yassir4 commented May 30, 2020

hamaron commented Jul 28, 2020 •

edited

scesbron commented Sep 11, 2020

scesbron commented Sep 11, 2020

scesbron commented Sep 11, 2020

pellarboss commented Sep 19, 2020

zanechua commented Jun 4, 2021 •

edited

agungs17 commented Sep 3, 2021

aeliusventure commented Sep 3, 2021

lurdharry commented Dec 1, 2021

React-native 0.60 -lPods-OneSignalNotificationExtension not found #838

React-native 0.60 -lPods-OneSignalNotificationExtension not found #838

Comments

jamesone commented Sep 2, 2019

rgomezp commented Sep 11, 2019 • edited

andreymyssak commented Sep 14, 2019

mtannerfors commented Sep 18, 2019 • edited

rizwanatta commented Sep 19, 2019

rgomezp commented Sep 19, 2019

anniewey commented Oct 1, 2019 • edited

rgomezp commented Oct 1, 2019

Dhanraj-bidchat commented Dec 15, 2019

jsellam commented Jan 8, 2020 • edited

jsellam commented Jan 8, 2020 • edited

madun commented Feb 13, 2020

MrAlekhin commented Feb 18, 2020

roysG commented Apr 15, 2020

Yassir4 commented May 30, 2020

hamaron commented Jul 28, 2020 • edited

scesbron commented Sep 11, 2020

scesbron commented Sep 11, 2020

scesbron commented Sep 11, 2020

pellarboss commented Sep 19, 2020

zanechua commented Jun 4, 2021 • edited

agungs17 commented Sep 3, 2021

aeliusventure commented Sep 3, 2021

lurdharry commented Dec 1, 2021

rgomezp commented Sep 11, 2019 •

edited

mtannerfors commented Sep 18, 2019 •

edited

anniewey commented Oct 1, 2019 •

edited

jsellam commented Jan 8, 2020 •

edited

jsellam commented Jan 8, 2020 •

edited

hamaron commented Jul 28, 2020 •

edited

zanechua commented Jun 4, 2021 •

edited