i think further investigation how to deal with this should be done...
- previously i ran 4.5.beta2 and had no problems, now 4.5 and the android client has the problem
- search for the same term works via browser
- you can never guarantee to have a 100% issue free collection
-- the server seems to be ok with that, as the browser search works
-- the android app "does not understand", so my guess would be an issue there... the app should fail more gracefully... maybe just skip the results with char encoding issues.
-- well, or have the server clean up the result, to make it client-safe
EDIT: i have the latest android app, appstore says its version 3.2
EDIT2: i just now realized that there IS something in the logs, when a search fails:
- Code: Select all
[2011-09-14 11:39:14,072] WARN FileUtil - Failed to list children for /media/music/Incoming/xxx
... and that directory does not exist anymore!
EDIT3: did a manual rescan... the nonexisting directory still showed up when browsing and also when searching, causing the error on the phone.
what i did next:
- install 4.4 server
- that seems to have caused a db delete, so it rescanned
- after it was finished i used the same search term as before: success, with web and phone
- again installed 4.5, it seems there was no rescan; search: success, with web and phone
... bug with db updates/scanning in 4.5?