Demo instance really representative of the actual thing?

[tehabe]

I'm think about switching from Plex to Navidrome or a similar subsonic-compatible server. And I wanted to try it, so I downloaded Submariner and just used the Navidrome demo instance to get a feeling how this would work on macOS and got the message "canceled" when trying to play something but the song played anyway.

I wonder if this is just the demo instance of Navidrome or could this be a bug. Should I consider another server which is more compatible?

[NattyNarwhal]

Oh, that's weird - this does seem to be Navidrome demo server specific. I use Navidrome for my personal server, so Navidrome itself is well tested.

I think this might be a Submariner bug exposed by the demo server, I'll have to dig into this more. But do try Navidrome; it should work fine for you. If not, Subsonic (and its forks like Airsonic) should work (I've tested it, but not as well as Navidrome), and others report success with other implementations like lms.

[NattyNarwhal]

Fun log material:

2023-05-04 17:48:02.163449-0300 Submariner[9096:922961] [API] API MISUSE: NSURLSession delegate Submariner.SBSubsonicDownloadOperation: <Submariner.SBSubsonicDownloadOperation: 0x127a04730> (0x127a04730)
2023-05-04 17:48:02.163500-0300 Submariner[9096:922961] [API] API MISUSE: task:didReceiveChallenge:completionHandler: completion handler called more than once
2023-05-04 17:48:21.930972-0300 Submariner[9096:922177] [quic] quic_conn_keepalive_handler [C102.1.1.1:2] [-bdc375dd] keep-alive timer fired, exceeding 2 outstanding keep-alives
2023-05-04 17:48:21.934488-0300 Submariner[9096:922177] [connection] nw_read_request_report [C102] Receive failed with error "Operation timed out"
2023-05-04 17:48:21.934800-0300 Submariner[9096:922177] [connection] nw_read_request_report [C102] Receive failed with error "Operation timed out"
2023-05-04 17:48:21.936203-0300 Submariner[9096:922177] [h3connection] 0x144840a18 102 stalled, attempting fallback
2023-05-04 17:48:21.936407-0300 Submariner[9096:922177] [h3stream] Task <20559793-1E04-4332-9AB0-3BEA1DCB029E>.<1> 0x101c0ac58 ID=0 handling fallback
2023-05-04 17:48:26.301938-0300 Submariner[9096:808548] [default] CGSWindowShmemCreateWithPort failed on port 0
2023-05-04 17:48:26.306711-0300 Submariner[9096:808548] [default] CGSWindowShmemCreateWithPort failed on port 0
2023-05-04 17:48:27.040116-0300 Submariner[9096:923781] [Symptoms] {
  "transportType" : "HTTP Progressive Download",
  "mediaType" : "HTTP Progressive Download",
  "BundleID" : "Submariner",
  "name" : "MEDIA_PLAYBACK_STALL",
  "interfaceType" : "WiredEthernet"
}
2023-05-04 17:48:29.732308-0300 Submariner[9096:922177] [API] API MISUSE: NSURLSession delegate Submariner.SBSubsonicDownloadOperation: <Submariner.SBSubsonicDownloadOperation: 0x123e11100> (0x123e11100)
2023-05-04 17:48:29.732361-0300 Submariner[9096:922177] [API] API MISUSE: task:didReceiveChallenge:completionHandler: completion handler called more than once

This affects the HTTP client stuff; parallel requests HTTP/2 or 3 connections seem to have issues? That includes things like downloading a track, for instance. My reverse proxy only exposes HTTP/1.1, so I probably haven't noticed that.

[NattyNarwhal]

Oh, never mind, the control flow handling authentication challenges was messed up. This should be fixed in 0d96af2.