I follow all the steps of documentation but nothing works
1 - Create a free account on OneSignal
2 - Use onesignal tool to generate the certificate and upload the .p12 file
3 - Initialize react-native-onesignal SDK in the code
The device asks for permission to push notifications but does not subscribe on the OneSignal Dashboard
There might be several reasons,
iPhone Simulator is unable to receive push notifications so better use a physical device.
Sometimes device id is not detected so it does not subscribe. Check this https://github.com/geektimecoil/react-native-onesignal/issues/200
in your case, it is hard to explain without source code.
Related
Did all initial setups, upload Auth key in firebase console.enter image description here
First of all mention your error if there is no error then run the app and check in xCode debugger you will definitely find the error regarding the push notifications.
But here is the checklist you have double check either you have configured or not
Install react-native-push-notification-ios
configure push notifications in ios files AppDalegate.m & AppDalegate.h
Generate the APNS from the apple developer account and upload in firebase console.
Add the capabilities in xcode Push Notifications & Remote messaging, make sure to check remote fetch
Add FirebaseAppDelegateProxyEnabled type "Boolean" value "NO" in
your info.plist:
Add permissions in Podfile
When attempting to implement Firebase Cloud Messaging into my application, I am receiving the following error at runtime:
I am receiving an FCM token, so it appears to be establishing a connection with firebase. I have read many suggestions on what the problem could be, many seem to indicate that there is a problem with my provisioning profile not allowing push notifications. I have checked these settings under "Signing & Capabilities" and it appears that the profile allows for push notifications, and has the aps-environment value in the entitlements section:
Is there something else I'm missing?
Here is my development environment:
macOS 10.15 (Catalina)
Xcode 11.5
iPad Air 2 (test deployment device)
I finally found the answer. Although my provisioning profile states that I have the aps-environment entitlement, and that I have Push Notification capability included, I STILL had to enable push notifications manually in the project. Additionally, the Background Modes (Remote notifications) capability needed to be added as well. These menus have changed in recent versions of xcode (for instance, the capabilities menu is now called signing and capabilities, and the add capability button is nestled up above all the settings).
In Xcode 11.5, follow these steps:
Click on your workspace name
Select your project in the target list
Select Signing & Capabilities
Click the +Capability button
Add Push Notifications and Background Modes (Remote notifications) from the list.
We're trying to build an app that can track the location of the device on-demand. So admins could send a ping signal and get back the current location of the device. Sort of like (find my phone). The functionality should work even if the app is in the background, when the device is locked, and even be available after a device restart without having to open the app first.
We're building the app using React Native and we were looking at some options for background services and push notifications but none seem to satisfy our needs. Any ideas?
You might be interested with this paid solution: https://www.transistorsoft.com/shop/products/react-native-background-geolocation
When I send multiple notifications to Apple or Android devices through MFP, Apple devices will display all notifications in the notifications center on the other hand Android will only display one last notification. We are using Unicast Notification to send messages to user devices using this REST API.
Initially my issue got fixed when I implemented solution given in this thread.
But after upgrading to MFP 7.1.0.00.20151227-1725 I started facing the issue again.
It it a known limitation that the attribute gets removed from the file upon re-build, since a re-build re-generates the file...
You need to add it back after a re-build. It is scheduled to be enhanced in the future so this won't be needed.
For now you can use for example an Ant task to replace the wlclient.properties file post-build with a version that contains again the attribute.
I'm new to iBeacon's and am trying to understand one simple thing.
Can I use iBeacon to display a notification on a user's iphone without a custom app being installed?
For example, I'd like to build an app that sends out iBeacon messages to people that have an iPhone. When they get near an iPad running my app, it notifies them that they're near my "event", which of course is taking place at the location of my iPad.
Is this possible without the user having already installed another app that I've made to receive notifications of my event?
Note that I'm open to any other tech or ideas that would make this work. I know that Apple does this with their Apple Stores, but I'm guessing they can do this because they already have an app installed on the users device - probably the "AppStore" app.
You typically need an app for any iOS notifications on seeing an iBeacon. That is what Apple does for their stores.
The only exception is if you use Passbook to set up a notification trigger. But you still need the user to install your Passbook entry.