I deployed a basic WebRTC test app to Heroku on a paid hobby dyno. It functions fine on Chrome running on Manjaro, but won't connect via https on iOS Safari. Uses websockets for signalling if that matters. Any help would be appreciated!
Test app:
https://webrtc-tstapp.herokuapp.com/
Repo:
https://github.com/TuxFan77/webrtc-test-app
What is the browser when did you test?
Currently, Chrome on iOS doesn't support WebRTC API perfectly yet.
Try Safari.
Related
I have set up and successfully deployed a spring-boot application storing data in a aws-rds, as well as a angular 7 client-side application that uses Okta for authentication. All deployed on Heroku. On my computer, everything works fine, but on any mobile devices (iphone, ipad, android phone), the application is not reaching (or even seeming to attempt) to reach the server application. I don't even know where to start debugging. Does anyone have any suggestions?
I am trying to use the BOT simulator to connect and test my Bot SDK application that I've deployed to Azure App Service.
When I run the bot web api propject locally, I can test it with the simulator no problem.
However, when I try to test the same application that is hosted remoely, the simulator fails. After investigation, I found that the simulator needs ngork to be able to connect to bot service that are hosted remotely
https://github.com/Microsoft/BotFramework-Emulator/wiki/Getting-Started#connecting-to-bots-hosted-remotely
If your bot is hosted remotely, ensure that ngrok tunneling software
is installed and configured. The Bot Framework Emulator is tightly
integrated with ngrok and can launch it for you when needed.
The matter has confused others and they asked questions here:
https://github.com/Microsoft/BotFramework-Emulator/wiki/Getting-Started#connect-to-a-bot-hosted-remotely
Why the simultor has dependance on ngork to connect to remotely hosted bots? It seem conter intuitive since the dns name is publicly available
When you're running the emulator locally and debugging in the cloud, you need to be set up for traffic to flow bi-directionally. By default without NGROK you can post to your bot, but for it to POST back to your client, it needs an IP address to post to. NGROK provides that without you having to set up local ports, etc.
I have installed and running this script on server: https://github.com/gorilla/websocket
Everything was configured and running ok when I was using ios native application but now I have to switch to phonegap and I cannot find example which is working.
I cannot move to another script on my server because it would be to much work.
Is there any way that I can connect to my server from phonegap ionic?
My application is for ios and android, it's game which needs real time connection just like chat application.
Thank you
Google Cloud Messaging (GCM) is a service that enables developers to send data from servers to both Android applications or Chrome apps and extensions.
I am developing a chrome and a firefox extension/add-on. I am using the Web Extension APIs for Firefox extension.
Now, Web Extension APIs don't support chrome.gcm.* APIs yet. Essentially, a firefox extension cannot talk to GCM.
Is there something else like GCM to which a firefox extension can talk to? Something provided by the Firefox just like GCM provided by Google for its browser Chrome? If not, can someone please explain how to achieve this in a Firefox Extension?
Update:
Even for web apps, firefox doesn't use something similar to GCM. They use service workers. Can Firefox Browser Extensions interact with service workers?
Firefox extensions currently can’t use service workers directly (according to an implementor who worked on service-workers support in Firefox).
Is there something else like GCM to which a firefox extension can talk to? Something provided by the Firefox just like GCM provided by Google for its browser Chrome?
Yes, there’s a Firefox equivalent of GCM. Firefox users receive push notifications from a server given by the dom.push.serverURL user preference. If you check dom.push.serverURL in about:config, you’ll see wss://push.services.mozilla.com/, which is the Mozilla Push Service—essentially, Mozilla’s equivalent of GCM.
That runs an AutoPush (Python-based open-source Push Server software project) backend, and the client part is (as the question notes) exposed to frontend code by a service worker.
So while there may be an alternative way Firefox extensions can connect with Mozilla Push Service, the only publicly-documented way is through the standard Web Push API that relies on service workers, which are not available yet for use in Firefox extensions.
I enabled WebSockets support on my Heroku application but last week Heroku updated their platform's routing architecture.
Now I get incomplete chunks in my browser. You can try my app:
http://dartlangfr-risk.herokuapp.com
Here my server code:
https://github.com/ggirou/risk/blob/master/bin/main.dart#L16-L40
Does anyone have a clue?
Thanks