PokemonGoF
IMPORTANT: Bot warning with this bot. Red message in app
IMPORTANT! It seems that almost all of our bot accounts got flagged with the red warning. So stop using the bot. We must investigate the cause.
I suspect that it is caused by the inbox is not cleared. When i open app, i get very old messages being displayed. I suspect this causes the bot warning now. We need to fix this asap!
On my account that i use daily on my phone in combination with the app, no red warning is there.
@Davidakachaos take a look when you are able to. This bot not receiving inbox messages the way it should.
I'll also take a look later.
I am able to replicate this issue. As another update, if its not wiped after a day, it triggers a niantic warning.
Temporary solution for those who are still safe: login phone to clear inbox, disable gym slot
Init.py Line 1532, change request.get_inbox() to request.get_inbox(is_history=True)
I need someone with multiple accounts that hasn't got the warning or didn't bot since we update to version 0.69.1 to test this. One acct with the above change, one without and let us know what happen to them
I don't have time, i'll paste the response here and hopefully someone can figure this out asap
[{'notification_id': u'GYM_REMOVAL_aa47efe6d5004151b77e16f6bb0368e2.16',
'category': u'gym_removal', 'variables': [{'literal': u'aa47efe6d5004151b77e16f6bb0368e2.16', 'name': u'GYM_ID'}, {'literal': u'Shangri la Phoenix', 'name': u'GYM_NAME'}, {'literal': u'10901816661029224455', 'name': u'POKEMON_ID'},
{'lookup_table': u'pokemon', 'name': u'POKEDEX_ENTRY_NUMBER', 'key': u'131'},
{'name': u'POKEMON_DISPLAY', 'byte_value': '\x10\x02'},
{'literal': u'GYM_BADGE_VANILLA', 'name': u'GYM_BADGE_RANK'}, {'literal': u'http://lh5.ggpht.com/HOLIHu6SKCDB45sW4e-Y0SLPO4owOk4RK27xirKax3O6AK9WcI9ltWJcosDA-CY6Y2sTWXAsB0lxZKBtIICq', 'name': u'GYM_BADGE_IMAGE_URL'}, {'literal': u'false', 'name': u'GYM_BADGE_LEVEL_UP'},
{'literal': u'127', 'name': u'GYM_BADGE_EARNED_POINTS'}, {'literal': u'0.454', 'name': u'GYM_BADGE_PROGRESS'}, {'literal': u'12', 'name': u'POKECOIN_AWARDED'},
{'literal': u'0', 'name': u'POKECOIN_AWARDED_TODAY'}, {'literal': u'50', 'name': u'MAX_DAILY_POKECOIN'}, {'literal': u'0', 'name': u'BATTLES_WON'}, {'literal': u'3', 'name': u'BATTLES_LOST'}, {'literal': u'0', 'name': u'DEPLOYED_MILLIS'}],
'labels': [1, 3], 'create_timestamp_ms': 1500532796709L, 'title_key': u'gym_removal_notification_toast'},
label UNREAD = 1; NEW = 2; IMMEDIATE = 3;
Server will always return as UNREAD. Read to figure out how to inform the server that message is read. It might be something new in 0.69.1
As a better solution, might be better to disable gym until its resolved, and pass it along to Dev Repo.
@VoIP likely not gym or inbox issue. Mappers who don't gym are hit too.
Likely to be 0.69.1 api issue.
Could it be with the buddy pokemon? I will log on and get Magikarp found a candy +26 magikarp candies
Today sucks!
Was playing around with optimiser as transfer wasn't working on my usual config, something went wrong and lost a ton of good mons (Unown & Moltres included) AND got the warning message, where is that cry smiley!
Well my phone account also received the warning. So it is not caused by inbox!
I don't know if this is helpful, but my gf who stopped botting 2 weeks ago did not receive a warning. I went on till i read this right now, checked it and I did get the warning.
@thelemonenergy, so your girlfriend is safe since she did not bot two weeks ago? If that is the case, definately something has changed in 0.69.1 that allows detection. Did she used gym slotting two weeks ago?
She did not use any gym features. (Luckily I configured her bot so i know most of the config) I think the 0.69.1 was released earlier than 2 weeks ago, but the gym slotting was not in the master branch by then.
Where can i see when exactly she botted the last time?
Guys, stay clam. This is not the first time (and definitely won't be the last). When. This happen stay clam, keep playing (as in please be good boy and girl, stop bot) until warning disappear. By then, we should have figured out what causes the flag and we will be back botting in no time. :)
We have all the warning in bot to keep you safe. As long as you follow those warning, no cause for worry.
But as usually, please remember i recommended not to use your main account for botting.
Oh, ok sorry, i kind of mixed that up. I will look in the event file of the webinterface and tell you all i can see about the date and version. Will do as soon as I have access to her pc.
Appears its a common issue in the Dev Pogo spot. Most likely there its something with the encryption.
@VoIP yup this is the 2nd time it happened.... The last time it happened, it takes almost a month before they say, ya, if you don't want to see the warning, please do this and that ... Hopefully this time round they will be faster....
@MerlionRock and possibly hope we get a "compensated" for the issues.. but I highly doubt that will happen (even if you are doing mapping).
Any update on this yet?
Is #re-research on discord the best place to follow for updates, tried to keep up but get lost quite quickly
@camnomis still not stable. #re-research is still looking into it, but there might be a fix in one of the node.js api's.
We've implemented the fix from node.js - Please test this by using this API, and report your results: https://github.com/goedzo/pgoapi/tree/Test-AntiBan-2
Using your fix @goedzo and so far so good (spun up a brand new account to test it on)
Im running it too with no errors on the account so far so for me it's a pass
On Sun, Aug 13, 2017 at 11:16 AM goedzo [email protected] wrote:
Ok cool @camnomis https://github.com/camnomis keep us posted!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/PokemonGoF/PokemonGo-Bot/issues/6198#issuecomment-322048031, or mute the thread https://github.com/notifications/unsubscribe-auth/AC6OX6cxcbONpIGTF-vUwAOu3HtCRN4Jks5sXxNWgaJpZM4Oukzs .
as soon as i got this warning i created a new account and put it on the bot it took 4 days for the warning to show up.