This leaves mount point intact and the OS remembers it
Start up a different Ambly-enabled app locally and attempt to connect
Step 4 fails because Ambly derives the mount point name from the Bonjour name. This produces a new mount directory. But the old mount point gets re-established by the OS when the new app starts up on the same http://127.0.0.1:[port] endpoint. This prevents mounting this same endpoint under the new directory.
The solution is probably to instead derive the mount point directory name from the HTTP URL (which doesn't change in the sequence above), so that things can be properly dealt with and the mount re-established properly by Ambly.
Step 4 fails because Ambly derives the mount point name from the Bonjour name. This produces a new mount directory. But the old mount point gets re-established by the OS when the new app starts up on the same http://127.0.0.1:[port] endpoint. This prevents mounting this same endpoint under the new directory.
The solution is probably to instead derive the mount point directory name from the HTTP URL (which doesn't change in the sequence above), so that things can be properly dealt with and the mount re-established properly by Ambly.