I've created a super simple Capture 2025 project with just a single fixture. I'm using two iPads, iPad A running Blackout Lighting, iPad B running Capture Mobile. Blackout Lighting is outputting sACN.
Unfortunately, Capture Mobile does not seem to receive or interpret any of the sACN data.
In order to nail down the root cause for this, I've connected a Mac to the same Wi-Fi network as iPad A and iPad B. Rest assured, sACN View does immediately see the sACN traffic and Capture for Mac also works as expected. So it's just Capture Mobile that's not working at all.
There seem to be zero settings in Capture Mobile and zero views that would help troubleshoot. Any hints how we can make use of this advertised feature?
On further investigation, does Capture Mobile maybe require the "Local Network" permission? Right now, Capture Mobile doesn't even show up in Settings > Privacy & Security > Local Network on iOS.
According to Apple's developer documentation the following operations do explicitly require those permissions:
Source: https://developer.apple.c...ocal-network-privacy
This might be the root cause.
Capture Mobile should have a setting for local network access. There should also be settings for Capture Mobile, accessible from the Settings app, under the Apps section. There are a few sACN specific options that may be relevant if you are not using the first 16 sACN universes.
I'm not sure that comparing with a Mac says a lot at all. It's a different operating system and your router / WiFi access point may also understand that it's a different type of device and apply other rules.
If possible I would suggest you try Art-Net instead. It is generally much easier to get UDP unicast and broadcast traffic through networks.
Capture Mobile does have this entitlement. I just double checked and had no problems receiving Art-Net.
This is far more likely to be a networking environment problem than anything else. I would recommend that you restart your devices, including all your networking equipment. I have seen routers and switches fail to keep track of multicast membership too many times. That wouldn't explain why you are unable to get Art-Net through, but some routers, WiFi-routers in particular, do block broadcast traffic.
On top of this - receiving sACN or Art-Net over WiFi is often problematic anyway. I would strongly recommend that you use an ethernet adapter and go cabled. Most WiFi access points will bundle up messages and send them in bursts, resulting in a 5 fps experience.
We are definitely linking this entitlement when building, it is there. There will be another reason for it not appearing in the UI. I suspect the reason is that we don't set a NSLocalNetworkUsageDescription. We'll look into that.
I did an interesting test - I completely uninstalled the app and then reinstalled it. At that point the Local Network option in the settings disappeared. So what I think has happened is that if you have had the question answered in a previous version of iOS then the option remains available. But if you completely reinstall the app it disappears. I'm guessing something changed in iOS 26.
However, even with the option gone, I had no issues sending Art-Net to the app. We will do further tests with this week, using sACN as well.