[BogdanV]

There's a big issue using "Connect Tablets" on iPad (not sure about other systems). When I turn off display on master tablet, clients lose connection. I suspect this is a "feature" of iOS. But when I turn the display back on, the client tablets do not reconnect, even though I have "automatic reconnect" turned on on both master and client tablets. The only workaround I have found so far is this: on master tablet I click "Disconnect" and create another server (by clicking "New Leader") with the same settings. Then the clients reconnect immediately. 

This is a big issue on live gigs when time is short and stress is high. For example: we have a soundcheck and we sync all tablets and everything works. The gig is two hours after the sound check, so naturally we turn of display on all iPads. When the gig starts, we go on stage, turn on each our own iPad and ... the sync is gone. The panic ensues, everyone starts solving the issue on their own tablet and we end up in a mess.

Is there any way around this?

[Zubersoft]

I'll look into it. There is nothing I can do about the operating system shutting off the network connection - that's out of my control. However, the fact that the devices aren't reconnecting is concerning. I'll have to see if I can reproduce that, and if so, try to figure out why that's occurring. You did not mention if you are connecting over WiFi or bluetooth. I really need that information.

Thanks,
Mike

[BogdanV]

I'll look into it. There is nothing I can do about the operating system shutting off the network connection - that's out of my control. However, the fact that the devices aren't reconnecting is concerning. I'll have to see if I can reproduce that, and if so, try to figure out why that's occurring. You did not mention if you are connecting over WiFi or bluetooth. I really need that information.

Thanks,
Mike

Thank you.We're connected over Wifi.

[BogdanV]

Any news on this front? Were you able to reproduce the issue?

[otnt]

Any news on this front? Were you able to reproduce the issue?

Hi Bogdan, 
I'm connecting Android tablets via Bluetooth. 
In similar situation when master turns off the screen it would disconnect follower devices.
After confirming YES in pop-up windows on followers devices to reconnect, followers would eventually reconnect after while. It would not be immediately. 

However in between the soundcheck/rehearsal and the live show/concert I would always disconnect tablets and switch off the Bluetooth to save the power.
They would connect straight away after that.

[carlo]

Any news on this front? Were you able to reproduce the issue?

Hi BogdanV,

My 2¢ here. I have two iPad Pro devices (both identical) running iPadOS 26.0.1 and MSP 3.9.29.

I connect them via Bluetooth and have only the client set to “automatic reconnect.” When both devices power back on, I start the master first and then the client (not sure if the order really matters, though), and they both reconnect successfully.

With Wifi I had the impression that sometimes all depends on the status of the IP stack and if it’s not fully ready when they try to reconnect, that when the pain starts. But, as I said, this may be only my impression.

[Zubersoft]

Not yet - it's still on the list of things to do. I was dealing with Google's looming deadline for 16kb page sizes and the forced targeting of Android 16, and had to make massive changes to the Android version because of this (which is the source of a lot of recent problems for some users).

Mike

[Zubersoft]

I definitely see the problem. I'm investigating now to see where the source of the problem is.

Mike

[Zubersoft]

I understand now why I never saw the problem - if I have a debugger attached to be able to monitor the behavior, the tablet does not kill the connection. If I run the app without the debugger, then it kills the network connection when the screen is turned off. So I'm going to need to add code to explicitly close the wifi connection myself when the tablet screen is turned off, then recreate the connection when it's resumed.

Mike

[Zubersoft]

This is a bit problematic because Apple provides no way at all to distinguish from the screen turning off vs the user just moving the app into the background (which does not kill the WiFi connection). So my current approach for this is, I'm going to do nothing when the app goes into the background (either by multi-tasking or the screen turning off), but when the app is resumed, I will recreate all of the connections. So users may see a small blip as connections as severed and recreated if they resume the app. There is no seamless way to handle this due to the behavior Apple decided on.

I just tested this, and it worked extremely well - the reconnection happens nearly instantly and then everything works correctly after.

Mike

[BogdanV]

I just tested the updated version yesterday at our band's rehearsal. I can confirm it works extremely well. Thank you for your effort.

[Zubersoft]

Excellent! Thanks for following up and for your patience in waiting for the fix.

Mike