React Native NativeModules Empty Object

5.3k views Asked by At

Trying to create my first npm module in order to determine if a user is on the phone. It's for a React Native app. No matter what I try, the module returns undefined. NativeModules always appears to be an empty object.

Please help! Below is a link to the code. export default RNOnPhoneCall; in index.js will only return undefined. How do I link the functions in ios folder, and export them in index.js? Heads up, android is not up to date yet, only ios.

Link to Github

3

There are 3 answers

1
Tori Huang On BEST ANSWER

I was not exporting the method correctly in my iOS file. Here's the solution, along with a link to the final project.

react-native-check-phone-call-status on github

#import "RNCheckPhoneCallStatus.h"
#import "React/RCTLog.h"
#import <AVFoundation/AVAudioSession.h>
#import<CoreTelephony/CTCallCenter.h>
#import<CoreTelephony/CTCall.h>

@implementation RNCheckPhoneCallStatus

RCT_EXPORT_MODULE()

RCT_EXPORT_METHOD(get:(RCTResponseSenderBlock)callback)
{
    NSString *phoneStatus = @"PHONE_OFF";
    CTCallCenter *ctCallCenter = [[CTCallCenter alloc] init];
    if (ctCallCenter.currentCalls != nil)
    {
        NSArray* currentCalls = [ctCallCenter.currentCalls allObjects];
        for (CTCall *call in currentCalls)
        {
            if(call.callState == CTCallStateConnected)
            {
                phoneStatus = @"PHONE_ON";
            }
        }
    }
    callback(@[[NSNull null], phoneStatus]);
}

@end
0
Blessing On

Try rebuilding your project. I faced the same issue recently and simply rebuilding resolved it

1
rule_it_subir On

After snooping around a little, I found out that the Obj-C file isn't added to the Compile Sources in Xcode. Just follow me: Let's say the file names are: NotchNative.h and NotchNative.m. If the NotchNative.m file is not listed, the files will not be compiled by Xcode hence it needs to be added to the Compile Sources.

enter image description here

Follow the steps in the image and rebuild/run the iOS app again. It's surely a fault on the Xcode side, as it doesn't happen in case of Swift projects.