Cause the App Store gives different signals on this… in the end I have issues with this great (best) app but there’s no response from the mail address so I was wondering if the forum is the right place (the app support button in the App Store redirects to the forums so…)?
i noticed the developer is listed as Trakt, Inc now. I wonder if it’s owned by Trakt now. They possibly bought the app and aquired his services all in one swoop.
No it doesn’t. I have an issue where Watcht - and only Watcht - shows an show with thousands of unseen episodes. Official Trakt app is fine, TVST app is fine, Trakt web app is fine, Trakt website is fine. Watcht is broken. No answers, no support.
So with this fact plus the „recent“ changes around hide shows and drop shows I wonder if it is a good idea to not maintain an app anymore.
And the probable takeover is kind of intransparent, feels like killing a (way!) better app in favor of the own official one.
Anyway: how to fix those kind of issues and unimplemented API changes? How to get support, now that Trakt. Inc. is the new owner?
I think those issues you’re seeing, that are similar to something I am too with “watched” episodes not being completely accurate, are probably related to the database rebuilding they recently did. I do hope @Ohifriend keeps developing it.
In fact I’d love it if this became the future alternative for those of us who don’t like where the whole new “Lite” is going. The layout, design and functioning is just more logical imho.
Exactly. Watcht is perfect with the look and feel.
For me one (not dropped) show is 1.544 episodes behind… which is crap. Also I can provoke this behavior for new so far unwatched shows with one watched episode and then being dropped. Only Watcht has this issue.
As may or may not be clear, I spend 99.9% of my work time on the official app(s) and not much time on other projects (including Watcht). I do my best to reply to emails but it’s not my focus as Watcht is generally pretty stable outside of the recent changes with Hide and Where to Watch not working.
The other issue with weird Up next shows showing incorrect data is a known issue that is being looked into on the server side but as you can imagine the official apps are generally higher priority than Watcht which isn’t being actively worked on - hopefully there will be a fix sooner than later.
The main reason Watcht has this issue versus other apps is pretty much related to the implementation of Up next - everyone does something slightly different as the API back when Watcht was created (some 8 years ago or whatever) didn’t have some of the other options we do now, and just other implementation details (Watcht was literally a playground for me as a developer originally).
