Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Favorite percentage wrong after posting log with favorite point #7782

Open
Lineflyer opened this issue Aug 13, 2019 · 4 comments
Open

Favorite percentage wrong after posting log with favorite point #7782

Lineflyer opened this issue Aug 13, 2019 · 4 comments
Labels
Bug Issues classified as a bug Google Play or Beta feedback Issues derived from Google Play reporting or beta user feedback

Comments

@Lineflyer
Copy link
Member

Lineflyer commented Aug 13, 2019

Describe the bug:
A user of the beta version contacted us with this screenshot:
grafik

It shows 133% favorite percentage.

To Reproduce:
Meanwhile the cache has new logs and the situation changes.
I asked the user to provide more details about when this happend, however I assume the following in this example:

  • The cache had § found logs and 3 favorite point (=100%)
  • He logged the cache and assigned a favorite point

Actual behavior/state after performing these steps:
The fav count is incremented c:geo internally but obviously the total find count is not updated c:geo internally. This would lead to 4 favorite point but still only 3 total finds (=133%)

Expected behavior/state after performing these steps:
The total find count should also be incremented c:geo internally once a user posts a log of type "Found it".

Version of c:geo used:
2019.08.01-RC

Is the problem reproducible:
Difficult to check

@okainov

@Lineflyer Lineflyer added Bug Issues classified as a bug Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility Google Play or Beta feedback Issues derived from Google Play reporting or beta user feedback labels Aug 13, 2019
@Lineflyer
Copy link
Member Author

I was able to reproduce this (and also another used contacted us with a proof).

Example:

  • Cache has 4 found logs and 4 favorite points. c:geo shows 100% favorite percentage.
  • Log this cache as found and award a favorite point

Result:
Directly after sending the log c:geo shows 5 favorite points and the percentage is 125%
Only after refreshing the cache the percentage is correct = 100% again

Conclusion:
When posting the log the amount of favorite points gets updated locally in the database but seemingly not the number of total finds. This is corrected by refresh as we parse the new number of total found logs in that case.
Fix would IMHO be to increase the number of total finds also locally if a found log is posted with c:geo.

In case of a high number of founds this problem is almost not noticeable as the difference is not so huge. But especially for a cache with a low number of finds this produces a large error.

@Lineflyer Lineflyer removed the Unverified Issue not yet confirmed/reproduced or feature requests not yet checked for plausibility label Dec 4, 2020
@bekuno
Copy link
Member

bekuno commented Dec 4, 2020

I would instead not update the local value. So it stays consistent to the cache update state.

@Lineflyer
Copy link
Member Author

Thats IMHO a bad idea because not teccie users expect to see a change after they gave a favorite point.

Years ago the log was not shown after sending it, only after refresh. That was also not what users expect.

@bekuno
Copy link
Member

bekuno commented Dec 5, 2020

Is there a reason that we do not refresh the cache automatic directly after the online log?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues classified as a bug Google Play or Beta feedback Issues derived from Google Play reporting or beta user feedback
Projects
None yet
Development

No branches or pull requests

2 participants