In angular app, a screen share publisher is created. Screen sharing is stopped by browser's stop sharing button, then publisher emits stream destroyed event and publisher is removed from DOM.
But when a subscriber of screen share publisher is created.And browser's stop sharing button is clicked no event is emitted, screen publisher is blacked out and publisher is not removed from DOM.
I tried to capture destroy and stop event of subscriber of screen share publisher but still no destroy event for subscriber. Also I tweaked with browser's APIs but no luck.
Any advice or idea what's going wrong?
Related
Can that be possible? I have a web app and a mobile app as well. The user goes to website and there is a button "Download App for Mobile". When the user clicks on the button, if the app is already installed, the app should be opened otherwise the user must be redirected to the respective store with the link to download the app from store. Any help in the form of Articles, Videos or suggestions would be highly appreciated.
To do this you would have to use sockets and make a background service on your mobile app that listens to an event. When you click on the button an event should be fired from the browser which when listened by the background service, brings the app to foreground. And it will require your web app and react-native to have a socket connection. If no connection is established then you can redirect the respective store. To create socket connection you would need to use a server for communication between mobile app and web app.
read about
getInstalledRelatedApps()
see here for more information
https://web.dev/get-installed-related-apps/
chromeStatusNewFeature
I'm finding it hard to get Branch.io deeplinking to work with Intercom.
The Branch link works well when opened via native Messages app - opens the app directly when tapped.
But if we send this link through an Intercom message, and then tap on it on the phone, the result is not as expected:
On iOS
Open Intercom messages view.
Tap on the Branch link (sent from Intercom console).
Browser opens with an alert asking to open the native app ('Open this page in "MyApp"?').
Press "Open".
App detects the Branch parameters on the link and redirects to the correct page.
Expected Behavior
App should detect the link directly without being handed over by browser.
On Android
Open Intercom messages view.
Tap on the Branch link (sent from Intercom console).
List of suggested apps pops up - including "MyApp".
Tap on "MyApp".
App detects the Branch link ONLY, but without the parameters - which then will not redirect to any page.
Now send the app to the background (eg: Tap on home button), and then open "MyApp" again.
Branch will now detect the link with the parameters and redirect to the correct page (this sometimes happens in iOS as well).
Expected Behavior
Branch should detect the link with parameters directly, without the need to send the app to background and reopen.
Does anyone have an idea what I have missed out on? or a workaround?
I was thinking to setup Universal Links by uploading the Association File.. 🤷♂️
Btw, Branch.io configurations are all done and works perfectly with other social media apps.
react-native: 0.61.5
react-native-branch: 5.0.0-beta.1
react-native-intercom: 16.0.0
When my service worker invokes a secured API that returns content, I do receive an error message, such that The Site has been updated in background. Can anyone please help me out ?
Based from this link, the message This site has been updated in the background is a forced message from the Chrome browser when the SDK cannot fetch the notification contents to retrieve. Notification contents are not sent to our background worker; instead we receive a signal to display a notification and then we fetch the notification contents from our server.
This behavior is most likely triggered by the user having multiple notifications pings, but only one message to receive.
You may also check this related SO post: Chrome Push Notification: This site has been updated in the background
Generally as soon as you receive a push message from GCM (Google Cloud Messaging) you have to show a push notification in the browser. This is mentioned on the 3rd point in here:
https://developers.google.com/web/updates/2015/03/push-notificatons-on-the-open-web#what-are-the-limitations-of-push-messaging-in-chrome-42
So it might happen that somehow you are skipping the push notification though you got a push message from GCM and you are getting a push notification with some default message like "This site has been updated in the background".
Hope this helps!
We have push notifications working successfully. Backend event source is a Worklight adapter written in JS using the 'WL.Server.createDefaultNotification' and 'WL.Server.notifyAllDevices' API calls to send unicast notifications. In the front-end, the app is registered for push notification call back using 'WL.Client.Push.registerEventSourceCallback' JS API.
These particular scenarios are not working:
App is open in the background after login. Notification message is received, but user does not tap notification banner message - and instead just opens app by touching app icon. Notification callback method is not called - and subsequently payload from the backend is not available for the method.
App is open in the background after login. Notification message is received which only has iOS badge change and payload but no notification message for the banner or lock screen. In which case user has nothing to tap on. When user opens the app again - notification callback is not called.
Knowledgecenter documentation seems to indicate that the callback method should be getting invoked even if the app is running in the background. This is with Worklight 6.2.0.1.
Push is indeed supposed to work as you've describe. This is a bug.
This is no manual workaround for this.
If you are an IBM customer or Business Partner you will need to open a PMR (support ticket).
I've recently implemented FB Javascript SDK for a mobile web app and am playing with their event subscription code:
FB.Event.subscribe('auth.statusChange', handleStatusChange);
I notice that handleStatusChange is called when I log in into facebook through my app. However, if I open another browser tab, go to facebook.com and log out the function isn't called.
I was expecting it to be called. Am I wrong? I thought the point of this function was to monitor changes that were not necessarily within the purview of my app.
Thanks!
auth.authResponseChange - fired when the authResponse changes
https://developers.facebook.com/docs/reference/javascript/FB.getAuthResponse/
This would be when a users add or removes a permission, in our flows we are supposed to provide away for a users to remove each permission and authResponse allows us to monitor.