Joined
·
2,537 Posts
Has anyone figured out the exact cause of this yet? For me it seems like sometimes it happens and sometimes it doesn't. Haven't been able to figure out why. It seems like somebody out there must know the answer by now.
Destinations 2 to 0 after 1 use. Cause?
1 - 20 of 29 Posts
Joined
·
2,537 Posts
I know that's not correct. There have been many times that I've got many trips on one filter none of which got me close to the destination. And yet those times the problem didn't happen.
I left downtown w filter on ohare
7 rides later it timed out in oak pk....
Joined
·
2,537 Posts
That sucks but it's not the same issue.
5 of them still had me downtown and
it timed out on the last 1 in Garfield pk
I've never been totally stiffed out of 1
like you are saying
Joined
·
687 Posts
It deletes destinations after selfie check also.
A driver will have two, after a long trip will now have three, you enter a destination, it asks for a selfie and then you have none.
Most annoying, send a bug report via the app. Help - account and app issues - common phone and app issues - feedback about the app.
Describe the actions and events clearly and accurately so they can reproduce the problem.
A driver will have two, after a long trip will now have three, you enter a destination, it asks for a selfie and then you have none.
Most annoying, send a bug report via the app. Help - account and app issues - common phone and app issues - feedback about the app.
Describe the actions and events clearly and accurately so they can reproduce the problem.
Joined
·
2,537 Posts
Seriously never? This has been pretty rampant ever since Uber patched the unlimited DF hack a few months ago. There have been lots of reports on UP.net from different markets including Chicago.
How often do you mess with the "arrive by" time? I'm beginning to think it might have something to do with that.
What version of the driver app are you using?
Joined
·
12,413 Posts
If I do a few rides on #1 it's a new thing its steals my last filter
Oh ya mine times out . But no filter left
Joined
·
2,537 Posts
Yes that's the issue I'm talking about... but it doesn't always happen "after a few rides" on the first filter. In fact sometimes I've done quite a bit more than a few on 1 filter without it happening.
Could it really just be random? Come on... someone has to have the answer.
@bobby747 how often do you mess with the DF's "arrive by" setting? What version of the driver app are you using?
Joined
·
2,537 Posts
You can always roll back to practically any version you want.
Are you saying you're using the latest version of the app (thus unable to adjust arrive by) and still it steals your second filter?
Joined
·
1,814 Posts
Since early July? Never because it's nearly useless.
Joined
·
1,814 Posts
And then ignore it anyway because it doesn't adversely impact top line revenue.
Joined
·
2,537 Posts
Why do you say it's useless?
Joined
·
1,814 Posts
Nearly useless because of the inability to edit arrival time, whether it's adding a time, reducing the time, or extending the time.
Joined
·
2,537 Posts
That is easily solved.
You can remove the destination, then immediately set it again with a new time. Double-check that it's now actually showing the new time; I find I have to repeat the process about 50% of the time.
I haven't figured out what combination of number of times you change it and number of rides you get causes the filter to eventually be burned.
1 - 20 of 29 Posts
Join the discussion
