Open microbit-mark opened 2 years ago
User reports that Scratch Link did work as expected in macOS11 Big Sur, so this appears to relate to the upgrade.
Thanks for the report! I'm sorry to hear about the trouble. It seems a lot of applications are having problems with Bluetooth in macOS 12. We'll try to figure out the problem but I can't promise it'll be quick.
Here's an example of the kind of thing I see when looking for information about Bluetooth on macOS 12: https://developer.apple.com/forums/thread/694146
Could it be that recentDevices is not populated correctly? I got to my surprise connectivity to Lego devices after I started the old Scratch Device Manager, which has no sense except that perhaps it hit the good point in the BLE stack. I have been unable to reproduce :-(
It seems that only BLE session works fine on macOS 12.3 beta. BT session still have some problems, but I think it's getting better.
I'm having the exact same issue trying to use Scratch Link to connect to LEGO Boost, on macOS 12.2 on a MacBook Pro (14", Apple Silicon processor). I'll subscribe to this issue to see if anything comes up in terms of a fix — and I'm happy to provide any debug information that might be helpful.
The suggestion of recompile and keep the process "active" (ie, with the dot in the dock bar) worked for me
El dom, 30 ene 2022 a las 5:36, Jason Levine @.***>) escribió:
I'm having the exact same issue trying to use Scratch Link to connect to LEGO Boost, on macOS 12.2 on a MacBook Pro (14", Apple Silicon processor). I'll subscribe to this issue to see if anything comes up in terms of a fix — and I'm happy to provide any debug information that might be helpful.
— Reply to this email directly, view it on GitHub https://github.com/LLK/scratch-link/issues/198#issuecomment-1025067951, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAKRJWK4NCHHDUAA5XV6BTUYS547ANCNFSM5IT5BW2A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
Basically I compiled bricklife's fork and followed the suggestions discussed here:
var thisProcess = ProcessSerialNumber(highLongOfPSN: 0, lowLongOfPSN: UInt32(kCurrentProcess))
TransformProcessType(&thisProcess, ProcessApplicationTransformState(kProcessTransformToUIElementApplication))
oh, i have same problem with this, my micro:bit is v1.3 interface version 0249 scratch Link 1.3.82 macOS version 11.4 chorme version 98.0.4758.80
I'm having the same issue: macOS v. 12.2.1 Scratch Link 1.3.82 d5ccbe7 Browser: safari Version 15.3 and Chrome 98.0.4758.102
With Scratch Link 1.4.3 and macOS 12.3, micro:bit has been successfully found and connected.
Guys, Is it working for macOS 12.3.1, scratch link 1.4.3?
It is not working for me with the above :(
Just tested with M1 mac mini and macOS 12.4, Safari 15.5. The website at scratch.mit.edu will not link via Scratch Link, but the Scratch app v3.29.1 appears to work fine.
Scratch Link 1.4.x now does not support Safari. Read this section: https://github.com/LLK/scratch-link#secure-websockets
Many thanks for pointing to that @bricklife
This change causes an incompatibility with some browsers, including Safari. An upcoming version of Scratch Link will resolve this incompatibility.
It's seems to be working for me in Chrome.
Expected Behavior
micro:bit should connect to Scratch
Actual Behavior
Following process set out in https://scratch.mit.edu/microbit no device is found by Scratch in the browser
ScratchLink is running but micro:bit is not visible under Bluetooth devices or in Scratch
ScratchLink has access to Bluetooth![image](https://user-images.githubusercontent.com/31242877/143061598-ef2c9d71-1598-4efd-9ee4-d3e5fe29cae2.png)
Steps to Reproduce
Explain what someone needs to do in order to see what's described in Actual behavior above
Steps to reproduce the behavior:
System Details
If the problem occurs in the browser, please provide operating system and browser e.g. Mac OS 10.11.6 Safari 10.0