Crashing When capturing a pokemon

  • 20
    Posts
    8
    Years
    • Seen Sep 22, 2016
    Hello everyone! I like a lot of you have begun to play pokemon go this week. Finally today I've been able to get on for decent periods of time. But when I get into a pokemon battle, I always end up crashing. I was wondering if people knew a way to get around this (turn off camera/VR) or any ideas in general.
     
    Someone I know had the same problem. It's frustrating, but I don't know of any sure-fire fixes. You can only restart the game and hope the problem stops for now.

    For me, I had an issue where a gym wouldn't register my win against it, and upon restarting it was as though I'd forfeited the battle just before winning, meaning the Gym lost significantly less ratings, making my efforts for nought. I found no fix for that either, so for now you'll just have to live with the issues, and hope Niantic will fix them soon enough.
     
    OK, thank you was hoping at the very least I wasn't alone in having this problem.
     
    Mine crashes sometimes once I get a pok?mon in the ball. I don't know if it was captured or not until I reload. It makes me so nervous lol
     
    From what I've experienced, if you catch the Pokemon (get the little stars flying off after three shakes) then the game freezes, you SHOULD have caught the Pokemon, so it's ok to force quit on either OS (Android/iOS).

    Just to put you at ease.
     
    Hi mate! I get this problem when I'm on my 2G. But I realized that it's not an issue of internet. If you're using android, just clear cache for the Pokemon Go app. If you're on iPhone, enable LTE and then disable it again. I don't know if the iPhone thing works, but android trick worked for me. I found it here. Pokemon Go Freezes After Catching Pokemon
     
    I have also had this problem several times but not always. I just log out of the app and come back on. I have yet to lose the Pokemon I have captured though. When I come back on the newly captured Pokemon is on my list.
     
    Hi Gocubsgo,
    I have the same problem, and I can confirm that it is due to AR. One time I just managed to get into a battle and turn off AR and it worked fine. Unfortunately, I currently have the same problem as you because the update turned AR back on :(
    You can either try and fluke it like me, block camera permission (Android 6.0) or try some other fixes. I'll let you know if I find anything.
     
    Back
    Top