You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I followed the guide step-by-step up to the part where the controller on the iOS app is connected to the Dolphin Ctrl Server. When I get to this step and go to test configuration of the controller I get this:
You see that I have the controller connected to the server but it displays as disconnected. When I hit 'Refresh', the Dolphin app crashes and won't open back up, it will just open and then immediately close after.
I wasn't able to get a reason as to why the app crashed since I couldn't open it, so I had to open the Dolphin app through the package contents and running the unix executable file in the terminal. This is the error that is thrown when I try to open the app:
Last login: Mon Aug 7 21:12:20 on ttys003
/Applications/Dolphin.app/Contents/MacOS/Dolphin ; exit;
(base) usr@usr-mbp ~ % /Applications/Dolphin.app/Contents/MacOS/Dolphin ; exit;
libc++abi: terminating due to uncaught exception of type std::__1::__fs::filesystem::filesystem_error: filesystem error: in file_size: Operation not supported ["/Users/usr/Library/Application Support/Dolphin/Pipes/ctrl1"]
zsh: abort /Applications/Dolphin.app/Contents/MacOS/Dolphin
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
So naturally, I go to the Pipes directory – located in the hidden directory 'Library' which can be shown by doing ⌘ + Shift + Period or just by using the Go command in the Finder app – and see that ctrl1 does exist in the path, but I am not sure about the file_size error?
(base) usr@usr-mbp Pipes % ls
ctrl1
So anyways, I am able to open my Dolphin app again by simply removing the ctrl1 FIFO by – 'rm ctrl1' in the Pipes directory. Was wondering why this is happening and is there a workaround? Hopefully this is enough information to replicate the error, please let me know if need more information.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, I followed the guide step-by-step up to the part where the controller on the iOS app is connected to the Dolphin Ctrl Server. When I get to this step and go to test configuration of the controller I get this:
You see that I have the controller connected to the server but it displays as disconnected. When I hit 'Refresh', the Dolphin app crashes and won't open back up, it will just open and then immediately close after.
I wasn't able to get a reason as to why the app crashed since I couldn't open it, so I had to open the Dolphin app through the package contents and running the unix executable file in the terminal. This is the error that is thrown when I try to open the app:
Last login: Mon Aug 7 21:12:20 on ttys003
/Applications/Dolphin.app/Contents/MacOS/Dolphin ; exit;
(base) usr@usr-mbp ~ % /Applications/Dolphin.app/Contents/MacOS/Dolphin ; exit;
libc++abi: terminating due to uncaught exception of type std::__1::__fs::filesystem::filesystem_error: filesystem error: in file_size: Operation not supported ["/Users/usr/Library/Application Support/Dolphin/Pipes/ctrl1"]
zsh: abort /Applications/Dolphin.app/Contents/MacOS/Dolphin
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
So naturally, I go to the Pipes directory – located in the hidden directory 'Library' which can be shown by doing ⌘ + Shift + Period or just by using the Go command in the Finder app – and see that ctrl1 does exist in the path, but I am not sure about the file_size error?
(base) usr@usr-mbp Pipes % ls
ctrl1
So anyways, I am able to open my Dolphin app again by simply removing the ctrl1 FIFO by – 'rm ctrl1' in the Pipes directory. Was wondering why this is happening and is there a workaround? Hopefully this is enough information to replicate the error, please let me know if need more information.
Beta Was this translation helpful? Give feedback.
All reactions