I seem to have this same problem with both of my Belas now. I have mini and the normal.
Hmm, I have no recollection when I tried last time to log in to bela with IDE. I was yesterday trying to use Super Collider code with my Bela, and I got in to IDE nicely but ran into some error of not having some library working so I updated to the new image and now I can't get IDE launched.

I tried the same procedure as adviced above but with no results.

Can you run the following commands in a terminal on your computer and post here the output they give you ?

ifconfig
cat /Volumes/BELABOOT/bela.version
ls /dev/tty*bela*
ioreg -p IOUSB -w0 -l

Yeah! Here it comes in separate comments:

jukkakaariainen@Jukka-MacBook-Pro ~ % ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
anpi1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 8a:5f:dc:e5:5b:07
media: none
status: inactive
anpi0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 8a:5f:dc:e5:5b:06
media: none
status: inactive
en3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 8a:5f:dc:e5:5b:e6
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 8a:5f:dc:e5:5b:e7
nd6 options=201<PERFORMNUD,DAD>
media: none
status: inactive
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:83:c3:da:82:80
media: autoselect <full-duplex>
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 36:83:c3:da:82:84
media: autoselect <full-duplex>
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 36:83:c3:da:82:80
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 8 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 9 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: <unknown type>
status: inactive
ap1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether b2:be:83:71:80:44
inet6 fe80::b0be:83ff:fe71:8044%ap1 prefixlen 64 scopeid 0xb
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (<unknown type>)
status: inactive
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether b0:be:83:71:80:44
inet6 fe80::1c74:7e9a:45c2:7329%en0 prefixlen 64 secured scopeid 0xc
inet6 2001:999:508:7fb:18cc:e6a9:89b6:2c0 prefixlen 64 autoconf secured
inet6 2001:999:508:7fb:4941:9e6e:8e2b:7d49 prefixlen 64 autoconf temporary
inet 192.168.27.38 netmask 0xffffff00 broadcast 192.168.27.255
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
awdl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether 8a:24:36:ea:6b:0e
inet6 fe80::8824:36ff:feea:6b0e%awdl0 prefixlen 64 scopeid 0xd
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 8a:24:36:ea:6b:0e
inet6 fe80::8824:36ff:feea:6b0e%llw0 prefixlen 64 scopeid 0xe
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::7f3a:11b:6425:a1ee%utun0 prefixlen 64 scopeid 0xf
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1000
inet6 fe80::ce81:b1c:bd2c:69e%utun1 prefixlen 64 scopeid 0x10
nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::ba77:83a1:345e:b175%utun2 prefixlen 64 scopeid 0x11
nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet6 fe80::95fa:8dec:679e:d5be%utun3 prefixlen 64 scopeid 0x12
nd6 options=201<PERFORMNUD,DAD>
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=404<VLAN_MTU,CHANNEL_IO>
ether 48:65:ee:1a:39:21
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (none)
status: inactive
en6: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
options=404<VLAN_MTU,CHANNEL_IO>
ether be:1a:ad:42:71:8e
media: autoselect (none)
status: inactive

    jukkakaariainen@Jukka-MacBook-Pro ~ % cat /Volumes/BELABOOT/bela.version
    BELA_IMAGE_VERSION="v0.3.8g"
    jukkakaariainen@Jukka-MacBook-Pro ~ % ls /dev/ttybela
    /dev/tty.usbmodembela6

    Jukkapoika Ah, actually it's so long answer from the "ioreg -p IOUSB -w0 -l" that I can't get it fit here

    no need at this point, we have all we need.

    Jukkapoika en6: flags=8822<BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
    options=404<VLAN_MTU,CHANNEL_IO>
    ether be:1a:ad:42:71:8e
    media: autoselect (none)
    status: inactive

    This is the Bela network, can you see in System Settings -> Network whether it shows up and how it's configured?

    I'd expect running this in the terminal to also fix it:

    sudo ifconfig en6 up

        Yeah, I actually tried this already earlier and it doesn't have an effect. It still doesn't connect to IDE.
        It changes the status to active:

        en6: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=404<VLAN_MTU,CHANNEL_IO>
        ether be:1a:ad:42:71:8e
        media: autoselect (100baseTX <full-duplex>)
        status: active

        Also if I disconnect the bela and reconnect it the status has changed to inactive.

        When connecting the Bela, BELABOOT shows up on my desktop
        But if I connect my Bela mini. It doesn't show up at all for a reason or another.

          Jukkapoika

          I don't know if this helps at all, but this kind of behaviour use to happen when having couple of different Bela's also before. That the other one didn't appear. And my work around was that I went to check the /user/.shh folder and remove the shh keys from the known_hosts file.

          But this doesn't seem to work anymore. And seems like my mac is not writing new ssh keys to that known_hosts file anymore.

            Open System Settings -> Network and there should be a connection named "Bela". Click on it, what does it show? I see this:

            I have icon appearing now here for neither of Bela's..
            Is there some settings that has changed after updating operating system at my mac?

            When I connect a new board I get a prompt that asks "allow accessory to connect to this computer" (or similar).
            Then my Network page looks like this:

            12 days later

            Hi, sorry for the delay. I got so deep in to other work during last two weeks.

            Hey, this problem seemed to be changed after I updated my operating system on my macbook. I am now on Sonoma 14.4.1 and currently I get an icon appearing to my desktop.
            However, I don't see the icon appearing at my network page and I can get the IDE to open at my browser, nor if I try to run scripts through terminal.

            Can there be some kind of firewall settings that might not let the ssh connection to work with Bela?

            And, now weirdly, everything is running smoothly. I visited my mac in safetymode and some how things are working in normal order even without safetymode. So, basically I am all good. Sorry to bother with this topic. I don't what was wrong in the end.

            If the issue resurfaces, have a look at what's in System Settings: select Bela and check details. If the interface doesn't have the 192.168.7.1 address, you can/should set it manually. It worked here.