Skip to content
This repository has been archived by the owner on Aug 17, 2020. It is now read-only.

Pokemon caught problem #27

Closed
Tourniquet88 opened this issue Jul 31, 2016 · 4 comments
Closed

Pokemon caught problem #27

Tourniquet88 opened this issue Jul 31, 2016 · 4 comments
Assignees
Labels

Comments

@Tourniquet88
Copy link

So I just cought a Pokemon. It then disappeared from the map, but since then it will reappear every like 20 seconds then the phone vibrates and then its gone again. That happend in an endless loop.

Its there for a shorttime, the phone vibrates and then its gone. Also the Pokemon displayed in the right bottom bar disappear there too.

Another Problem I guess is, when I caught the Pokemon and restart the app, I can catch the Pokemon again at the same place.

@JFouts
Copy link

JFouts commented Jul 31, 2016

This is happening because there is a new timer created every time the GameManagerViewModel is initialized. Basically every time you view a new screen and then go back to the map. It needs to track the timer that it has already created for refreshing the map rather than making a new one.
If two timers try to refresh the map too soon after one another the second timer will result in the map being cleared.

@ST-Apps
Copy link
Owner

ST-Apps commented Jul 31, 2016

@JFouts isn't this related to #41 which we solved before?

@ST-Apps ST-Apps added the bug label Jul 31, 2016
@ST-Apps ST-Apps added this to the PoGo-UWP 1.1.0 milestone Jul 31, 2016
@ST-Apps ST-Apps self-assigned this Jul 31, 2016
@JFouts
Copy link

JFouts commented Aug 1, 2016

Yes it is. This should be fixed completely after #15 is pulled.

@ST-Apps
Copy link
Owner

ST-Apps commented Aug 1, 2016

Please try v1.0.7-beta to see if the bug is gone.

@ST-Apps ST-Apps closed this as completed Aug 3, 2016
ST-Apps pushed a commit that referenced this issue Aug 19, 2016
Repos update from ST-Apps
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants