iOS (and Android) b...
 
Notifications
Clear all

iOS (and Android) bug when trying to play to a JRiver access key server (not the device running WR) which is a client of another JRiver "main" library server

3 Posts
2 Users
0 Reactions
234 Views
(@craigmcg1965)
Posts: 17
Eminent Member
Topic starter
 
[#26]

The connectivity is  Whiskey River on Ipad or S23 connected to JRiver access key jrJiax which pulls the library from "main" library server access key TmdofT.

When I ask WR to play to jrJiax the app screen shows playback but there's no audio output on the desire playback device jrJiax (my laptop) but the playback actually comes from the "main" library server  TmdofT.

My expectation is that actual playback should be on the access key server specified in WR (jrJiax in this case) NOT the access key that is the main source of the music (TmdofT in this case). If I wanted playback to be on Tmdoft,  I would connect to that access key.

Can this be corrected in both versions as dev time permits?


 
Posted : 24/05/2026 4:12 pm
(@craigmcg1965)
Posts: 17
Eminent Member
Topic starter
 

This bug can be closed because I can no longer replicate it on either Android or iOS. Given the number of software updates on Windows, Linux, etc. whatever was causing the misbehavior that I reported in the early Android testing and early iOS testing over a week ago, is no longer doing so. Sorry for the noise.


 
Posted : 02/06/2026 1:50 pm
Stevo
(@px)
Posts: 44
Member Admin
 

No worries.  Submitting update to Google today.  Will post when submitted.


 
Posted : 03/06/2026 6:44 pm
Share: