React Native Notifications

Overview


React Native Notifications

npm Build Status npm (tag) npm (tag)

Handle all the aspects of push notifications for your app, including remote and local notifications, interactive notifications, silent notifications, and more.

All the native iOS notifications features are supported!

For information regarding proper integration with react-native-navigation, follow this wiki.

Requirements

Apps using React Native Notifications may target iOS 10 and Android 5.0 (API 21). You may use Windows, macOS or Linux as your development operating system.

iOS

Interactive notifications example

  • Remote (push) notifications
  • Local notifications
  • Background/Managed notifications (notifications that can be cleared from the server, like Facebook messenger and Whatsapp web)
  • PushKit API (for VoIP and other background messages)
  • Interactive notifications (allows you to provide additional functionality to your users outside of your application such as action buttons)

Android

  • Receiving notifications in any App state (foreground, background, "dead")
  • Built-in notification drawer management
  • High degree of code extensibility to allow for advanced custom layouts and any specific notifications behavior as available by Android's API
  • Android equivalent of React-Native's implementation of PushNotificationsIOS.getInitialNotification().

Upcoming: local notifications, background-state Rx queue (iOS equivalent)

Quick Links

License

The MIT License.

See LICENSE

Comments
  • Android overhaul (includes important bug fixes and new functionality)

    Android overhaul (includes important bug fixes and new functionality)

    This is a mammoth pull request, and I know that's a pain for maintainers. So I've tried to make this as easily digestible as possible. I've elaborated on the motivation for the changes below, and although I didn't write it that way, I've gone back and split this into smaller feature commits so they can each be evaluated some-what individually.

    • c967bff484f3313420429e0e3c7ab76c3669aa5b - Migrate to FCM and refactor

    This is the largest commit of the lot, but mostly does what it says. The motivation for upgrading from GCM (deprecated) to FCM is pretty obvious but some of the refactoring probably needs further explanation/justification.

    In particular I've completely done away with the concept of PushNotification and split its functionality into two classes, LocalNotification and RemoteNotification, which are slightly more limited in scope.

    This is a breaking change to the Android Java API.

    Additionally PushNotificationProps has been changed to NotificationProps to highlight its dual role and had its behaviour adjusted to more accurately represent Google/Firebase's concept of a notification. In particular, Firebase RemoteMessage class does not bundle end-user data arguments in with UI notification properties. Notification properties and "data" are distinct concepts.

    NotificationProps contains a getData() method to return the data only, the notification properties can be accessed by their corresponding accessor methods. This flows over into JS where there is a property called data, which should take a JS object and all user/custom data should be part of that object, not as part of the top-level notification. This is also a breaking change.

    These breaking changes weren't made arbitrarily or even to keep the project neat. They're actually required to facilitate correct function. In particular we need to be able to reliably determine whether a notification is "data only" so that JS consumers know under which context a notification is being delivered to them. I believe this is something that was perhaps missed by the original author of this functionality, but there are very distinct rules under which notifications are delivered to running applications. I've actually explained these rules in a README update (later commit) but the official Firebase reference explains in detail.

    The final breaking change is that RemoteNotification does not automatically post a local notification when a push/remote notification is received (in the foreground). This is important as it gives JS consumers control over when they'd like to display notifications and also what information they include in said notifications. Firebase does not support several options (large icons, LED lighting) etc.

    Android now supports cancelAllLocalNotifications.

    • ae36e8a3b89ebddbf31743870beeab03230f420b - Namespace globally broadcast JS events

    Fairly self explanatory, this is necessitated by the fact Android's JS events are broadcast "globally", so it's best to avoid any accidental interference by name-spacing.

    • 521f0c7e3bd9d4003f9361b63267987764fd1e55 - Support FCM token invalidation

    A simple mechanism to invalidate push tokens. This can be used for example when a user logs out to ensure the app stops receiving notifications.

    • 98424119cfb51eacaf8ee1503dab9fbed3eb2ee2 - Fixed initial intent behavior for background notifications

    I've covered this pretty thoroughly in the README and it relates to the "data-only" changes mentioned above (first commit) - or in this case, when the notification isn't data-only. If the system tray receives our push notification because the app was backgrounded, at the moment there's no way to tell when the user launched the app by tapping that notification - this commit corrects that situation.

    • faf442e27c5e27989e51fdd90a8fa510fc6db4d0 - Do not automatically dismiss all notifications

    This is about giving control to JS consumers. At present any time the app is launched all notifications are dismissed. That's likely to be undesirable for many use cases, particularly when a user has received multiple push notifications pertaining to different components of the app. The support that was added (first commit) for cancelAllLocalNotifications() means users can still achieve this effect if it's desirable. This is a breaking change with respect to default expected behaviour.

    • 812ced326fd8cece8850dee02ed879e0558297c8 - Android large icon support (URL or drawable name)

    This is actually pretty dang nifty. It's now trivial to specify largeIcon appears in the notification (typically used in messaging apps as profile pictures). Fresco (React Native's image manager) is used to download the images if they're specified as remote URLs - it takes care of caching and what-not.

    Additionally, file:// URLs are supported, which is what React Native converts require("./some_image.jpg") syntax to in JS. So React Native bundled images can seamlessly be used in addition to remote images.

    • de8c172949c76531dbb2c04f96fdfde6c2bc48ea - Minor code simplification/clean-up

    Just a nit. Nothing particularly important or pressing.

    • f084ebd5b3cfcb55b8422d5ab7aaec01a14d24b4 - Move getInitialNotification() NotificationsAndroid (match iOS)

    Got rid of PendingNotifications, as it was an unnecessary namespace. This is a breaking change.

    • 59c6237552ac4bd130d83fb9120d8576b3f86ccb - Android lights/LED support

    Added support for controlling the LED notification light i.e. What Facebook and similar apps do.

    Firebase (system tray) remote notifications are actually incapable of achieving this, so it's one of many very good reasons to send "data-only" notifications and generate local notifications from the content.

    • 7ff0123cd8c3c672aca7026d5e412ebb77c7d7b4 - Android README updates

    • dc3e4626f00fb2bb0b987360b60f438f6b07f760 - Expose invalidateToken() to JS

    Expose invalidateToken() implemented in 521f0c7e3bd9d4003f9361b63267987764fd1e55 to JS.

    • 3c1f7a72c43e47621f6dadd4e34c6f02ee2f4e72 - Fixed native Android test compilation

    Ensure the Android native tests compile correctly with the latest changes.

    • 835cd866461d72ff4663410ad927100c96faac33 - Refactored ProxyService into LocalNotificationService

    General clean-up and removal of dead/unnecessary code.

    • ff3ae152b3f57be9fb2ba2f29572214ad642974b - Android background queue

    Fixed (or rather added) proper background notification support. Android needs a background queue, for precisely the same reasons iOS needs one. Therefore, I've added NotificationsAndroid.consumeBackgroundQueue().

    Events won't be delivered at all unless this is called, which is a breaking change, but the same behaviour as iOS. I've updated the documentation accordingly. In doing so I've also addressed some misleading advice / sample code. In particular the (iOS) documentation showed adding and removing event listeners inside components. This is incorrect, "cold start" background notifications will not immediately be received by your listener if they're added inside a component, as the component hierarchy does not exist at all until your app is foregrounded.

    • a207aa4235f6e6ed85463e81d06b889dda7ad50d - RN 0.47 support (handle Android breaking change)

    Probably easiest way to explain this is just to refer to the discussion/PR for the same change merged into react-native-maps - https://github.com/airbnb/react-native-maps/pull/1481.

    • 9edcddf66e838f3d0ade945deba54e81937fde22 - Updated README installation instructions for Android.

    Prior to this commit, there were issues with multiple versions of Firebase being included due to a bug in the Google Services plugin. This commit provides updated installation instructions that work-around the bug in the Google Services plugin.

    --

    If you made it all the way through that then your time was hugely appreciated. You deserve a gold star! ⭐️

    I'm certainly open to feedback and happy to correct code style issues and what-not.

    🏚 stale 
    opened by Benjamin-Dobell 53
  • Notification Event Callbacks are not Firing on iOS

    Notification Event Callbacks are not Firing on iOS

    Thanks for picking up the task of being the only free and maintained PN library for react-native 🙏

    react-native: 61.0 react-native-notifications: 3.1.4

    I have followed the installation instructions exactly as outlined, and have picked up a few additional snippets from other github issues that have helped me get to a perfectly functioning Android implementation for foreground, background (warm) and background (cold) notifications.

    Im having some issues on iOS though, namely none of the native event callbacks are firing: registerNotificationOpened registerNotificationReceivedBackground registerNotificationReceivedForeground

    I am receiving push notifications on iOS and when I press the notification banner, none of those callbacks are triggered.

    It may be worth noting that getInitialNotification is working on iOS.

    I've searched every issue and am at a loss. Any ideas what I may have improperly configured, or is anyone else experiencing this?

    I'm using firebase to send the actual remote notifications.

    🏚 stale 
    opened by rynpatk 52
  • postLocalNotification - fireDate ignored

    postLocalNotification - fireDate ignored

    In React Native 0.61.5 react-native-notifications 3.1.1

    On android it doesn't matter what date i pass as fireDate, the notifications is fired immediately.

    const someLocalNotification = Notifications.postLocalNotification({
        fireDate: addSeconds(new Date(), 15),
        body: 'Local notificiation!',
        title: 'Local Notification Title',
      });
    
    Android type: accepted/bug 🏚 stale 
    opened by tststs 44
  • Android Compile Error

    Android Compile Error

    I met android compile error. react-native: 0.63.2 react-native-notifications: 3.3.0

    Log is like this. react-native-notifications: 3.2.2 works good.

    1: Task failed with an exception.

    • Where: Build file '/node_modules/react-native-notifications/lib/android/app/build.gradle' line: 4

    • What went wrong: A problem occurred evaluating project ':react-native-notifications'.

    Plugin with id 'kotlin-android' not found.

    • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. ==============================================================================

    2: Task failed with an exception.

    • What went wrong: A problem occurred configuring project ':react-native-notifications'.

    compileSdkVersion is not specified. Please add it to build.gradle

    • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. ==============================================================================

    • Get more help at https://help.gradle.org

    🏚 stale 
    opened by jihokim2 40
  • setRegistrationTokenUpdateListener does not return the deviceToken

    setRegistrationTokenUpdateListener does not return the deviceToken

    I am moving from react-native-push-notification to this one because of the conflict of the RNN-RNPN. However, it does not work in my case. PendingNotifications.getInitialNotification returns undefined and NotificationsAndroid.setRegistrationTokenUpdateListener does not returns deviceToken. I can see the result and correct response in Android monitor Logging (App initialized => publishing existing token (dc5oJgMT-qw:APA ...). But, I cannot get any response from JS. What can I do with that? I also try the example of this one. https://github.com/chrise86/rn-notification-navigation It gives me the same result.

    Android/core 🏚 stale 
    opened by seanlau555 34
  • [v3] registerNotificationOpened not triggered on Android

    [v3] registerNotificationOpened not triggered on Android

    I previously had an issue with sending data to my device (https://github.com/wix/react-native-notifications/issues/497). Solved this by changing the payload to (Amazon SNS):

    {
       "GCM":" {
           \"notification\": {
               \"title\": \"title\", 
               \"body\": \"Sample message for Android endpoints\" 
           }, 
    }
    

    But I still think I the docs can be more clear about how to implement a custom FirebaseMessagingService. Right now I want to send data to my app, I'm not sure if this works without a custom FirebaseMessagingService or how to implement one.

    Although with the custom messages send via Amazon SNS are now shown on my Android device, the registerNotificationOpened event is not triggered when I click the notification (on iOS it is). How can I resolve this?

    I want to open a certain screen when opening the notification based on data send with the notification.

    Do I have to add the custom FirebaseMessagingService to my app to handle data? How can I implement this? Tried sending another payload as stated in the docs (https://firebase.google.com/docs/cloud-messaging/concept-options) with the apns key, but it didn't work out as expected. The registerNotificationOpened was not triggered and the data was not parsed in the same way as on iOS where everything works without any hassle.

    Thanks for the help in advance.

    🏚 stale 
    opened by rnnyrk 33
  • What is the best way to use it with RNNavigation?

    What is the best way to use it with RNNavigation?

    Hi, guys! Thanks for your libraries they are great. I have a question what is the best way to use RNNotifications with RNNavigation. In docs it says to subscribe to notifications in componentWillMount and remove listeners in componentWillUnmount of the root component e.g. App or something, but with RNNavigation we don't have one. We start App with startSingleScreenApp and that's it. Of course I can subscribe for notifications before call to startSingleScreenApp, but I won't be able to remove listeners. So what is a best practice to deal with it how should I use it with RNNavigation? Thanks in advance.

    opened by Elf2707 32
  • The local notification is not visible

    The local notification is not visible

    I have follow the instruction to install the lib in Xcode 9. I use local notification for my app and run in simulator iPhone 6 and run in real device iPhone 7 but the notification is not visible. Please help me My snippet code to show notification

    _let localNotification = NotificationsIOS.localNotification({ alertBody: "Local notificiation!", alertTitle: "Local Notification Title",

        silent: false,
    	category: "SOME_CATEGORY",
    	userInfo: { }
    });_
    
    🏚 stale 
    opened by googlecomvn 27
  • notificationReceivedBackground didn't fire

    notificationReceivedBackground didn't fire

    I have run the example, notificationReceivedForeground and notificationOpened work fine.But notificationReceivedBackground didn't fire, is there any possible reason cause this?

    bug iOS/background-notifications 🏚 stale 
    opened by waynehong 27
  • registerNotificationReceivedBackground listener not triggered on Android when App is in background

    registerNotificationReceivedBackground listener not triggered on Android when App is in background

    Using Android, when App is in background, notification gets displayed on tray but registerNotificationReceivedBackground event is not triggered. This event is important to trigger the App do a service api call. Especially, if the user happens to dismiss the notification. The App never knew a notification arrived. [This flow works fine on iOS.]

    • I have tried latest version (v3.3.2) and even went back to v3.2.* versions and same behavior
    • It appears same issue was reported on 2/3 for v3.1 https://github.com/wix/react-native-notifications/issues/478, unresolved and was closed by stale bot.
    • I even tried to debug Native code PushNotification.java and the other java files. I've put system.out.println() to what i think would be the likely functions that will get called, e.g. notifyReceivedToJS(), but none of the functions were triggered when the notification is received while app is in background. It seems the App is disconnected during this state
    1. Is this a known issue that will eventually be resolved?
    2. Is there a work around that I could try? Or how has the others worked around this?

    Thanks!

    Android type: accepted/bug 🏚 stale 
    opened by reeinohio 25
  • Anybody has exactly instruction how to setup react-native-notifications for RN 0.60.4

    Anybody has exactly instruction how to setup react-native-notifications for RN 0.60.4

    I can't setup react-native-notifications for RN 0.60.4. "react-native-notifications": "2.0.3",

    /android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:66: error: constructor RNNotificationsPackage in class RNNotificationsPackage cannot be applied to given types;
          new RNNotificationsPackage(),
          ^
      required: Application
      found: no arguments
      reason: actual and formal argument lists differ in length
    
    🏚 stale 
    opened by iutin 24
  • android device does not show push notification

    android device does not show push notification

    minSdkVersion = 21
    compileSdkVersion = 33
    targetSdkVersion = 33
    

    System: OS: macOS 12.5.1 CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz Memory: 391.32 MB / 16.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 14.17.4 - /usr/local/bin/node Yarn: 1.22.11 - /usr/local/bin/yarn npm: 7.20.3 - /usr/local/bin/npm Watchman: 2021.08.02.00 - /usr/local/bin/watchman Managers: CocoaPods: 1.11.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5 Android SDK: Not Found IDEs: Android Studio: 2020.3 AI-203.7717.56.2031.7583922 Xcode: 13.3/13E113 - /usr/bin/xcodebuild Languages: Java: 11.0.12 - /usr/bin/javac npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.63.4 => 0.63.4 react-native-macos: Not Found npmGlobalPackages: react-native: Not Found

    opened by camboYY 0
  • Hipaa complaint

    Hipaa complaint

    Our team wants to create a medical app which is Hipaa complaint. As we know that AWS SNS service is Hipaa complaint but FCM (Firebase Cloud Messaging) is not. When creating platform application in AWS SNS, we are required to select the Push notification platform (FCM) which our app is registered with.

    Our app is built in React Native which uses react-native-notifications and we want to implement Cloud Based Push Notifications with Hipaa complaint. By using AWS SNS service with FCM plateform, will our app notifications be secured and adhere to Hipaa?

    opened by hsaeed667 0
  • EXC_BREAKPOINT crash with silent notifications

    EXC_BREAKPOINT crash with silent notifications

    We've been seeing a huge number of these crashes since support for silent notifications was added (back?) in this PR https://github.com/wix/react-native-notifications/pull/587

    From some research it seems like this is a common crash when the callback handler is called multiple times. After some debugging I found that I can repro when the client code takes longer than 25 seconds to complete and call the completion handler.

    In that case this code will execute, calling the completion handler for me https://github.com/wix/react-native-notifications/blob/master/lib/ios/RNNotificationEventHandler.m#L53

    But then sometime later it is called again here https://github.com/wix/react-native-notifications/blob/master/lib/ios/RNNotificationEventHandler.m#L43

    Our current mitigation is to patch that function by first checking if the completion handler has been called. Here's the patch for reference.

    diff --git a/node_modules/react-native-notifications/lib/ios/RNNotificationEventHandler.m b/node_modules/react-native-notifications/lib/ios/RNNotificationEventHandler.m
    index 5c8dd0b..9b8f44a 100644
    --- a/node_modules/react-native-notifications/lib/ios/RNNotificationEventHandler.m
    +++ b/node_modules/react-native-notifications/lib/ios/RNNotificationEventHandler.m
    @@ -39,16 +39,19 @@ - (void)didReceiveBackgroundNotification:(NSDictionary *)userInfo withCompletion
             __block BOOL completionHandlerCalled = NO;
             dispatch_semaphore_t semaphore = dispatch_semaphore_create(0);
             [_store setBackgroundActionCompletionHandler:^(UIBackgroundFetchResult result) {
    -            dispatch_async(dispatch_get_main_queue(), ^{
    -                completionHandler(result);
    -            });
    -            completionHandlerCalled = YES;
    +            if (!completionHandlerCalled) {
    +                completionHandlerCalled = YES;
    +                dispatch_async(dispatch_get_main_queue(), ^{
    +                    completionHandler(result);
    +                });
    +            }
                 dispatch_semaphore_signal(semaphore);
             } withCompletionKey:uuid];
             [RNEventEmitter sendEvent:RNNotificationReceivedBackground body:[RNNotificationParser parseNotificationUserInfo:userInfo withIdentifier:uuid]];
             // Allow 25 seconds for this to process. If not finished call the callback with failed.
             dispatch_semaphore_wait(semaphore, dispatch_time(DISPATCH_TIME_NOW, 25 * NSEC_PER_SEC));
             if (!completionHandlerCalled) {
    +            completionHandlerCalled = YES;
                 dispatch_async(dispatch_get_main_queue(), ^{
                     completionHandler(UIBackgroundFetchResultFailed);
                 });
    

    Obviously, our code should not be taking more than 25 seconds, but until we can figure that out, this patch seems to work.

    Full trace

    OS Version: iOS 15.4.1 (19E258)
    Report Version: 104
    
    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Crashed Thread: 0
    
    Application Specific Information:
    Exception 6, Code 2766350976, Subcode 8
    
    Thread 0 Crashed:
    0   libdispatch.dylib               0x324e83a80         dispatch_group_leave.cold.1
    1   libdispatch.dylib               0x324e4e870         dispatch_group_leave
    2   libdispatch.dylib               0x324e4be64         _dispatch_call_block_and_release
    3   libdispatch.dylib               0x324e4da28         _dispatch_client_callout
    4   libdispatch.dylib               0x324e5bf44         _dispatch_main_queue_drain
    5   libdispatch.dylib               0x324e5bb94         _dispatch_main_queue_callback_4CF
    6   CoreFoundation                  0x3254a22ec         __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
    7   CoreFoundation                  0x32545c1f0         __CFRunLoopRun
    8   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    9   GraphicsServices                0x35d5c1370         GSEventRunModal
    10  UIKitCore                       0x32a245e84         -[UIApplication _run]
    11  UIKitCore                       0x329fc75e8         UIApplicationMain
    12  Driver                          0x2047cb1b8         main (main.m:7)
    13  <unknown>                       0x10546dce4         <redacted>
    
    Thread 0 Crashed:
    0   libdispatch.dylib               0x324e83a80         dispatch_group_leave.cold.1
    1   libdispatch.dylib               0x324e4e870         dispatch_group_leave
    2   libdispatch.dylib               0x324e4be64         _dispatch_call_block_and_release
    3   libdispatch.dylib               0x324e4da28         _dispatch_client_callout
    4   libdispatch.dylib               0x324e5bf44         _dispatch_main_queue_drain
    5   libdispatch.dylib               0x324e5bb94         _dispatch_main_queue_callback_4CF
    6   CoreFoundation                  0x3254a22ec         __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
    7   CoreFoundation                  0x32545c1f0         __CFRunLoopRun
    8   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    9   GraphicsServices                0x35d5c1370         GSEventRunModal
    10  UIKitCore                       0x32a245e84         -[UIApplication _run]
    11  UIKitCore                       0x329fc75e8         UIApplicationMain
    12  Driver                          0x2047cb1b8         main (main.m:7)
    13  <unknown>                       0x10546dce4         <redacted>
    
    Thread 1
    0   libsystem_kernel.dylib          0x394853ab4         __workq_kernreturn
    1   libsystem_pthread.dylib         0x40748b104         _pthread_wqthread
    
    Thread 2 name: com.apple.uikit.eventfetch-thread
    0   libsystem_kernel.dylib          0x3948534e0         mach_msg_trap
    1   libsystem_kernel.dylib          0x394853b20         mach_msg
    2   CoreFoundation                  0x32545781c         __CFRunLoopServiceMachPort
    3   CoreFoundation                  0x32545bca8         __CFRunLoopRun
    4   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    5   Foundation                      0x328444410         -[NSRunLoop(NSRunLoop) runMode:beforeDate:]
    6   Foundation                      0x328485ca8         -[NSRunLoop(NSRunLoop) runUntilDate:]
    7   UIKitCore                       0x32a1bffac         -[UIEventFetcher threadMain]
    8   Foundation                      0x328494558         __NSThread__start__
    9   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 3
    0   libsystem_kernel.dylib          0x394853a6c         __semwait_signal
    1   libsystem_c.dylib               0x33b70d0d8         nanosleep
    2   libsystem_c.dylib               0x33b72137c         sleep
    3   Driver                          0x204ba3f24         monitorCachedData (SentryCrashCachedData.c:139)
    4   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 4 name: SentryCrash Exception Handler (Secondary)
    0   libsystem_kernel.dylib          0x3948534e0         mach_msg_trap
    1   libsystem_kernel.dylib          0x394853b20         mach_msg
    2   Driver                          0x204bb0ae0         handleExceptions (SentryCrashMonitor_MachException.c:266)
    3   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 6
    0   libsystem_kernel.dylib          0x394853ab4         __workq_kernreturn
    1   libsystem_pthread.dylib         0x40748b104         _pthread_wqthread
    
    Thread 7 name: com.facebook.react.JavaScript
    0   JavaScriptCore                  0x33c652264         JSC::JSLock::willReleaseLock
    1   JavaScriptCore                  0x33c652204         JSC::JSLock::willReleaseLock
    2   JavaScriptCore                  0x33c651be8         JSC::JSLockHolder::~JSLockHolder
    3   JavaScriptCore                  0x33bc2e43c         JSValueUnprotect
    4   Driver                          0x204b7b248         facebook::jsc::JSCRuntime::JSCObjectValue::invalidate (JSCRuntime.cpp:580)
    5   Driver                          0x204b821d0         [inlined] facebook::jsi::Pointer::~Pointer (jsi.h:337)
    6   Driver                          0x204b821d0         [inlined] facebook::jsi::Object::~Object (jsi.h:507)
    7   Driver                          0x204b821d0         [inlined] facebook::jsi::Object::~Object (jsi.h:507)
    8   Driver                          0x204b821d0         facebook::jsi::dynamicFromValue (JSIDynamic.cpp:183)
    9   Driver                          0x204b849a4         facebook::react::JSIExecutor::callNativeModules (JSIExecutor.cpp:391)
    10  Driver                          0x204b84b5c         facebook::react::JSIExecutor::invokeCallback (JSIExecutor.cpp:262)
    11  Driver                          0x204b78ed0         [inlined] std::__1::__function::__value_func<T>::operator() (functional:1885)
    12  Driver                          0x204b78ed0         [inlined] std::__1::function<T>::operator() (functional:2560)
    13  Driver                          0x204b78ed0         [inlined] facebook::react::NativeToJsBridge::runOnExecutorQueue::lambda::operator() (NativeToJsBridge.cpp:310)
    14  Driver                          0x204b78ed0         [inlined] std::__1::__invoke<T> (type_traits:3694)
    15  Driver                          0x204b78ed0         [inlined] std::__1::__invoke_void_return_wrapper<T>::__call<T> (__functional_base:348)
    16  Driver                          0x204b78ed0         [inlined] std::__1::__function::__alloc_func<T>::operator() (functional:1558)
    17  Driver                          0x204b78ed0         std::__1::__function::__func<T>::operator() (functional:1732)
    18  Driver                          0x204ac3540         [inlined] std::__1::__function::__value_func<T>::operator() (functional:1885)
    19  Driver                          0x204ac3540         [inlined] std::__1::function<T>::operator() (functional:2560)
    20  Driver                          0x204ac3540         facebook::react::tryAndReturnError (RCTCxxUtils.mm:74)
    21  Driver                          0x204acf640         facebook::react::RCTMessageThread::tryFunc (RCTMessageThread.mm:69)
    22  Driver                          0x204acf3f4         [inlined] std::__1::__function::__value_func<T>::operator() (functional:1885)
    23  Driver                          0x204acf3f4         [inlined] std::__1::function<T>::operator() (functional:2560)
    24  Driver                          0x204acf3f4         facebook::react::RCTMessageThread::runAsync (RCTMessageThread.mm:45)
    25  CoreFoundation                  0x3254c30e0         __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__
    26  CoreFoundation                  0x3254c403c         __CFRunLoopDoBlocks
    27  CoreFoundation                  0x32545bec4         __CFRunLoopRun
    28  CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    29  Driver                          0x204ab85d4         +[RCTCxxBridge runRunLoop] (RCTCxxBridge.mm:308)
    30  Foundation                      0x328494558         __NSThread__start__
    31  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 8
    0   libsystem_kernel.dylib          0x394853ab4         __workq_kernreturn
    1   libsystem_pthread.dylib         0x40748b104         _pthread_wqthread
    
    Thread 9 name: AVAudioSession Notify Thread
    0   libsystem_kernel.dylib          0x3948534e0         mach_msg_trap
    1   libsystem_kernel.dylib          0x394853b20         mach_msg
    2   CoreFoundation                  0x32545781c         __CFRunLoopServiceMachPort
    3   CoreFoundation                  0x32545bca8         __CFRunLoopRun
    4   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    5   AudioSession                    0x33805af00         CADeprecated::GenericRunLoopThread::Entry
    6   AudioSession                    0x3380648ec         CADeprecated::CAPThread::Entry
    7   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 10 name: com.apple.CoreMotion.MotionThread
    0   libsystem_kernel.dylib          0x3948534e0         mach_msg_trap
    1   libsystem_kernel.dylib          0x394853b20         mach_msg
    2   CoreFoundation                  0x32545781c         __CFRunLoopServiceMachPort
    3   CoreFoundation                  0x32545bca8         __CFRunLoopRun
    4   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    5   CoreFoundation                  0x3254f0894         CFRunLoopRun
    6   CoreMotion                      0x33fb33750         CLMotionActivity::isTypeInVehicle
    7   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 11 name: com.apple.NSURLConnectionLoader
    0   libsystem_kernel.dylib          0x3948534e0         mach_msg_trap
    1   libsystem_kernel.dylib          0x394853b20         mach_msg
    2   CoreFoundation                  0x32545781c         __CFRunLoopServiceMachPort
    3   CoreFoundation                  0x32545bca8         __CFRunLoopRun
    4   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    5   CFNetwork                       0x3267034d4         _CFURLStorageSessionDisableCache
    6   Foundation                      0x328494558         __NSThread__start__
    7   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 12 name: com.apple.coreaudio.AQClient
    0   libsystem_kernel.dylib          0x3948534e0         mach_msg_trap
    1   libsystem_kernel.dylib          0x394853b20         mach_msg
    2   CoreFoundation                  0x32545781c         __CFRunLoopServiceMachPort
    3   CoreFoundation                  0x32545bca8         __CFRunLoopRun
    4   CoreFoundation                  0x32546f6b4         CFRunLoopRunSpecific
    5   AudioToolbox                    0x33af86810         CADeprecated::GenericRunLoopThread::Entry
    6   libAudioToolboxUtility.dylib    0x3581b6044         CADeprecated::CAPThread::Entry
    7   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 13 name: fs-default-0
    0   libsystem_kernel.dylib          0x394854640         __psynch_mutexwait
    1   libsystem_pthread.dylib         0x40748c3d8         _pthread_mutex_firstfit_lock_wait
    2   libsystem_pthread.dylib         0x407493528         _pthread_mutex_firstfit_lock_slow
    3   FullStory                       0x1057fff4c         __fs_log_impl
    4   FullStory                       0x105803860         __fs_log_impl
    5   FullStory                       0x105859358         rust_eh_personality
    6   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 14 name: fs-default-1
    0   libsystem_kernel.dylib          0x394854640         __psynch_mutexwait
    1   libsystem_pthread.dylib         0x40748c3d8         _pthread_mutex_firstfit_lock_wait
    2   libsystem_pthread.dylib         0x407493528         _pthread_mutex_firstfit_lock_slow
    3   FullStory                       0x1057fff4c         __fs_log_impl
    4   FullStory                       0x105803860         __fs_log_impl
    5   FullStory                       0x105859358         rust_eh_personality
    6   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 15 name: fs-default-2
    0   libsystem_kernel.dylib          0x394853f64         __psynch_cvwait
    1   libsystem_pthread.dylib         0x407492294         _pthread_cond_wait
    2   FullStory                       0x10585246c         rust_eh_personality
    3   FullStory                       0x105869fd8         rust_eh_personality
    4   FullStory                       0x105800744         __fs_log_impl
    5   FullStory                       0x105803860         __fs_log_impl
    6   FullStory                       0x105859358         rust_eh_personality
    7   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 16 name: fs-default-3
    0   libsystem_kernel.dylib          0x394854640         __psynch_mutexwait
    1   libsystem_pthread.dylib         0x40748c3d8         _pthread_mutex_firstfit_lock_wait
    2   libsystem_pthread.dylib         0x407493528         _pthread_mutex_firstfit_lock_slow
    3   FullStory                       0x1057fff4c         __fs_log_impl
    4   FullStory                       0x105803860         __fs_log_impl
    5   FullStory                       0x105859358         rust_eh_personality
    6   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 17 name: fs-default-4
    0   libsystem_kernel.dylib          0x394854640         __psynch_mutexwait
    1   libsystem_pthread.dylib         0x40748c3d8         _pthread_mutex_firstfit_lock_wait
    2   libsystem_pthread.dylib         0x407493528         _pthread_mutex_firstfit_lock_slow
    3   FullStory                       0x1057fff4c         __fs_log_impl
    4   FullStory                       0x105803860         __fs_log_impl
    5   FullStory                       0x105859358         rust_eh_personality
    6   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 18 name: fs-default-5
    0   libsystem_kernel.dylib          0x394854640         __psynch_mutexwait
    1   libsystem_pthread.dylib         0x40748c3d8         _pthread_mutex_firstfit_lock_wait
    2   libsystem_pthread.dylib         0x407493528         _pthread_mutex_firstfit_lock_slow
    3   FullStory                       0x1057fff4c         __fs_log_impl
    4   FullStory                       0x105803860         __fs_log_impl
    5   FullStory                       0x105859358         rust_eh_personality
    6   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 19 name: futures-timer
    0   libsystem_kernel.dylib          0x394853f64         __psynch_cvwait
    1   libsystem_pthread.dylib         0x407492294         _pthread_cond_wait
    2   FullStory                       0x105857338         rust_eh_personality
    3   FullStory                       0x10585364c         rust_eh_personality
    4   FullStory                       0x105804018         __fs_log_impl
    5   FullStory                       0x1058054ec         __fs_log_impl
    6   FullStory                       0x105859358         rust_eh_personality
    7   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 20
    0   libsystem_kernel.dylib          0x394853ab4         __workq_kernreturn
    1   libsystem_pthread.dylib         0x40748b104         _pthread_wqthread
    
    Thread 21
    0   libsystem_kernel.dylib          0x394853f64         __psynch_cvwait
    1   libsystem_pthread.dylib         0x407492294         _pthread_cond_wait
    2   JavaScriptCore                  0x33cb064d0         scavenger_thread_main
    3   libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 22
    0   libsystem_kernel.dylib          0x394853ab4         __workq_kernreturn
    1   libsystem_pthread.dylib         0x40748b104         _pthread_wqthread
    
    Thread 23
    0   libsystem_kernel.dylib          0x394853ab4         __workq_kernreturn
    1   libsystem_pthread.dylib         0x40748b104         _pthread_wqthread
    
    Thread 24
    0   JavaScriptCore                  0x33bc0dd08         JSC::JSCell::visitChildren
    1   JavaScriptCore                  0x33c662ca4         [inlined] JSC::JSObject::visitChildren
    2   JavaScriptCore                  0x33c662ca4         JSC::JSObject::visitChildren
    3   JavaScriptCore                  0x33c1d8ca4         JSC::SlotVisitor::drain::lambda::operator()
    4   JavaScriptCore                  0x33c1d5d78         JSC::SlotVisitor::drain
    5   JavaScriptCore                  0x33c1d6740         JSC::SlotVisitor::drainFromShared
    6   JavaScriptCore                  0x33c1ae7c8         WTF::SharedTaskFunctor<T>::run
    7   JavaScriptCore                  0x33ca66f98         WTF::ParallelHelperClient::runTask
    8   JavaScriptCore                  0x33ca67cf4         WTF::ParallelHelperPool::Thread::work
    9   JavaScriptCore                  0x33ca2f660         WTF::Detail::CallableWrapper<T>::call
    10  JavaScriptCore                  0x33ca88f64         WTF::Thread::entryPoint
    11  JavaScriptCore                  0x33ca8b270         WTF::wtfThreadEntryPoint
    12  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 25
    0   libsystem_kernel.dylib          0x394853600         syscall_thread_switch
    1   JavaScriptCore                  0x33ca59344         WTF::LockAlgorithm<T>::lockSlow
    2   JavaScriptCore                  0x33c1cb48c         JSC::MarkedBlock::aboutToMarkSlow
    3   JavaScriptCore                  0x33c59f61c         JSC::HashMapBucket<T>::visitChildren
    4   JavaScriptCore                  0x33c1d8cf8         JSC::SlotVisitor::drain::lambda::operator()
    5   JavaScriptCore                  0x33c1d5d78         JSC::SlotVisitor::drain
    6   JavaScriptCore                  0x33c1d6740         JSC::SlotVisitor::drainFromShared
    7   JavaScriptCore                  0x33c1ae7c8         WTF::SharedTaskFunctor<T>::run
    8   JavaScriptCore                  0x33ca66f98         WTF::ParallelHelperClient::runTask
    9   JavaScriptCore                  0x33ca67cf4         WTF::ParallelHelperPool::Thread::work
    10  JavaScriptCore                  0x33ca2f660         WTF::Detail::CallableWrapper<T>::call
    11  JavaScriptCore                  0x33ca88f64         WTF::Thread::entryPoint
    12  JavaScriptCore                  0x33ca8b270         WTF::wtfThreadEntryPoint
    13  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 26
    0   JavaScriptCore                  0x33c1d57fc         JSC::SlotVisitor::markAuxiliary
    1   JavaScriptCore                  0x33c662f68         [inlined] JSC::JSObject::visitChildren
    2   JavaScriptCore                  0x33c662f68         JSC::JSObject::visitChildren
    3   JavaScriptCore                  0x33c1d8ca4         JSC::SlotVisitor::drain::lambda::operator()
    4   JavaScriptCore                  0x33c1d5d78         JSC::SlotVisitor::drain
    5   JavaScriptCore                  0x33c1d6740         JSC::SlotVisitor::drainFromShared
    6   JavaScriptCore                  0x33c1ae7c8         WTF::SharedTaskFunctor<T>::run
    7   JavaScriptCore                  0x33ca66f98         WTF::ParallelHelperClient::runTask
    8   JavaScriptCore                  0x33ca67cf4         WTF::ParallelHelperPool::Thread::work
    9   JavaScriptCore                  0x33ca2f660         WTF::Detail::CallableWrapper<T>::call
    10  JavaScriptCore                  0x33ca88f64         WTF::Thread::entryPoint
    11  JavaScriptCore                  0x33ca8b270         WTF::wtfThreadEntryPoint
    12  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 27
    0   JavaScriptCore                  0x33c1d8cb8         JSC::SlotVisitor::drain::lambda::operator()
    1   JavaScriptCore                  0x33c1d8cb4         JSC::SlotVisitor::drain::lambda::operator()
    2   JavaScriptCore                  0x33c1d5d78         JSC::SlotVisitor::drain
    3   JavaScriptCore                  0x33c1d6740         JSC::SlotVisitor::drainFromShared
    4   JavaScriptCore                  0x33c1ae7c8         WTF::SharedTaskFunctor<T>::run
    5   JavaScriptCore                  0x33ca66f98         WTF::ParallelHelperClient::runTask
    6   JavaScriptCore                  0x33ca67cf4         WTF::ParallelHelperPool::Thread::work
    7   JavaScriptCore                  0x33ca2f660         WTF::Detail::CallableWrapper<T>::call
    8   JavaScriptCore                  0x33ca88f64         WTF::Thread::entryPoint
    9   JavaScriptCore                  0x33ca8b270         WTF::wtfThreadEntryPoint
    10  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 28
    0   libsystem_kernel.dylib          0x394853f64         __psynch_cvwait
    1   libsystem_pthread.dylib         0x407492294         _pthread_cond_wait
    2   JavaScriptCore                  0x33ca686d8         WTF::ParkingLot::parkConditionallyImpl
    3   JavaScriptCore                  0x33c90bccc         WTF::Condition::waitUntilUnchecked<T>
    4   JavaScriptCore                  0x33c1d6598         JSC::SlotVisitor::drainFromShared
    5   JavaScriptCore                  0x33c1ae7c8         WTF::SharedTaskFunctor<T>::run
    6   JavaScriptCore                  0x33ca66f98         WTF::ParallelHelperClient::runTask
    7   JavaScriptCore                  0x33ca67cf4         WTF::ParallelHelperPool::Thread::work
    8   JavaScriptCore                  0x33ca2f660         WTF::Detail::CallableWrapper<T>::call
    9   JavaScriptCore                  0x33ca88f64         WTF::Thread::entryPoint
    10  JavaScriptCore                  0x33ca8b270         WTF::wtfThreadEntryPoint
    11  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    Thread 29
    0   JavaScriptCore                  0x33c1c9f54         JSC::MarkedBlock::Handle::stopAllocating
    1   JavaScriptCore                  0x33c1c4914         [inlined] JSC::LocalAllocator::stopAllocating
    2   JavaScriptCore                  0x33c1c4914         JSC::LocalAllocator::stopAllocating
    3   JavaScriptCore                  0x33c1907c0         JSC::BlockDirectory::stopAllocating
    4   JavaScriptCore                  0x33c1ccb24         JSC::MarkedSpace::stopAllocating
    5   JavaScriptCore                  0x33c1a1548         JSC::Heap::stopThePeriphery
    6   JavaScriptCore                  0x33c19e2b4         JSC::Heap::finishChangingPhase
    7   JavaScriptCore                  0x33c19e004         JSC::Heap::runCurrentPhase
    8   JavaScriptCore                  0x33c1a9850         JSC::Heap::HeapThread::work
    9   JavaScriptCore                  0x33ca2f660         WTF::Detail::CallableWrapper<T>::call
    10  JavaScriptCore                  0x33ca88f64         WTF::Thread::entryPoint
    11  JavaScriptCore                  0x33ca8b270         WTF::wtfThreadEntryPoint
    12  libsystem_pthread.dylib         0x40748b9a8         _pthread_start
    
    
    
    EOF
    
    opened by nicolas6422 6
  • first notification crash app only testflight

    first notification crash app only testflight

    hi everyone, the first notification the device receives crashes ... after the first one it works fine. With crashlytics I only found this:

    Crashed: com.apple.main-thread 0 libdispatch.dylib 0x6c3d0 dispatch_group_leave$VARIANT$armv81.cold.1 + 36 1 libdispatch.dylib 0x33ee0 _dispatch_group_wake + 118 2 Talk 0x37d614 __39-[RNNotificationsStore completeAction:]_block_invoke + 51 (RNNotificationsStore.m:51) 3 libdispatch.dylib 0x63194 _dispatch_call_block_and_release + 24 4 libdispatch.dylib 0x64198 _dispatch_client_callout + 16 5 libdispatch.dylib 0x454a8 _dispatch_main_queue_callback_4CF$VARIANT$armv81 + 908 6 CoreFoundation 0x4d7e8 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 12 7 CoreFoundation 0xb0e8 __CFRunLoopRun + 2528 8 CoreFoundation 0x1dd7c CFRunLoopRunSpecific + 572 9 GraphicsServices 0x19a0 GSEventRunModal + 160 10 UIKitCore 0x4ec05c -[UIApplication _run] + 1080 11 UIKitCore 0x281ce0 UIApplicationMain + 2028 12 Talk 0x4c88 main + 7 (main.m:7) 13 ??? 0x105284190 (Mancante)

    https://imgur.com/SrY6zau

    can you give me support?

    with regard

    opened by Larens94 0
  • Is this protect EOL, not compatible with Android API 31+

    Is this protect EOL, not compatible with Android API 31+

    As of this month, all new Android apps must target API 31

    compileSdkVersion = 31
    targetSdkVersion = 31
    

    As of Nov 2022, All Android Apps must (SEE HERE)

    This change requires the android:exported="true" or android:exported="false" to be defined. If it is not the app can not be installed.

    When you set API 31 you get an ERROR attributed to this library.

    Installation did not succeed.
    The application could not be installed: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED
    
    List of apks:
    [0] '/Users/[USERNAME]/github/[APP]/android/app/build/outputs/apk/release/app-release.apk'
    Installation failed due to: 'Failed to commit install session 1735472622 with command cmd package install-commit 1735472622. Error: INSTALL_PARSE_FAILED_MANIFEST_MALFORMED: Failed parse during installPackageLI: /data/app/vmdl1735472622.tmp/base.apk (at Binary XML file line #148): com.wix.reactnativenotifications.fcm.FcmInstanceIdListenerService: Targeting S+ (version 31 and above) requires that an explicit value for android:exported be defined when intent filters are present'
    Retry
    Failed to launch an application on all devices
    

    I am digging into the code, but not seeing what lines need to change for this library, sorry. I just know if there is not a patch for this in the next 60 days no one can use this for an RN Android App anymore

    opened by russmenum 8
Releases(4.3.1)
Owner
Wix.com
Open-sourcing useful pieces of code
Wix.com
React Native Library for OneSignal Push Notifications Service

React Native OneSignal SDK OneSignal is a free push notification service for mobile apps. This SDK makes it easy to integrate your native React-Native

OneSignal 1.4k Sep 24, 2022
Send or schedule Android system notifications for React Native.

react-native-system-notification Send or schedule Android system notifications for React Native. Table of Contents Installation Usage Creating Notific

null 15 Jul 15, 2022
Free React Native library to display local notifications.

React-Native NotiFREE ⚛ React Native library to display local notifications. A FREE alternative to React Native NotiFEE. Why? Nobody can remove the gr

Douglas Nassif Roma Junior 22 Jun 19, 2022
React Native Android Notification Listener - Listen for status bar notifications from all applications

react-native-android-notification-listener React Native Android Notification Listener is a library that allows you to listen for status bar notificati

Leandro Simões 75 Sep 22, 2022
Show internal notifications for react native application with TypeScript

React Native InApp Notifications Typescript component to show internal notifications for react native application Install yarn add react-native-intern

Viacheslav Volkov 3 Aug 25, 2022
Firebase incoming call notifications for React Native based applications.

Android Call Notifications App (React Native) Banner Notifications FullScreen Notifications Prerequisites for project Create a firebase project from f

Vishnu Ramineni 20 Sep 20, 2022
PushyPush - How to Code Push Notifications for React Native Apps

How to Code Push Notifications for React Native Apps Please step through the fol

Nick 5 Apr 27, 2022
Alarm clock functionality for react native ios and android using react-native-push-notification and react-native-community/async-storage

react-native-simple-alarm Alarm clock functionality for react native ios and android built using react-native-push-notification and react-native-commu

Jordan Daniels 65 Sep 7, 2022
A barcode scanner component for react native - not maintained anymore - use react-native-camera

react-native-barcodescanner - not maintained anymore - use react-native-camera Version 0.4.0 of react-native-camera includes barcode scanning for andr

Idea Creation / E-GUMA 537 Sep 17, 2022
React Native CallKit utilises a brand new iOS 10 framework CallKit to make the life easier for VoIP developers using React Native.

React Native CallKit utilises a brand new iOS 10 framework CallKit to make the life easier for VoIP developers using React Native.

React Native WebRTC 121 Jan 6, 2022
React-native-wordle - A simple re-implementation of wordle using react native

react native wordle A simple re-implementation of wordle. guess the randomly cho

Ananthu P Kanive 15 Sep 10, 2022
React-native-esbuild: The fastest bundler for React Native

Fast bundler and dev server for react-native using esbuild

Joel Arvidsson 449 Sep 26, 2022
React Native Firebase Authentication Starter, manage user authentication in React Native app with firebase

Sign up and sign in screens for mobile using React Native. This is an example of how to use Firebase Authentication in React Native application, how to let users create an account or log in to an existing account.

Maor 14 Sep 8, 2022
Native filesystem access for react-native

react-native-fs Native filesystem access for react-native IMPORTANT For RN < 0.57 and/or Gradle < 3 you MUST install react-native-fs at version @2.11.

Hagen Hübel 4.5k Sep 26, 2022
react-native native module for In App Purchase.

Announcement React Native IAP hook is out. You can see medium post on how to use it. The react-native-iap module hasn't been maintained well recently.

dooboolab 2.2k Sep 23, 2022
React Native authentication with the native Touch ID popup.

React Native Touch ID React Native Touch ID is a React Native library for authenticating users with biometric authentication methods like Face ID and

Naoufal Kadhom 1.4k Sep 27, 2022
Native sensors access for react-native

react-native-sensor-manager Wrapper for react-native. Accelerometer, Gyroscope, Magnetometer, Orientation, Step Counter, Thermometer, LightSensor, and

Kevin Primicerio 229 Aug 22, 2022
React Native: Native Bottom Sheet - Text View

ReactNative: Native Bottom Sheet Text View (Android/iOS): Deprecated Due to time constraint, this library is deprecated and not maintained anymore, Y

Pranav Raj Singh Chauhan 22 Jul 4, 2021
React Native Unofficial SDK for integrating MercadoPago PX Native UIs.

React Native Unofficial SDK for integrating MercadoPago PX Native UIs. Getting Started To integrate this SDK you can check out our docs. Add your App

BlackBox Vision 90 Sep 10, 2022