I think I know the answer to this question from my experiments, but I haven't been able to find a definitive answer when doing research.
Is is possible to send notifications to a PWA when it is opened in Chrome on mobile, but isn't installed?
Once it is installed I can receive notifications, but I can't before.
I'm having a hard time getting remote debugging working for my mobile so it's difficult to tell if the push event is even firing.
The docs, don't specify the need to install the pwa to be able to use the notification feature. However what I suspect is happening in your case is that Chrome is not giving priority to notify to the notification that you are sending without installing. What I mean is that you might receive your notification on the regular wakeup cycle of Chrome, and not as a background task. (But this is just a speculation)
Another common scenario that happens a lot, trust me :-), is that you forgot to give permission to send notifications in the first place.
Regarding remote debugging, refer the docs, to get it setup on Android. As a lot of the online tutorials are a bit out of date.
Note: I found an article online that shows a notification received without installing on Android, here is its link, it might not be very helpful for your case but check it out you might figure something out.
Yes they can.
The problem was that I had notifications enabled for my site, but disabled for Chrome itself.
Related
My issue is that I am testing with an iPhone and an iPad, and my iPad is receiving just fine, but my iPhone receives when the app is first installed, and then stops working. I've also seen the reverse, where the ipad stops and the phone works great. Running ios 15.3.1, but not unique to this release. I am using Microsoft Notification Hub to aggregate and push to devices. registrations are properly in the hub and verified through test send. Also using a separate tool to test directly sending to my ios devices using the token I receive from Apple. This tests out just fine as well. I believe that the call to DidReceivedRemoteNotification isn't being called all of the time, but there is no rhyme or reason. The behavior changes in test, when I have the debugger attached and I point my app to the test hub. So it's very difficult to reproduce in a way that I can understand what's happening. Looking for some suggestions on how to diagnose, or why might the method not be called sometimes, on a given device. Thanks in advance.
Ok, so I have things working correctly now. For the benefit of those who are looking at the same issues, and especially those who are inexperienced at ios apps, here goes...
I was using DidReeiveRemoteNotification for both the foreground and background pushes. This seemed to work most of the time, especially in foreground, but not always. In background, it was touch and go. I captured a sysdiagnose log and looked at the push as it was logged from the device, and saw that it was blocked by the OS, because it had too many apps running in the background. It is not guaranteed to wake up your app, and I was relying on it.
So instead, I implemented WillPresentNotification in my appdelegate to deal with foreground pushes, and it works very reliably. For background, all I needed to do was update the app badge and send an alert to the device, and that can be done without waking up the application - the os does it for you. Then, when the app gets woken back up to the foreground, I do a final update to my data so it matches with the badge. Hope this is of use to others.
My boss has charged me with the task of finding how to integrate WeChat into our photobooth's "Total Share" section.
Our photobooths work under windows and their software is a mix of Java and a PHP web API installed locally, that then connects to a web service.
The intention is to give the user the option to, when their picture is done, get a copy of it via WeChat (I guess that by introducing it's phone number)
Through my searches I've found a WeChat JS-SDK, but that seems to connect sites you are watching on your phone with your actual WeChat app so it doesn't work in my case.
The other source I have found is the Official Account Admin Platform, but I'm not really sure if this would allow me to do what I need. As far as I've seen, the Official Account can send messages in response to a trigger (that would work for me, send a message when the user clicks on the button), but it also seems to need that they "subscribe" (in a way) to the Official Account, and secondly I'm not sure how can this be automatized.
Especial mention:
I'm a junior developer, so API integration is a bridge I haven't crossed yet, and as such I'm utterly lost.
Is it possible to get the functionality I require? If so, what are the steps to do it?
You don't need to make a fully fleshed tutorial to write an answer, just knowing in what direction should I go, and maybe some possible caveats that more experienced developers may be able to foresee, would be great.
Thanks.
Forgive me if you think its an obvious one, but I didn't find any relevant(non-obsolete) material on the same.
So, I have a chrome extension out there (Zoho Mail Tracker) which as the name suggests is an email tracker for the Zoho mail client.
It relies on the GCM notifications for giving information to the user. My question is what should I use as GCM won't work on Firefox.
I tried reading a lot and seems like most of the stuff is either obsolete or deprecated. Should I resort to long polling(seems really a bad idea), or websockets?
Or should I simply wait until its properly implemented in Firefox?
Can anyone please so let me know precisely that how can I accomplish the task in which I need to show Push Notification to user when App is Quit/closed?
Currently, I am able to get the push notification done when App is running in background or opened. But App couldn't receive Notification when it is quit/closed by the user.
Right now, it's a really critical task on my shoulders. It's pretty clear do tell me in case if you guys need me to brief in details.
I am having a very hard time to believe that your scenario is Really the following:
When the app is either: open and in the foreground, or open and in the background, you are able to receive a notification to the device, and have its contents displayed in the app, but
When the app is quit (as in not running), the notification does not arrive to the device at all.
I have tested several devices and several push-enabled applications (event source, tag-based). The notification does arrive to the device, after the user subscribed to either a tag or by logging-in (in the case of event source-based), after which sending a notification always arrived to the device.
I don't understand this sentence:
my app logouts with the user
You need to be CLEAR in your explanation. Is there a logout button that the user clicks? If yes, are you also for some reason perform an unsubscribe API invocation? If no, edit the question and provide DETAILED, step-by-step reproduction instructions, AS WELL as provide your application, or any code that you use so that it could be inspected for possible issues.
Does anyone know of an AIR Native Extension (ANE) that allows you to access the device's notification sound(s)? OR, a method to query if the device is in "silent" or "vibrate" mode?
I've set up Push Notifications, but no sound plays on my (Android) device.
I know I can play my own sounds, but I want to use the native notification sound (the same as an SMS or email alert sound) and I don't want the sound to play if it shouldn't (viz. silent mode / vibrate mode).
I've been looking for hours and there's a "Vibrate ANE," and others looking for the same type of capability, but I haven't found anything usable for native sound notifications.
I believe that iOS automatically will play a notification sound when it receives a push notification (I think), but Android just flashes the "shade title" & shows the app's icon for the notification.
Maybe someone else has stumbled across a solution??? =)
Many Thanks!
Todd =D
I think you might have to be careful attempt to access the built in sounds on iOS.
We definitely could write an extension that played any of the system sounds. However I believe these sounds are copyrighted, and my understanding of the Apple ToS is that your application may get rejected from the AppStore if you use them directly.
This is why things like a notifications extension only use a "default notification" value to access system sounds that are set by the user. These sounds are played on certain system events.
The sounds are all accessed via undocumented IDs: http://iphonedevwiki.net/index.php/AudioServices
So yeah we’ve been very cautious of writing anything that could put developers in trouble with the AppStore. You have enough problems getting apps through as is. But if you read otherwise let me know.