Welcome to the official Pokémon Forums!

Click here to review our official Rules & Guidelines.

After todays update wasn't able to complete the daily quest "put 4 Pokémon V in play"

13

Comments

  • Infernomaker1
    Infernomaker1 Member Posts: 64 ✭✭✭
    100 Likes 25 Agrees 10 Comments 5 LOLs
    #22

    Same problem.

  • TechHog
    TechHog Member Posts: 2,901 ✭✭✭✭✭
    5,000 Likes 5,000 Agrees 2,500 LOLs 2500 Comments
    #23
    https://community.pokemon.com/en-us/discussion/comment/6284#Comment_6284

    There wasn't an update yesterday. Just server maintenance. This probably needs an actual client update, which probably won't happen for another 2 weeks.

  • tylercorsair
    tylercorsair Member Posts: 1 ✭
    Photogenic First Comment
    #24

    I am still experiencing this issue as of yesterday; hoping a game update will resolve it! This definitely results in a less enjoyable experience, especially when trying to complete the Battle Pass.

  • Hauek
    Hauek Member Posts: 3 ✭
    5 Likes First Comment
    #26

    Latest update didn't fix this, at least for me. Tried to complete the quest several times and then finally changed it.

  • TechHog
    TechHog Member Posts: 2,901 ✭✭✭✭✭
    5,000 Likes 5,000 Agrees 2,500 LOLs 2500 Comments
    #27
    https://community.pokemon.com/en-us/discussion/comment/6329#Comment_6329

    There hasn't been an update since the one that caused this.

  • flufnstuf
    flufnstuf Member Posts: 1 ✭
    First Comment
    #28

    Yup, same boat here. Other bugs I got today:

    -Changed my avatar from wearing glasses to sunglasses

    -card drawn backwards. like i had the Pokemon logo on my bench and had to click it to see what it was. Probably should have screenshot that.

  • EpicSaladu
    EpicSaladu Member Posts: 4 ✭
    5 Likes First Comment Photogenic
    #29

    Same, happens also to : "put 2 pokemon V into play".

    They should fix this asap...

  • DoubleCure
    DoubleCure Member Posts: 2,507 ✭✭✭✭✭
    2,500 Likes 2,500 Agrees 1,000 LOLs 100 Answers
    #31

    @Geeodorah not really, the bug still occurs after the latest 1.4.0 update.

Categories