Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
[Solved] App got a wrong date on a trip
I don't know how this happened.
Assuming you have not removed that Outing from your Mobile App, please
- Open the App
- Choose Completed Outings
- Click the "eye" icon next to this outing; This opens it in Checklist view.
- Choose "Finish Outing" from the dropdown menu
- Email the Outing to me at firstname.lastname@example.org
Then I will get a copy of that import file to look at.
Or if you haven't deleted the CSV file from your PC, you can simply mail that to me from your PC. Either or both would be good.
I have done that.
Whoops, I sent you the wrong one. Now have sent the right one, from 8/14. And I just noticed I have two trips like that. From 8/14 and 8/16.
I have not received any emails from you. Please check the address you used and resend.
Sent again. TThis time forwarded from email. For some reason, even though I typed your address into the app, it still sent the email to me. Even though I blanked out my address.
There are two problem outings. The one for 8/14 seems clean to me, but on the 8/20, I added a comment near the bottom on the temperature. 69 degrees. Interesting that it decided to use a 12/31/69 date.
(As I have said elsewhere, I was afraid adding any comments to the email would mess BD up.)
There does seem to be a problem with the Trip Start/End Date/Times.
I imported your 20-AUG sightings and got a trip start date of 19-AUG-2020 9:47pm for some reason.
I will get this fixed. But need some time on this one as working heavily on getting v5.2 of BD Desktop out the door.
I will leave this topic unsolved until I get it fixed.
Also, just to note, that the problem is in the Trip Dates generated by the Mobile App. The CSV file that is imported has the wrong dates. This is not a problem with BD Desktop. fyi
Have you seen this one again since August? I can't reproduce this and don't see a problem.
I did correct the issue where we are sending a time along with the date to BD Desktop on import.
I am going to mark as Solved. But if you can reproduce this or have seen it again since August, please let me know.
No, I have not seen this lately.