kitencx / foursquared

Automatically exported from code.google.com/p/foursquared
Apache License 2.0
0 stars 0 forks source link

no points being reported #149

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Many people are reporting that they aren't getting points/seeing points when 
they check in. Please investigate.

Original issue reported on code.google.com by jlapenna on 27 Dec 2009 at 8:13

GoogleCodeExporter commented 9 years ago
I've looked the group - lots of people reporting this are on the old version
And from 4sq help :
We constantly tweak and tune the way points are dolled out. Here's the secret 
sauce:

You can only earn points at certain times:
We DON'T give points for normal-work-hour checkins (e.g. Mon -> Fri, 8am -> 4p)
We DO give points for midweek checkins AFTER 4pm. On weekends you get points 
All 
Day Long. (brunch!)

Original comment by avolo...@gmail.com on 27 Dec 2009 at 9:28

GoogleCodeExporter commented 9 years ago
err, the text there is wrong

we're slowly moving from "daytime"-only points to all day points

there's still something strange about point calculations on the scala backend; 
high
on our list right now to investigate. collecting as many data points as 
possible to
identify pattern of when it's awarding versus not

Original comment by naveen...@gmail.com on 28 Dec 2009 at 8:18

GoogleCodeExporter commented 9 years ago
This problem isn't limited to Android. Naveen, go ahead and pick apart my 
account (G.S.). I'm first-gen 
iPhone and basically off the grid ever since I loaded 1.4.3. All check ins 
equal nothing, while my wife 
Carly S. gathers up badges, mayorships, and points at the same venues at the 
same time on her iPhone 
3GS. I feel like I'm in Coach while she's sitting in First Class. And these 
points are coming before 4 p.m. 
Know what else is lovely? I'll add a venue for no points, and she'll check into 
it for 5+. Please get things 
working properly again soon. I'm traveling to multiple cities in January.

Original comment by gsax...@gmail.com on 29 Dec 2009 at 12:25

GoogleCodeExporter commented 9 years ago
yup, this was an api issue. it was fixed at some point yesterday and i've been
watching it since and it looks like it's behaving

let me know otherwise + close this ticket if confirmed

Original comment by naveen...@gmail.com on 30 Dec 2009 at 10:46