Pokemon Go!

I'm getting that same network error again from last time... Got it last night as well. I've used my phones lte (cell c), 'n Mifi device (telkom hspa) and my tablet (Vodacom lte). All give the same issue. I'm gonna go ahead and say the issue is not my local network connection...
 
this is why I love PTA.
20 mins from work to the first raid.
start time was 16:30
at 16: 45 we were starting the next raid a few blocks away, that same crew then did another 4 raids in quick sucsession all before 18:00. I went home unfortunately.

Look, don't get me wrong, I work in the Sandton area and there are many gyms in 5 min to 10 min walks from each other, the problem is more with how they released the raids...ie making them way to common in general and this goes for all raids. And on top of that, they release legendaries as well, but failed again by making them way to common as well. Now we sit with a problem where we have a game that is "casual" by nature with a mostly casual player base, expecting them to become grinders. You can see niantic has attempted to correct the issue with the new entei/suicune/raikou release, in making them less common as well rotating them. But you sit in a situation where the casuals will play casually and the grinders are a bit fatigued and do not event want to bother with "common" raids such as snorlax or tyranitar.
Add to this the displacement of players in SA and you sit in a situation like what i had yesterday. I had to simply drive by a snorlax raid and two to three blocks further a tyranitar and entei raid right next to each other.
 
Look, don't get me wrong, I work in the Sandton area and there are many gyms in 5 min to 10 min walks from each other, the problem is more with how they released the raids...ie making them way to common in general and this goes for all raids. And on top of that, they release legendaries as well, but failed again by making them way to common as well. Now we sit with a problem where we have a game that is "casual" by nature with a mostly casual player base, expecting them to become grinders. You can see niantic has attempted to correct the issue with the new entei/suicune/raikou release, in making them less common as well rotating them. But you sit in a situation where the casuals will play casually and the grinders are a bit fatigued and do not event want to bother with "common" raids such as snorlax or tyranitar.
Add to this the displacement of players in SA and you sit in a situation like what i had yesterday. I had to simply drive by a snorlax raid and two to three blocks further a tyranitar and entei raid right next to each other.

we do mainly tier 5 raids, but Snorlax, ttar and lapras still get people. unless its in working hours we all put in the effort to make sure everyone in the group has something.

there was a dude who did not yet have a blastoise, a bunch of us drove to the moot to go help him take it down. (he caught it)

a situation like you had, the group we had yesterday would have done all of those raids, but communicated it in the group, and ajusted timing to suit everyone.

in the PTA group, teh hardcore grinders help the casuals. sure there might be someone who still has no ttar and is always keen but never mentions he does not have one, so people might not make the effort to drive to silver lakes....
 
Keep getting this stupid error. Tried 3 different networks and still the same issue. Do you have any idea how difficult it is to clear a gym with six mons inside, when you can only fight one at a time before getting this error and having to restart the game. And then obviously you have to beat each Mon 3 to 4 times before the gym is cleared... Fck that. I'm going home.
683001a4d1d6b96169d9ad94fd40dfe4.jpg
 
Keep getting this stupid error. Tried 3 different networks and still the same issue. Do you have any idea how difficult it is to clear a gym with six mons inside, when you can only fight one at a time before getting this error and having to restart the game. And then obviously you have to beat each Mon 3 to 4 times before the gym is cleared... Fck that. I'm going home.
683001a4d1d6b96169d9ad94fd40dfe4.jpg

From this general description
https://www.reddit.com/r/TheSilphRoad/comments/6xtd92/error_code_directory/
Sounds like some other error occurred first in your battle with the gym and then the application had a issue syncing the state of the gym.
In my experience when something like this happens i just walk away, restarting the app, waiting 10min does not work.
Rather better to keep your sanity and take another gym
 
From this general description
https://www.reddit.com/r/TheSilphRoad/comments/6xtd92/error_code_directory/
Sounds like some other error occurred first in your battle with the gym and then the application had a issue syncing the state of the gym.
In my experience when something like this happens i just walk away, restarting the app, waiting 10min does not work.
Rather better to keep your sanity and take another gym

+1 same here.
if I get any error I just walk away.

but also SykomantiS have you updated to the latest version of the app?
 
I have. Although, I wonder if this might be due to the fact that my Nexus is running Android Oreo. It might be an issue related to that. None of my other apps are showing any sort of bad behaviour including the other games
 
I have. Although, I wonder if this might be due to the fact that my Nexus is running Android Oreo. It might be an issue related to that. None of my other apps are showing any sort of bad behaviour including the other games

I doubt it.

but as has been said, if you get an error at a gym, just walk away, you wont be able to do anything there for a while.
and network errors, drifting out of the way, and the worst bug, the one where someone feeds a golden raz just as you finish beating the pokemon.
 
Managed to clean out that gym (mostly), the last remaining Mon, a magikarp, had 4cp left... Aaaaaand, a raid boss appeared and kicked me out before I could finish it...
 
I wonder if they will ever fix all the bugs in this game, as i find the more they fix the more bugs appear. Take for example the bug which I sometimes experience (less now), but its a bug where some network error or something happens while you are attempting a catch and just as it seems like you caught the mon, you go into this almost debug mode with arrows on the side as well as a infinite jumping ball. Sucks when that happens on a legendary raid, as it recently did with me and when you attempt to log back in and the raid is over.... :'(
Another strange bug that was new to me, was feeding a berry to a mon i just placed in a gym and feeding was fine, but when i attempted to exit this phase the berry kept on floating everywhere on screen, in the menus extra
 
so I am going to be in the greater Durban area from Sunday until next week Thursday.

other than Ushaka, and the 2 botanical gardens, any other places I should check out?
I want to go on a serious magicarp hunt, where is the best place for that?
 
Still having issues with my go plus. No amount of restarts is helping. Even tried Baxteen's way. Doesn't help really.
 
Still having issues with my go plus. No amount of restarts is helping. Even tried Baxteen's way. Doesn't help really.

have you tried changing the battery?


I have also found if your signal is weak and you are having trouble conneting or getting lots of "network error" or "error 2" your go plus will disconnect.

also remember, a go plus stays connected for an hour, then the game disconnects it. you can connect once after that, without needing to restart the phone, but after that you will need to restart the app.
 
It's not a signal issue. I get the same problem even when connected to my home WiFi. It might be battery related, I'll have to check that out.
Didn't know about the 1 hour connection thing, so thanks for that, will keep it in mind.
My issue though is connecting in the first place.

I have a second go plus, but it's completely unopened in its original packaging. The idea was to sell it, bit I'm wondering if I shouldn't break it out for testing purposes.

Edit to say, I have no issue detecting the go plus, in game or in the bt settings menu. The issue is just connecting after pairing.
 
Last edited:
It's not a signal issue. I get the same problem even when connected to my home WiFi. It might be battery related, I'll have to check that out.
Didn't know about the 1 hour connection thing, so thanks for that, will keep it in mind.
My issue though is connecting in the first place.

I have a second go plus, but it's completely unopened in its original packaging. The idea was to sell it, bit I'm wondering if I shouldn't break it out for testing purposes.

Edit to say, I have no issue detecting the go plus, in game or in the bt settings menu. The issue is just connecting after pairing.



hold on.

connecting after pairing?
try this. follow these steps exactly.

open pogo. eject go plus.
close pogo. go into bluetooth settings.
un-pair go plus (it should not show up, but if it does, we found a problem.)
turn off bluetooth on phone.
long press go plus until light stays blue.
long press until vibrate.
restart phone.

once restarted, open pogo (Bluetooth still off)
when pogo is open and running fine, turn on bluetooth. (best would be via drop down settings menu)

go into settings in pogo, go to go plus.

there should be no devices at all. if there is, eject, and restart this process.
only when you are sure there is no go plus connected, or paired to the phone do you click the button on the go plus.
the light on the plus should flash white.
now there should be a go plus icon in the game that you can connect to.


I suspect the reason for your struggles is your phone is pairing to the go plus before pogo is connecting, leading to some funny settings coming from the game.


if you connect at any time, remember, the go plus will vibrate within seconds of you telling the game to connect it. if it does not, and you find your plus has a green dot under settings, but no green dot on the home screen, that is what is happening.

force closing the game and retrying without shutting down solves that reconnect issue for me about 50% of the time.
 
Top
Sign up to the MyBroadband newsletter
X