BluOS Controller hanging on startup

Beantwortet

Severino Adler

• 15. Mai 2022 19:29
• Bearbeitet

Dear support Crew,

I am running the BluOS Controller Version 3.18.1 on my Macbook (13-inch, 2017, Two Thunderbolt 3 ports) with macOS 12.3.1 (So it is up to date). Unfortunately it hangs directly when starting showing only a black screen. It is completely unresponsive, so I have to Force Quit it. It was running when I first tried to set up my bluesound node over WiFi (Though it was terribly slow). However, that didn't work since I tried it with the iOS app and set a password that was not properly configured and in the end airplay was not working. Afterwards, I hard reseted the node and did the setup using ethernet. Now airplay works fine. In the process I also reinstalled the BluOS Controller app on my MacBook. Since then it hangs on startup. 
I tried it with ethernet connection, in other WiFi networks and with all network disabled. Nothing makes the app at least show me anything else than a black screen.
My first guess was leftover files or network configurations from the previous install. I tried searching the file system with the locate command on the command line and didn't find any. I also deleted some of the network configuration files that didn't help too.

I would like the app to run on my MacBook too. Any Ideas what to do?

Best,
Sever

0

• Offizieller Kommentar

  

  Tony W.

  Product Support Manager

  • 16. Mai 2022 12:49

  Hi Severino

  Your App may be having issues locating the players on your network. Please ensure your MacBook is on the same network as your Players and multicast traffic is enabled.

  If problems persist, please e-mail us at support@bluesound.com so we may take a closer look.
• 

  Severino Adler

  • 17. Mai 2022 15:19

  I resolved the Problem. It was after all traces from the previous install. Mainly they are located in ~/Library/Application\ Support/, ~/Library/Preferences, ~/Library/Cache, ~/Library/Saved\ Application\ State. If I had to guess I would say the crash was probably caused by the saved application state. Anyhow, I strongly recommend implementing a proper uninstall routine in the app to avoid this sort of problems. I know it is very convenient to simply delete an app, but searching for traces afterwards is a really nasty user experience and a proper uninstall routine should be part of any proper software.

  Best regards,
  Sever

  1
• 

  Milan Holý

  • 17. Mai 2022 20:14

  I had the same issue today on m1 mac with the same macOS. Severino thank you for solution!

  0
• 

  Tom Coppens

  • 25. Mai 2022 19:06

  I had also the same issue, but cant fix the problem. I don't understand Severino solution. Do i have to delete something else? The location: ~/Library/Application\ Support/, ~/Library/Preferences, ~/Library/Cache, ~/Library/Saved\ Application\ State

  I cannot find??

  Thanks

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.