Hi Seungjin, Does the new 2.28 release now support the latest macOS, or are there still issues with releases after Big Sur? Thanks, Jeremy
Hello, Jeremy, The issue is on macOS itself not on our app. From this thread -- https://developer.apple.com/forums/thread/694146, you can see what is going on. Thanks
Ah. Doesn't seem Apple has any intent on fixing the methods it broke in the new BT stack. From other products I've got it seems that they've recoded bits of their drivers to use some newer methods (I'd be lying if I said I actually knew anything about what Apple has actually changed in the stack...other than dropping support for a number of older chipsets). Was hoping you'd done the same with this release. On a newer Mac, so don't have the option of using Big Sur.
Forget about Bluetooth. The app no longer even launches on Monterey or Ventura. The error is a missing libavfilter.dylib. The developer should stop claiming, as they did with the 2.28 release, that the update should be done for all platforms. macOS is simply no longer supported, for paid or unpaid customers, and this should be reflected in the documentation. As it is, users will have their money stolen unless they consult these forums first.
Yeah. It's unfortunate. This was a much better product than the network-based kvms out there. I could use it both for work and controlling games on a remote machine. Network-based gets a big laggy for game controls and keyboard events aren't always correct (i.e. left and right shift are not treated uniquely, same with left and right option, caps lock doesn't work with ms remote desktop unless in unicode mode and then shift doesn't work). So was really hoping we'd see some changes in Across to get it working on Mac again, but when this release didn't address any of that, does seem we've probably reached the end of this road.
Hi, guys! @jeglin, There could be some problems in bundling the app package. I apologize for the issue. We will release v2.29 fixing the issue ASAP. Thanks in advance for your patience. @Jeremy, We have nothing to do from our side because the macOS Bluetooth stack except the core Bluetooth functions macOS is using doesn't work at all. That is, apple prevents other 3rd party developers from using Bluetooth and no official/unofficial comment on the issue yet, as you can see in the apple developer forum threads. You have to consult to apple instead of us on the issue. Thanks.
Understandable from your end, but after two versions of MacOS, I think it's safe to say that Apple also has no intention of changing anything on their end. So seems a bit of a stalemate. In that regard, do agree with Jeglin, that you should update the product page and either state compatibility is through MacOS 11 only (not supported on 12 or 13) or just remove Mac as a supported platform altogether. Or another suggestion: you could make it such that you could at least pair using the network (rather than bluetooth) stack on the initial setup and then change the support statement to network only on 12 and above.
Jumping in here after many months, hoping to see an announcement that it works with newer MacOS versions... only to find the same lame excuse from the developer. "It's Apple's fault"... Stop, just stop. I'm sorry, but it's not Apple's fault that we still see "compatible with MacOS 10.17 or later" everywhere on this website. The only way to find out it won't work with MacOS 11+ is digging into this forum. There's a word for that: deception. At this point, saying this is compatible with MacOS is the same as saying an app will work with Windows XP+... but only up to Windows 7. If you don't want this to be seen as an easy money grab, please update the website and make it clear that it won't work with MacOS devices updated in the last 3 years. (/end of harsh response)
Hi @seungjin-lee, Do you have any response to @Jeremy's suggestion? Supporting network pairing would greatly simplify my situation as well. Or you could use Core Bluetooth for pairing which should work. (I'm not familiar with macOS programming, but AFAIU, Apple adds its own wrapper API to bluetooth. It's a giant ecosystem, there's no way that a bluetooth connection can't be made by 3rd parties. Pairing actually does work through the app. But anyway, I'm a layman on bluetooth side.) I'm now trying to somehow carry over Across's app config state from an older Big Sur machine (which is paired with my devices) to an M1 MacBook Air with Ventura to see if it would work with NET... It's pretty much a UI constraint.