Socket io android background github

Using socket.io in a background task #146

Comments

guyschlider commented Aug 20, 2015

Any example of a possible usage of socket.io in a background task? (when the iOS app isn’t in the foreground)

I’m looking for a way to keep sending data to the server even if the screen is locked/the user moved into another app.

The text was updated successfully, but these errors were encountered:

nuclearace commented Aug 20, 2015

I’m not sure if that’s possible. iOS multitasking is pretty restrictive.

Sent from my iPhone

Any example of a possible usage of socket.io in a background task? (when the iOS app isn’t in the foreground)

I’m looking for a way to keep sending data to the server even if the screen is locked/the user moved into another app.

—
Reply to this email directly or view it on GitHub.

danishin commented Aug 21, 2015

@nuclearace Is it restrictive as in not allowing WebSockets at all (afaik it seems to allow low-level TCP socket connection only?) or as in only allowing when the intention is sound like being used for signaling channel for voip functionality?

nuclearace commented Aug 21, 2015

I haven’t really looked into it, since I wrote this library to be platform independent. But I think it has to with it only allowing VoIP connections in the background.

meismyles commented Aug 26, 2015

They actually expanded the scope of applications allowed to communicate in the background.
Now allow apps if they fall into a number of categories such as playing audio, location updates (navigation), VoIP, Newsstand, background fetch, remote notifications, etc.

nuclearace commented Aug 26, 2015

Yeah, but I actually have no idea how to properly do it with this library. (If it’s even possible)

meismyles commented Aug 26, 2015

Oh yeah, I was just letting the OP know that it is now theoretically allowed, not that it is possible with this library. I’ll potentially be attempting it soon so I’ll report back if I have any success.

meismyles commented Sep 17, 2015

Woops, forgot to reply. I implemented this client recently in an iOS app that plays audio and setting my applications background mode to audio kept the socket open and connected when the app was in the background. So it should work fine.

aniketc-gslab commented Mar 30, 2016

@meismyles , I am also going through the same issue, but when I activated Audio and VoIP background modes (and marked the socket.io client as voip = true while initializing) the connected socket is giving me the log as

2016-03-30 12:11:12.213 GSLVideoCallApp[3318:1287745] LOG SocketEngine: Writing ws: has data: 0
2016-03-30 12:11:12.214 GSLVideoCallApp[3318:1287745] LOG SocketEngine: Sending ws: as type: 2
2016-03-30 12:11:12.218 GSLVideoCallApp[3318:1287744] ERROR SocketEngine: connection closed by server

When I am switching the app to background and 2-3 minutes after locking the phone.
Is there something wrong I am doing or missing something.

shoaibhussan commented Oct 20, 2016

@meismyles please tell whether you were able to connect socket in background or not,
if yes,then please help us too.
Thanks

okankocyigit commented Aug 9, 2017

Has anybody solved this problem?

princenaman commented Oct 27, 2017

Any update or workaround sample?

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Socket IO Android Client Not Working In Android 8.0 Oreo Above #548

Comments

GulajavaMinistudio commented Aug 7, 2018

Notification with socketIO not work with app that target Android 8.0 above. This because behavior changes in Android 8.x for background executing limit and start using JobScheduler.

Any work around for this?
Or we shoudl migrate to Firebase Cloud Messaging ?

The text was updated successfully, but these errors were encountered:

IlyaDiallo commented Aug 7, 2018

What do you mean by «target Android 8.0», do you refer to the SDK version ?

GulajavaMinistudio commented Aug 8, 2018

Yes, Android SDK version 8.0 above. Socket IO Service is not running, because background execution limits in newest Android API.

IlyaDiallo commented Aug 8, 2018

Notifications are working except for background services. If you can live with a permanent notification for your app, a possible workaround is to use startForegroundService.

kushanshah11 commented Sep 10, 2018

i Have Done some of stuff and working fine in background and forground but when i kill it will not working.

public class ChatServiceWorker extends Worker <

private static final String TAG = «SocketService»;

private Socket mSocket;

private Context mContext;

private NotificationManager notificationManager;

private NotificationCompat.Builder notificationBuilder;

private int currentNotificationID = 0;

private void initSocket() <
mSocket.connect();
mSocket.on(Socket.EVENT_CONNECT_ERROR, onConnectError);
mSocket.on(Socket.EVENT_CONNECT_TIMEOUT, onConnectError);
mSocket.on(Socket.EVENT_CONNECT, onConnect);
mSocket.on(Socket.EVENT_RECONNECT, onConnect);
mSocket.on(Socket.EVENT_DISCONNECT, onConnectError);

// auth();
mSocket.on(«chat message», onReceived);
>

private Emitter.Listener onConnect = new Emitter.Listener() <
@OverRide
public void call(Object. args) <
Log.d(TAG, «connected » + mSocket.connected());
>
>;

private Emitter.Listener onConnectError = new Emitter.Listener() <
@OverRide
public void call(Object. args) <
Log.d(TAG, «error » + args[0].toString());
>
>;

private Emitter.Listener onReceived = new Emitter.Listener() <
@OverRide
public void call(final Object. args) <
Log.d(TAG, «received rtm»);
// I parse the object.
// binder.messageArrived(args[0].toString() + «,» + args[1].toString());

>;
/* @subscribe
public void sendMessage(SendMessageEvent event) <
mSocket.emit(«send», event.getMessage());
>*/

/* @OverRide
public void onDestroy() <
super.onDestroy();
Log.d(TAG, «onDestroy»);
mSocket.disconnect();
mSocket.off(Socket.EVENT_CONNECT_ERROR, onConnectError);
mSocket.off(Socket.EVENT_CONNECT_TIMEOUT, onConnectError);
mSocket.off(Socket.EVENT_CONNECT, onConnect);
mSocket.off(«chat message», onReceived);

/* @OverRide
public IBinder onBind(Intent intent) <
return binder;
>
*/
private void setDataForSimpleNotification(String message) <
notificationBuilder = (NotificationCompat.Builder) new NotificationCompat.Builder(mContext)
.setSmallIcon(R.drawable.ic_launcher)
.setContentTitle(«Chat»)
.setContentText(message);
sendNotification();
>

private void sendNotification() <
Intent notificationIntent = new Intent(mContext, MainActivity.class);
PendingIntent contentIntent = PendingIntent.getActivity(mContext, 0, notificationIntent, PendingIntent.FLAG_UPDATE_CURRENT);
notificationBuilder.setContentIntent(contentIntent);
Notification notification = notificationBuilder.build();
notification.flags |= Notification.FLAG_AUTO_CANCEL;
notification.defaults |= Notification.DEFAULT_SOUND;
currentNotificationID++;
int notificationId = currentNotificationID;
if (notificationId == Integer.MAX_VALUE — 1)
notificationId = 0;
notificationManager.notify(notificationId, notification);
>

public void sendMessage(String variable,String mUsername , String message)<

Источник

Socket io android background github

Socket.IO enables real-time bidirectional event-based communication. It consists of:

• a Node.js server (this repository)
• a Javascript client library for the browser (or a Node.js client)

Some implementations in other languages are also available:

Its main features are:

Connections are established even in the presence of:

• proxies and load balancers.
• personal firewall and antivirus software.

For this purpose, it relies on Engine.IO, which first establishes a long-polling connection, then tries to upgrade to better transports that are «tested» on the side, like WebSocket. Please see the Goals section for more information.

Unless instructed otherwise a disconnected client will try to reconnect forever, until the server is available again. Please see the available reconnection options here.

A heartbeat mechanism is implemented at the Engine.IO level, allowing both the server and the client to know when the other one is not responding anymore.

That functionality is achieved with timers set on both the server and the client, with timeout values (the pingInterval and pingTimeout parameters) shared during the connection handshake. Those timers require any subsequent client calls to be directed to the same server, hence the sticky-session requirement when using multiples nodes.

Any serializable data structures can be emitted, including:

Simple and convenient API

Browser support is tested in Sauce Labs:

In order to create separation of concerns within your application (for example per module, or based on permissions), Socket.IO allows you to create several Namespaces , which will act as separate communication channels but will share the same underlying connection.

Within each Namespace , you can define arbitrary channels, called Rooms , that sockets can join and leave. You can then broadcast to any given room, reaching every socket that has joined it.

This is a useful feature to send notifications to a group of users, or to a given user connected on several devices for example.

Note: Socket.IO is not a WebSocket implementation. Although Socket.IO indeed uses WebSocket as a transport when possible, it adds some metadata to each packet: the packet type, the namespace and the ack id when a message acknowledgement is needed. That is why a WebSocket client will not be able to successfully connect to a Socket.IO server, and a Socket.IO client will not be able to connect to a WebSocket server (like ws://echo.websocket.org ) either. Please see the protocol specification here.

The following example attaches socket.io to a plain Node.JS HTTP server listening on port 3000 .

In conjunction with Express

Starting with 3.0, express applications have become request handler functions that you pass to http or http Server instances. You need to pass the Server to socket.io , and not the express application function. Also make sure to call .listen on the server , not the app .

In conjunction with Koa

Like Express.JS, Koa works by exposing an application as a request handler function, but only by calling the callback method.

In conjunction with Fastify

To integrate Socket.io in your Fastify application you just need to register fastify-socket.io plugin. It will create a decorator called io .

Please see the documentation here.

The source code of the website can be found here. Contributions are welcome!

Socket.IO is powered by debug. In order to see all the debug output, run your app with the environment variable DEBUG including the desired scope.

To see the output from all of Socket.IO’s debugging scopes you can use:

This runs the gulp task test . By default the test will be run with the source code in lib directory.

Set the environmental variable TEST_VERSION to compat to test the transpiled es5-compat version of the code.

The gulp task test will always transpile the source code into es5 and export to dist first before running the test.

Support us with a monthly donation and help us continue our activities. [Become a backer]

Become a sponsor and get your logo on our README on Github with a link to your site. [Become a sponsor]

Источник