![]() ![]() ![]() ![]() |
|
Today at lunch I dropped my phone which was enough to crack the screen.
Still useable, but annoying as it means I will probably have to purchase another phone as I leave for Japan soon and repairing my take too long (never used one of those phone screen repair places)
Oh, no! You'll definitely need a fully functioning one for Japan - so many Pokestops and gyms!
Geek girl. Freelance copywriter and editor at Unmistakable.co.nz.
Installed the newest update yesterday via APK; raids are now broken completely - laggy, unresponsive messes
However they have actually managed to fix some of the outstanding issues introduced in earlier upgrades and it "feels" as if my PoGo Plus is actually more responsive (to Pokemon, PokeStops are another story)
As a result, I don't want to downgrade to the older version.
There's a lot of people on Silph Road reporting the same issue with raids. Niantic will need to release another update at this rate, or nobody will be able to get Mewtwo. I've just got my iPhone back from the shop, with a new battery installed, so I am raring to go. Not sure if I want to install the new update, or whether iOS will even experience a similar issue. I suspect Niantic will force it before Mewtwo is released anyway, so I may not have much of a choice.
Geek girl. Freelance copywriter and editor at Unmistakable.co.nz.
I believe that the update was pulled from the Google Play store, which means that the Apple release would have also been pulled - given the 2-3 day gap between the releases
And in other news I purchased another phone yesterday - waiting for it to be delivered
Hopefully no issues with the PoGo Plus!
I saw that. To Niantic's credit, their Silph Road rep was onto it pretty quickly and took the details from a bunch of affected players so they could troubleshoot. It would have been disastrous to release Mewtwo with unplayable raids.
What kind of phone did you get? I've just got my iPhone 6S back from the iStore with a free replacement battery (whoop!) so I've treated it to a new glass screen protector (they took the old one off during the repair) and a new case. So it feels like new :) My son wants to get another Articuno before the birds leave. He's got plenty but none with 90+ IV's - unlike Moltres where he caught two 98 IV specimens back-to-back. So I guess I'm raiding for that this weekend, lol. I really want another Lapras, too. All my raid ones fled, and my only decent IV is an 82% I hatched last year.
Geek girl. Freelance copywriter and editor at Unmistakable.co.nz.
Purchased an LG G6 (parallel import); slightly concerned that the increased screen resolution will cause problems but I'll cross that issue if it happens
Hopefully something is done soon about "network issues" happening on gyms that have "recently" (not sure how recently is recently - I've had issues 12 hours later) that causes regular gym battles to be unplayable, which then causes the rest of the game to be unplayable
Since the end of the last event (feels like it was a few months ago now), I've been saving my stardust (had roughly 1 million, aiming for 1.5 million) to do some powerups
Today I finally got to 1.5 million and so can now spent the dust - with dust being semi limited however I need to be smart about it, so will have to create a spreadsheet and evaluate.
Some of the original targets (evolved egg hatches that I want to get from Level 20 to Level 30) are probably on the chopping block as they have no purpose in the game ..
Geek girl. Freelance copywriter and editor at Unmistakable.co.nz.
I did the spreadsheet last night and decided while it might be nice to have at least one of each evolved form at Level 30 (instead of Level 20), do I really want to use stardust on an Arbok, Primeape, Dugtrio, Marowak etc etc ... the answer was NO ...
As a result, my stardust plans consist of taking at least one Legendary from level 20 to level 30 and then taking a few of my level 30s to level 35 (depending on candy)
Anyone here received network errors on a normal gym battle after participating on a raid on that same gym in the hours before (talking up to 48 hours earlier)?
It has been heavily reported on TSR as an issue, and I emailed support on the matter. The customer service rep kept on referring to raids as the issue and even gave me some premium raid passes as compensation.
*sigh*
nzkiwiman:
Anyone here received network errors on a normal gym battle after participating on a raid on that same gym in the hours before (talking up to 48 hours earlier)?
It has been heavily reported on TSR as an issue, and I emailed support on the matter. The customer service rep kept on referring to raids as the issue and even gave me some premium raid passes as compensation.
*sigh*
Just got a series of network errors on a normal gym battle today. On a gym I haven't done a raid on in the last two weeks. Or possibly ever. Not sure on that one. There are two next to each other and I can't recall which one had the raid.
It didn't stop me beating it but it did some weird things to health levels of both sides.
Wouldn't really complain about bonus premium passes though.
nzkiwiman:
Anyone here received network errors on a normal gym battle after participating on a raid on that same gym in the hours before (talking up to 48 hours earlier)?
It has been heavily reported on TSR as an issue, and I emailed support on the matter. The customer service rep kept on referring to raids as the issue and even gave me some premium raid passes as compensation.
*sigh*
That's kind of hilarious considering people complaining about lost raid passes have struggled to get them refunded. I haven't run into the issue myself, but I know many people have. Let's hope the update announced today helps with that, along with the gym lag that caused the last one to get pulled from the Play store.
Some good QOL changes happened today, with the Go+ now able to spin gyms (it was in the update patch notes, but I can already do it without the update being available for iOS yet) and the "last ball glitch" being fixed. Someone at a raid I went to today caught Articuno with the actual last ball. The big one is being able to go into a raid lobby and scope things out without losing a pass - i think that one needs the update, though.
Wild rumours abound about Metwto being postponed and Gen3 launching on October 27th, but nothing from what I'd call a reputable source. I still think we'll get Mewtwo this coming weekend, if the new update fixes the other issues.
Geek girl. Freelance copywriter and editor at Unmistakable.co.nz.
When the first messages appeared that the Go Plus could now spin stops, the two gyms I can hit (with drift) from work did not allow the Plus to get items
I wondered if it was because they already had raids operating on them, because as soon as the raids ended, everything worked.
I wont complain that now I have to empty to bag even more time during the day ;-)
*refreshes APK Mirror*
Haha! Yeah, I am stoked that the plus spins gyms. I bought it exclusively to collect resources, because I live in a spawn-dense spot with few stops nearby, which leads to running out of Pokeballs while I'm at home. When a large number of gyms became stops, I lost some of my collecting power (I normally do it while driving by strapping the plus to my forefinger with a hair tie). My number of collectible stops was fewer than before. Now ALL the gyms are spinnable, even ones that were never Pokestops, my collecting ability is greatly enhanced. Now, if they'd just let us have more bag space...
Geek girl. Freelance copywriter and editor at Unmistakable.co.nz.
littleheaven:
Some good QOL changes happened today, with the Go+ now able to spin gyms (it was in the update patch notes, but I can already do it without the update being available for iOS yet) and the "last ball glitch" being fixed. Someone at a raid I went to today caught Articuno with the actual last ball. The big one is being able to go into a raid lobby and scope things out without losing a pass - i think that one needs the update, though.
I noticed my Go+ spinning gyms yesterday (I didn't get the update before it was pulled, so looks like this was a server-side change). A very nice addition!
|
![]() ![]() ![]() ![]() |