Ultrasonic can't connet to Subsonic 6.1.4 #238
Comments
Same problème after update subsonic server to 6.1.4 |
hi, for add more information, when i want to connect the app to my server there are no reaching time, the app say directly that there are an issue with the network... if i shutdown the server, the app take a little time to say that there are an issue with the network. thanks this is a screenshot of the message : https://ibb.co/hfwxZf |
just for information ultrasonic also bug with the official demo server : http://demo.subsonic.org |
@Tapchicoma is a problem with API version. Latest version of Subsonic reports API version Here is the error:
The Subsonic changelog says that new point added:
The changes in was in Artist: <xs:complexType name="Artist">
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="artistImageUrl" type="xs:string" use="optional"/>
<!-- Added in 1.16.1 -->
<xs:attribute name="starred" type="xs:dateTime" use="optional"/>
<!-- Added in 1.10.1 -->
<xs:attribute name="userRating" type="sub:UserRating" use="optional"/>
<!-- Added in 1.13.0 -->
<xs:attribute name="averageRating" type="sub:AverageRating" use="optional"/>
<!-- Added in 1.13.0 -->
</xs:complexType> And in ArtistID3: <xs:complexType name="ArtistID3">
<xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="name" type="xs:string" use="required"/>
<xs:attribute name="coverArt" type="xs:string" use="optional"/>
<xs:attribute name="artistImageUrl" type="xs:string" use="optional"/>
<!-- Added in 1.16.1 -->
<xs:attribute name="albumCount" type="xs:int" use="required"/>
<xs:attribute name="starred" type="xs:dateTime" use="optional"/>
</xs:complexType> The new version of API simply add a new optional attribute. |
Makes sense, though it is not possible for now to make an app update on play store, as app still targets api 22 😞 Though we can still make an update to F-Droid. |
@Tapchicoma is a workaround, better than nothing 😅 |
yep |
Is there some ETA for the F-Droid update please? |
@weendigo the new tag was created but we has not control over F-Droid builds. In the meantime you can download our GitHub build. |
@ogarcia Thanks! |
Thanks you so mutch !! |
Let's keep this bug open. App should better behave in future on such api updates. |
I've tried to install the apk but am getting 'app not installed' at the end? |
@blinkertoon you must uninstall older version before install the new one. The github version cannot be installed over Google Play version or F-Droid version. |
Ok, thanks. Will try again. |
Hello! Is there any news for a new build on Google Play? |
Not in the nearest future. Still missing:
|
OK thanks, I'll work around it then 😄 |
Related Issue: #79 |
Also have this problem on my Android phone (Pixel 3 stock) running the Google Play Store version which looks to be currently 2.5.0, so no surprise. Hadn't really noticed since I generally just use Ultrasonic to sync my music from my Airsonic server (unRAID docker by binhex), but usually use Google Play Music for actual playback since it integrates with stuff better like Android Auto, Maps, etc. But I popped it open to grab some more files and am getting the same error as on @nate2014jatc screenshot. Waiting for fix on Play Store as I like to stick to that if at all possible! Thanks for you work! |
So I am setting up a new device and since the Play Store version doesn't work I had no choice but to grab the latest apk from github (v2.6.1 appears to still be it, as linked above) and I tried using that. I'm still getting the same errors as in the screenshot above when trying to setup my server and connect - Network Error Occured... Luckily on my old device I still had most of my music downloaded for offline use and so I could just listen to it using the Play Music app even though Ultrasonic didn't work, but on my new device now I obviously can't even get it to start up so I can download my music/playlists. Has there been any progress on a fix? Even better a fix that can be published to the Play Store? I'm using it with Airsonic 10.3.1-RELEASE (not entirely sure what Subsonic that is based on) running on unRAID docker container. |
Interesting development... I got the upgrade to Android 10 today on my Pixel 3 (running bone stock, no bootloader/root/rom/etc) and I was poking through apps to see if anything broke with the new OS version and came to Ultrasonic. I decided to fire it up on a whim expecting the same as above (I am running the Play Store version 2.5.0) and it gave me a warning about possibly not working due to new OS etc. An aside - my Ultrasonic is basically a new install as I deleted all of its data a couple months back in an attempt to get it work, which failed at the time of course. Since it is a clean install I've never been able to add a working server due to the above error, but I went through the process and put in the info for my Airsonic server (docker container running in unRAID, version on the about page shows "10.4.0-RELEASE – July 13, 2019"). I got the error above like normal and was about to give up and continue on but changed one thing before I did. It was failing with the above error in this thread when I used server address of http://192.168.0.10:4040/ but if I removed the trailing slash and used http://192.168.0.10:4040 it started working! I've started setting it up again and it seems to be continuing to work. I'm able to playback songs and have pinned a playlist which downloaded all the songs in it for me. Don't know what the difference is or why it works in Android 10 but had stopped working in the previous Android version, but I'll take it! As far as I can see the app hasn't been updated in over a year, so doesn't seem like a new version of that being the fix, something in the OS. |
Hello there ! I got the same error message on 2.6.2 with a 0.19.0 funkwhale. |
Yeah if you don't read the manual
|
Just to add my experience to it: |
Problem description
Since the last update of subsonic (6.1.4) ultrasonic can't connect to the serveur. i tryed with others app and it's work fine.
System information
The text was updated successfully, but these errors were encountered: