Unable to Lock Target Device. Make Sure You Do Not Have Open Files on This Device and Try Again.
Notifications Not Shown - Mobile Push
Common reasons why Mobile Push notifications are not showing on your device.
"Delivered" notifications in OneSignal means we have successfully sent the notification to the push servers (FCM/APNS/WNS etc..). These push servers then distribute the notifications to your subscribers. The "Confirmed" stat means our SDK received the notification which should have been shown on the device. Run across Confirmed Deliveries for more details.
The post-obit are reasons why notifications may testify as "Delivered" on the OneSignal dashboard or API, only are not visible on your device.
Devices must exist online to receive push button notifications. If your device is turned off, in airplane manner, has unstable or no internet connectedness, the button will not show until a proper connection is made. You can set the timeframe Google and Apple tree Servers will wait for a connectedness with the Time To Alive (TTL) Parameter (the default is iii days).
Cheque the network / WiFi y'all're connected as it may have closed your connection to Apple or Google servers'. Attempt disabling and re-enabling your cyberspace connection. Likewise effort without wifi using cellular data.
If you lot are restricting traffic to or from the Internet, you need to configure information technology to let connectivity with FCM which requires open up ports to: 5228, 5229, and 5230. More details: https://firebase.google.com/docs/cloud-messaging/concept-options
APNS devices must connect to: TCP port 5223 & TCP port 443 or 2197. More than details: https://back up.apple.com/en-united states/HT203609
If you check the logs from the app, yous may also see:
ERROR: Encountered error during button registration with OneSignal: Error Domain=OneSignalError Lawmaking=0 "(null)" UserInfo={error=Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={NSUnderlyingError=0x2834051a0 {Mistake Domain=kCFErrorDomainCFNetwork Code=-1004 "(cipher)" UserInfo={_kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, NSErrorFailingURLStringKey=https://api.onesignal.com/players, NSErrorFailingURLKey=https://api.onesignal.com/players, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=61, NSLocalizedDescription=Could non connect to the server.}} -
Bank check the segment you sent the push to and make sure it is setup correctly. This is under Segments. Sometimes an incorrect filter is added to the segment removing certain devices.
-
Check the Actor ID record in the Audience > All Users section of the dashboard. Under the "Segments" column, you volition see if that user is in the segment targeted for button.
Android,iOS: In your Device Settings > Notifications > Your App, you can turn on and off push button notifications.
Make sure push permissions are enabled for your device:
Android Settings App > Notifications > Your App you lot should see "Show notifications" enable and all categories underneath enabled. If you have a category disabled, you will not become notifications from that category.
In this example, the "Abandoned Cart - Urgent" Category is turned off. If I set this category in the notification, the device will non get this notification.
If no category is ready, OneSignal uses a default "Miscellaneous" category. Make sure that is enabled if non setting categories. See Android Notification Categories for more details.
Go along the app running, but put it in the groundwork/out of focus when testing.
If your app is open while sending, you may be hiding the notification using the Foreground Notification Received Event if on our updated Major release SDK or In-Focus Displaying is set up to None or 0 if on an older version of OneSignal SDK.
Some devices have a specific bombardment optimization that will stop or decrease rate of notifications showing.
Android: In Settings, search for:
- Power Saving Mode or Energy Saving - If "Power Saving Style" and/or "Limit apps and Habitation Screen" is enabled, this will limit all groundwork action (push button notifications) from being received.
- Adaptive ability saving mode - If enabled, device will automatically turn on/off "Power Saving Way" based on your usage patterns.
- or Battery Optimization or Background usage limits - Battery optimized apps will have background functions (like push notifications) restricted. Make sure your app is Not Optimized.
iOS: If the device has Depression Power Mode enabled and has low power, it will reduce the charge per unit at which notifications can be received. Cheque if enabled in Settings > Battery > Depression Power Manner.
If Do Non Disturb is enabled, this prevents the notifications from "popping up" on the screen but nonetheless shows in the "Notification Center".
iOS: Disable inside in Settings > Do Non Disturb.
Android: Disable within in Settings > Notifications > Do Non Disturb. Or search for "Exercise non Disturb" in Settings and disable.
When an app is in a Force Stopped / Force Killed state well-nigh events including FCM messages for push notifications will not exist received. An app can be placed in this land in the following ways.
- From Settings > Apps, "Force Terminate" is pressed.
- Long pressing the back button on some devices.
- Using a third party job killer like Greenify.
- Swiping abroad your app while remote debugging information technology. (Non the aforementioned as viewing the logcat but launching your app every bit a remote debug process.)
- Automatically on some devices due to custom Android tweaks washed by manufactures. This is a known event affecting all push button providers (not just OneSignal). We have written a weblog mail about this and provide more details and give-and-take in this Github Issue.
Based on your device manufacturer, yous can follow these steps to enable push for your device. For your app users, if yous want to help brainwash them on this effect, y'all can send these specific devices In-App Messaging to enable proper settings.
| Manufacturer | Description |
|---|---|
| Asus | Check your app in the Auto-beginning Managing director. |
| Huawei | Step i: Settings --> Avant-garde Settings or Power Saving --> Battery Director or Protected Apps --> select the app to protect it. Pace 2: Settings --> Apps or Notification Manager --> Advanced or Notify for your app --> Ignore Bombardment Optimizations, select the app and ignore it. Stride three: Settings --> Notification Console & Status Bar --> Notification Center, select the app, then actuate "Permit Notifications" and also "Priority Display". Total Instructions Pre-EMUI 5.0 / Android 7 - Go to Settings > "Protected apps", check your app. Full Instructions |
| LeEco/LeTV | Footstep i: Settings --> Permissions --> Manage Auto Launch --> select the app to protect it. Step 2: Settings --> Bombardment --> Power Saving Management --> App Protection, select the app and ignore it. |
| Lenovo | Settings --> Power Manager --> Groundwork App Direction, select the app and ignore it. |
| OnePlus | Settings > Battery > Battery optimization > Meridian right three-dot menu > Advanced optimization, turn off. Settings > Battery > Battery optimization > Your App > select Don't optimize. Settings > Alert slider to make sure information technology'due south set up the manner you desire. Make sure that Gaming manner is off or become to Settings > Avant-garde > Gaming mode and toggle Block notifications Look in Settings > Apps and check the Notifications settings for any trouble apps. |
| Oppo | Settings --> "Security settings" --> "Data saving" and enable your app. |
| Samsung | 1 - Turn off Power Saving mode. This could be preventing notifications from displaying. |
| Sony | Tap on the battery icon. Go to Power Direction --> STAMINA mode --> Apps active in standby --> Add your app. |
| Xiaomi/ | More than details in Android Central Mail. Settings > Installed Apps > Your App > Battery Saver > change selection from "Battery Saver" to "No restrictions". Provide authorization to your app to run at startup by activating the AutoStart option in Settings > Installed Apps > Your App Settings > App Notifications > your app > toggle on "Priority" Settings > Notifications & status bar > Plow on "Show Notification Icons" (if you lot desire to meet icons) > App notifications > Your App > Show notifications Settings --> Developer Options. Disable "retentivity optimization". To enabled Developer Options get to Settings --> Nearly. Tap on MIUI 8 times. Full Instructions |
| MIUI x | Settings > Bombardment & performance > Choose apps > Select the app that is not showing notifications > Select No restrictions Settings > Permissions > Autostart > Toggle slider next to the apps that are not getting button |
More data on problematic devices can be institute in our blog post: Notifications are highly reliable, except when device manufacturers interfere
i. Run the following to cheque the current state of your app.
Supervene upon "com.company.appname" with your parcel name.
adb beat dumpsys packet com.visitor.appname | grep stopped If you come across stopped=faux if everything is fine, otherwise you will see stopped=true then your app was force killed in some way.
2. Some other style is to ship a few notifications and cheque for the following GCM logcat entry.
Due west/GCM-DMM: broadcast intent callback: result=CANCELLED forIntent { deed=com.google.android.c2dm.intent.RECEIVE pkg=com.onesignal.example (has extras) } If you seen this cancelled intent above then your app could non be started to procedure the notification.
Some device manufactures will white list apps from going into the force closed country. Instance such as Gmail and Whatsapp.
FCM provides a Balance API to query the terminal time a device has been connected to FCM. See the following Google documentation on how to get this.
https://developers.google.com/instance-id/reference/server#get_information_about_app_instances
The most common reason is an outdated version of the OneSignal SDK in the app. Make sure you updated to the latest version of the OneSignal SDK in your app. You should have minimum version 2.10.1.
If you are using Xcode eleven, make sure you are using the latest version of the OneSignal SDK (minimum version 2.x.1). You lot tin open your All Users page and check the SDK VERSION cavalcade to see what version you are on. Xcode eleven made a breaking change that affects push token registration. More than details here: https://onesignal.com/weblog/ios-thirteen-introduces-4-breaking-changes-to-notifications/
Updated 27 days ago
What'southward Side by side
Source: https://documentation.onesignal.com/docs/notifications-show-successful-but-are-not-being-shown
0 Response to "Unable to Lock Target Device. Make Sure You Do Not Have Open Files on This Device and Try Again."
Postar um comentário