Regarding being on edge — you and me both. Sympathies. I apologize if my frivolous speculation is making you more tense; I’ll cut it out.
As stated, easily sideloaded. And the current jailbreak detection is pretty easily bypassed as well. ( not jailbroken as I’m currently locked out of the intel map :/ )
They’re a welcome distraction. It’s not like this thread is going to have this issue sorted when niantic chooses to remain absent.
Someone even disagreed with that post, funny enough.
same here iOS 14.0 then 14.0.1 now. Many copy past as answer to my appeals from niantic...
Greetings and salutations. Have a seat.
14.0.1, but yeah, me too. Updated as it fixes the widgets.
I got so frustrated about this I started to take it out on my family. Left all ingress chats and trying to take a break. Still hoping for the appeal, but not counting on anything.
Well, it’s a matter of perspective. First of all, it’s just a “strike”. Basically even if it was at all warranted, you’d need two more to have your account terminated.
Second, hang in there man. Calm down, in the end it’s just a game. It’s not like you are not able to play the game at all. I’m sure it’ll get sorted out at some point.
i know the feeling of how frustrating this is. It's pretty upsetting when you poured so much time into a game and played it fairly. The game was really slow before the quarantine/lock down and now it's slow to the point where i generally was losing interest in the game. This lack of transparency and coming up IFS, this is pretty frustrating. IFS normally has puzzle with intel? not that i much good at it, i still tired to help.
There were multiple, moving pieces related to our efforts to address abuse that happened at or around the same time, and I hear you that it has been frustrating without quick and clear communication. It took time for us to investigate what happened and why, and I prioritized trying to get that info and identify a resolution path. I'll do my best to confirm that we let Agents know we're aware and investigating high-priority issues more promptly in the future.
Additionally, I'll try and clarify our messaging from yesterday, posted here:
In one group, some Agents incorrectly received a first strike on their accounts. Not every Agent who updated to iOS 14 was affected; however, this did affect Agents on iOS 14. We have since identified what happened, this strike has been cleared, and as of yesterday those Agents should be able to use both the Ingress app and Intel Map.
In another group, some Agents also received a first strike, and upon review these first strikes remain, but the warning message that should be displayed when starting the Ingress app isn't currently showing on Ingress 2.55.1. Because of this, these Agents can't review or accept the warning message, shown as part of the three-strike policy. The fix to display this warning message to Agents who've received a first strike should be coming in the next Ingress update, 2.56.2, which we're targeting to begin rolling out next week.
What was the cause for the strike that stands?
My three year anniversary is coming up I believe. Have recursed twice and L15 again. I’ve poured so much time and energy in this game...
Can’t even get a humane conversation. It’s just bots and email templates, they created these forums and then refuse to use them as a way to communicate with their users. If not themselves, through vanguards, moderators; anything.
Well then I for one am very curious as to what the reason will be when the actual message is displayed. If no more information will be given; how can we prevent it in the future? I for one am clueless as to what I would have done to “cheat”.
I’ve been trying to have a conversation in the appeal, but that is just a wall. Will we get more details displayed in the message? Because I’ve never used modified software, and I have protected my gmail with two factor authentication.
Several other people I know have this same infraction apparently and they are clueless as to what is going on and why as well.
Though there is still a lack of clarity surrounding this topic, I very much appreciate your post and opening this communication :)
I have played and lived with ingress for more than 7 years. (I recently celebrated 7 years as L8 agent)
It's not just a game for me.. I think I deserve more than a strike without ever knowing how to avoid getting another one. I'm totally clueless about what I might have done to trigger a strike.
Agent can update to IOS 14 when Prime 2.56 relese without strike and run Prime and intel normal? Way Prime 2.55 get no access to Intel Map? All agents with the Prime bug get 1 real strike on accout or they can ignore it and only see strike message with 2.56 and never get strike on account?
So in addition to being ineffective in terms of communication you are ineffective in terms of development. Players impacted for a reason that everyone ignores will have to kindly wait for an application update in order to validate a warning and thus hope to recover the intel Map. This means that players at the time the update will be available will have already been blocked for more than a week minimum. You make a penalty reduction to take into account your bugs? Finally, do you realize that you are slowly killing a community that makes your game live?
if you are going to sanction users. You need to specify exactly what they did wrong. What 3rd party software was being used, user was caught spoofing, whatever, it is, there needs to be SPECIFIC information. Not a general “stop cheating”.
Strike for nothing? You’re pathetic ****.
@NianticBrian - I can chat in COMM now, but I still get the suspended message in intel. Clearly something is still broken. I should not have a strike against me -- I know this for a fact, I do not use any weird software or anything non-vanilla. This tells me that you guys still have something broken in your workflow, even if you are trying to punish some cheaters. I'm incandescent with annoyance over this because I have reported actual cheaters for years here in Phoenix to deaf ears. Several have their cheating software running right now capturing and linking as I type this. I am only assuming I still have a "strike" against me because intel isn't working (although it is odd that I can chat in COMM now). If I do, I find it completely insulting that I do because I DON'T CHEAT.
(Sorry for all of the bold. I am just at my wits end with these communication issues).
sorry, you haven't fixed it. I'm still banned from intel (but not from comms now) and I haven't ever cheated. I am on iOS 14. Im not going to accept a first strike because I haven't done anything wrong.
Just wait like 2 or 3 days and there will maybe be an announcement posted somewhere about what might have happened. Kind of like the clarity we were told we might get on the erroneous bans a week or two ago.
@NianticBrian Agents get real strike on accout or Niantic never get real strike when Niantic do wrong with Prime not agets?
I'm guessing people that had the COMMS ban lifted had the strike removed, even if the intel ban is still in place. The intel ban remaining sounds like another bug.
In the "3 Strikes Policy" it states the following (posted below). It appears that the COMM ban is part of the Strike 1 discipline, so if the strike is removed, COMM access should be restored, which is what I'm seeing many cases of.
Strike 1: Warning
If this strike is issued, you will see a warning message in the Ingress app informing you that we have detected a violation on your account. You must acknowledge this warning in the Scanner each time you access Ingress before you can continue playing Ingress. This warning will also prevent you from communicating with other Agents via COMM during this period.
This will last for approximately 7 days. After this period, your gameplay experience and access to COMM will be fully restored. Any further violations will result in additional escalated punishments. You will not receive another warning.
@NianticBrian can you please check with the team if a lift of comm ban also should have removed intel-ban but something went wrong?
@NianticBrian If this is the case, please let us know ASAP! Please don't wait 3 days for the team to fix it before telling us anything. #BetterCommunication
Like many others in this thread and elsewhere, I have not cheated, yet I'm still locked out of Intel and your message implies that I will be given a strike for nothing more than using the latest iOS version after you said it was compatible. Your timeline indicates that I will probably be unable to properly take part in FS October.
This is not the behaviour of a competent games company.
Your continual insistence despite all evidence to the contrary that Niantic is right and Niantic's customers are wrong, when Niantic has an international reputation for laughable QA, in this case and with the false ratings drops in Wayfarer is ridiculous.
You would do well to remember that your EU customers have the right under the GDPR to demand human reviews of automated decisions that adversely affect them, to see copies of data and the reasoning that led to those decisions and that we have the right to sue over defamatory statements about us made by your company.
Yeah, I waited on purpose with installing ios 14 to make sure everything was cool with ingress first. (Based on previous upgrades I knew being first was a bad idea) So after your message I did the upgrade and still i got a strike, seriously ****.
I've asked our team to investigate why Agents are able to access COMM but still unable to access Intel Map, and we'll report back when we have more info.
That’s all i wanna hear, i don’t cheat, its impossible on ios
i also also appreciate the message, even if it’s a lot late.
y’all still need to work on that. And I don’t ever expect you to give specifics on why some have been justly banished from the game. I get it. It makes sense
but when there is a clear indication of no wrongdoing you need to eat all your words and just admit ya **** up. M’kay? Hint: this is one of those times. Y’all **** up, left everyone hanging, sent a watered down ooops that was confusing as hell, in multiple places and sent the agents wongly banned and correctly reinstated another confused email.
it was pretty clear from the get go this was nothing of their making.