ChrisHenderson

@Tony Quan The Android team says that they didn't fix the issue yet. It could be a driver issue, or possibly simply the act of updating the app fixed it somehow? Either way, if you run into the problem again, feel free to reach out. It's hard to figure out why it broke if it's working again, but if it breaks again, we can take another look. Thanks so much for your help! We try to resolve bugs as quickly as possible, but sometimes we have several bugs we're looking into at the same time. We really appreciate your helpfulness in fixing the bug for iOS!

I'm not sure, as I've not worked with soundbars before. I'm one of the iOS app developers, so TV's aren't my area of expertise. My first thought would be to reach out to a dealer, or Control4's tech support if you are a dealer. It's possible that there's a driver option for that or maybe the driver doesn't support the soundbar? Does it work with a touchscreen (i.e., T3 or T4)?

A big thanks to @South Africa C4 user for helping diagnose the first bug I mentioned!

Upon further inspection, we found that there were two bugs in the iOS app that broke DS2 playback. Bug #1: The iOS app treated the "Use HTTPS" checkbox in Composer differently than Android. On Android, checking that box enables HTTPS. On iOS, it enables HTTPS and RTSPS. The DS2 does not support RTSPS, however. I fixed this bug yesterday, making that checkbox only enable HTTPS. Bug #2: We updated a library that we use for RTSP that broke DS2 playback. That update hasn't made it's way to the App Store yet, so we're going to revert that change and fix it before it goes public. (This is why we have a 2 week testing period before releasing apps on the App Store.) We are expediting both of these fixes and they should be available on the App Store in a week. It sounds like they're having other issues with this new DS2 driver and firmware related to Intercom as well that are not related to these iOS bugs I just mentioned.

Thanks for testing that out! I let them know that it didn't fix it.

@Tony Quan The Android team looked at the logs. They can't reproduce the issue, but they believe that your project may be missing a "refresh navigators." Every time a dealer makes a change, they're supposed to refresh navigators so that the changes will be fully applied. There's a way to do it via the mobile apps as well. Could you go to "Settings > Support > Support Settings > Sync Settings > Sync my system". They say that if you still have problems after that they can look into it more. Just let me know if that fixes it for you.

Hello, @Tony Quan! Welcome to Control4! I'm terribly sorry it's not working on Android for you! I just chatted with one of the Android developers and he confirmed that this bug hasn't been reported yet. He says he'll look into it, but he needs a controller snapshot. It's a zip file that contains the controller and touchscreen logs. It can be generated via Composer, if you're a dealer. If you're not a dealer, could you ask your dealer to provide the snapshot and email it to me? I'll PM you my email address.

I do see some notes in Composer about how the DS2 RTSP URL changed recently. That wouldn't explain why the T4 works but not iOS though.

It seems to be working fine for me with the latest App Store version, 324.21.0. Could you reproduce the bug on iOS and then email me the logs? I'll PM you my email.

There are some potential issues with OS 3.4.2 + latest DS2 driver + Intercom that some of my coworkers are looking into. I'm personally looking into iOS app + DS2 camera feed (not for Intercom).

@South Africa C4 user I'm sorry that it stopped working! I'll take a look on Monday when I'm in the office and have access to a DS2.

Sadly, that bug number is for something unrelated. I looked for other bugs and found DRIV-10015, which was about this issue. Maybe that's the one you were talking about? Anyways, DRIV-10015 is a closed bug and says that the logout issue was fixed in version 12 of the TuneIn Premium driver. Opening Composer, I see that v13 seems to be the latest for the "TuneIn" driver, last updated 2023-09-22. Maybe you could try updating your driver?

Hello, @Kaas Mayer! I'm sorry it's been a problem for so long. Do you know who you were talking to or what the ticket/bug number was?

Sorry, I missed this. Yes, we fixed a bug that caused this. @fvierra27 Are you still seeing the problem? The bug fix should be released now.

Dang, that's a long wait. I'll forward this to the Android team and ask them if they can get logs sooner.