Any one has problem updating the App using Testflight?
Recently, I always got an error in Testflight of “Couldn’t load App. This build is no longer available.” when I clicked the link in the update email. I tried different versions of builds, none of them worked.
Any idea?
When you open the TestFlight app and select Everdo app, which version and the expiration date do you see?
Great feedback, thank you!
When I open Testflight, it simply says “No apps available to test”. I received the invitation link of the very first version of Everdo App. I don’t know what happened but it disappeared now. I tried using the very beginning invitation link as well as the recent links for updates. None of them works.
One thing is, I installed another app using Testflight. Did that matter?
Thanks!
In today’s update many changes were implemented to reduce lag, improve scrolling performance, swipe gestures, and overall reduce glitches in the UI.
The result looks good so far, but it’s possible that some things might have been broken along the way 
Please report if that’s the case.
@Mai, your point’s haven’t been addressed yet.
Is the Archive module working properly or it is not finished?
Sometimes when I finished my tasks they aren’t listed in the Archive list. The other time they are. Of course, I archived them.
In the Desktop app I can see all archived items.
I will see what’s going on. Maybe some specific kind of items is being filtered out? Or is it random?
The ones I recognized were Waiting items. But it is not a rule because other waitings are in the Archive list. It looks like a random behavior.
When we edit an item and switch the list or project from left side panel then edited item is still open. Is it conscious or unexpected behavior?
2.
When we have a long task title and we want to change the first word then it is a pain to scroll to the beginning
3.
Items on the Waiting list doesn’t save contact info.
4.
please look what a strange font is used to present due days or time tag. This is on iPhone XS with iOS 13.
Thank you for your report. I’ll make sure it’s addressed.
This should be fixed now. The Archive was not being ordered correctly.
It works fine. Thanks
I noticed today that marking as done or trashing an action scheduled to start in the future makes the app crash for me.
As usual, steps on how you may be able to reproduce the crash:
Another ‘issue’ I came across: it’s possible to remove the start date from a scheduled action, and when you do so the action remains in the ‘Scheduled’ list, showing a repeating date that doesn’t exist (I didn’t set it to repeat) until you restart the app. Once you restart, it’s possible to search for the action by name, but the action doesn’t show in the ‘Scheduled’ neither ‘Next’ lists.
Thank you for reporting, this is very helpful!
Is the ability to show/hide (collapse) task notes on the list of features to be added?
I see it was requested and added to the Android app back in Dec 18.
If I have tasks with long checklists it’s easy to hide them on desktop by simply collapsing, but on mobile it increases scrolling somewhat.
Hi,
there is a strange behavior with the Waiting list.
One or two updates ago I reported that the iOS app doesn’t show assigned contact to the waiting items.
Now when I add a new item using the Desktop or iOS app then the contact is assigned correctly but all items which were created before don’t show assigned contact in the iOS app.
If I remember correctly, there was a bug that prevented the contact data from syncing correctly between the iOS app and the sync server. This is why some items on iOS might have no contact assigned. To fix these out-of-sync items, you can either re-assign the contact, or perform a pull in sync settings.
Hi,
thanks, now it’s working.
There is one more issue.
When we use a context tag(with @) then it shows only items from the Next list. Items with chosen context but from the Waiting list are missed.
Basically, it is logical. When we wait for something, there is no context but in the Desktop app all items are shown.
Not sure if this is what you mean, but I just noticed that the “Waiting” section is indeed missing when using context-based navigation items. This is a bug.
Yes this is exactly what I was thinking about
