i'm using firebase for my react PWA push notification , I've got everything setup for web app firebase push notification. when I try requesting a notification to desktop it works perfectly but on android devices when I send notification, event hough Postman gives success and message ID and etc but nothing shows on the screen neither in use, nor in background.
Not saying this is the answer in your case but, I had the same problem (notifications worked on desktop and IOS devices but not on Android). My problem was that I had notifications turned off. On your Android phone or tablet, open the Chrome app and try this.
To the right of the address bar, tap More. Settings. List item
Tap SiteSettings. Notifications.
At the top, turn the setting on or off.
Related
I'm implementing Pusher-Beams with next.js using authenticated users flow exactly as described in beams docs, and I got in the browser console client is subscribed and registered successfully.
However at pusher-beams debug-console website page I have these messages when I click on push notification button and nothing shown in my application,
I don't know what exactly I'm doing wrong here?!! and why I keep getting device de-registered message?
Note: I've tried with Chrome, Firefox and Brave but it is not working.
I implemented a local notification test per this example https://www.codenameone.com/blog/local-notifications.html
I have the following two questions:
1) can I test local notifications from CN1 simulator. In the link above, I see a local notification test screenshot using the iPhone 6 simulator. Is there a way to force the app to run in background form the simulator in CN1?
2) If a local notification is sent when the app is running in foreground, I understand that the notification will not fire. Is the message lost in this case or is it queued somewhere?
Currently you can only test this on the device, it will work in the native simulator for iOS as you saw in the screeshot. You can run on the native iOS simulator using a Mac and include source.
The message would be lost if you fire in the foreground on iOS as it's the assumption that this is something you can notify within your app more effectively. You can determine if your app is in the foreground using the Display.isMinimized() method. In the foreground case you can use a tool like ToastBar to show a notification.
On iOS versions before iOS 11:
I connect to a wifi network, the captive portal splash page is presented, a presented button links to an app on the app store https://itunes.apple.com/etcetc, the button is pressed and the app store is opened iOS.
On iOS 11:
The app store is not opened into the foreground. The user has to press the home button to get the app store.
How do I open the app store in the foreground when pressing the app store link?
This problem only happens in iOS 11.
Thanks
We met the same problem, what we can do is filing a bug report to apple.
Please refer to the discussion here: https://forums.developer.apple.com/thread/75498#221482
I'm building a web app with Stripe checkout. On desktop it loads a nice modal when you go to pay, but on mobile it brings the users off to a Stripe page, and then back. I want it to look like the user is never leaving our site.
Is there a way to force the modal to be loaded on mobile? I'm building the web app in ionic at the same time, so if I want to turn it in to an app I can. Ionic uses a WebView on the phone and that loads the modal fine, so there must be some setting that is allowing it?
Anyone have any ideas? Thanks.
edit If I 'request desktop site' on my mobile it loads the modal fine
As Stripe makes these determinations based on the User-Agent you could try changing the User-Agent of your webview to match that of a desktop browser, (I did a similar thing except I needed to force mobile behavior in the desktop).
It should be stated, that this is definitely not recommended by Stripe nor supported and could break at any time. They'd recommend you just build a custom form using Stripe.js
How i can set User Agent in Cordova App has how to set the User-Agent in iOS and Android.
I've been using the WebAuthenticationBroker to connect to external APIs (Onedrive and Google drive); however after porting my app to UWP. The webView that is displayed on tablet mode shows up without a back or a cancel button. (The same webView on phones and in desktop mode appear fine) The hardware back button doesn't seem to work either and am stuck in limbo!
WebAuthenticationResult webAuthenticationResult = await WebAuthenticationBroker.AuthenticateAsync(WebAuthenticationOptions.None, new Uri(url), new Uri(redirectUrl));
What could I be doing wrong?