jackBonadies/SeekerAndroid

Schedule or force wishlist refresh

Opened this issue · 1 comments

My wishlist searches have been last searched about a week ago, which might be due to port forwarding issues or something, but could also be a bug.

I would request a feature to schedule or force Seeker to search all wishlist searches again

Hello, thanks for the feedback. This is definitely a bug. The way wishlists work is when you log in the central server gives you a wishlist interval, this interval is almost always 12 minutes (or 2 minutes for privileged users). I haven't ever seen it be anything else (though I assume the reason it is retrieved from the server is so that the server can change it under heavy load). Seeker will take this and automatically search 1 of the wishlist searches at each interval, round robin cycling through them. Port forwarding should have no effect in this case (other than fewer results).

I will have to investigate and see what could possibly be causing this bug. One thing I can think of is that, wishlist searches do not automatically reconnect to the server if the user is disconnected (which for mobile can happen if, say, you switch between wifi and mobile enough times - happens automatically on android depending on which is faster more stable), Seeker reports that you are logged in but you are not maintaining an active connection (I have been meaning to add a status indicator but the UI never looks quite right..). I would say (1) restart Seeker - go to the home page > options > Shutdown, restart, wait 12 minutes, if it does not search even then I would say its a bug and to please send over the diagnostic text file. (there is a feature on seeker (on the latest version) in settings "enable diagnostics" that will write everything out to a text file, which can be useful in troubleshooting). If it does work after restarting then I would say that its simply disconnected from the server, and I will improve seeker to check the connection status and reconnect. Either way, let me know, and thanks for reporting this bug.