Just happened again, it's the valentine 2016 event and then Gill with the Duff Gardens offer.
I would expect it will happen over and over to those of us hit by it once already until EA fixes it or we give up on the game completely and spend our time and money elsewhere. But given how many people play the game it probably doesn't matter to EA if every person who gets hit with this quits.
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
It didn't help me with the glitch. A rollback didn't help at all for me and they "fixed some bugged variables" but it all came back again.
No matter if they roll back your game or fix it properly by correcting the "bugged variables".....it only fixes your game AFTER being hit by the glitch. The only difference is the roll back you lose progress (and items / donuts /etc...) but the fixed variables simply continues where you are without any loss of items.
BUT either way, it only fixes what WAS broken.....not fixing what BROKE it. So even if your game was fixed properly by correcting the "bugged variables", you can still be hit with the glitch again.
I have had 9 roll backs and one legit fix by correcting the "bugged variables", and have been hit with it after both again (and again....and again.....and again.....and again....and again 7 more times.....)
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
I’ve heard a number of users “suggest” that this should theoretically help. I have yet to hear anyone provide any evidence in support of the idea.
I uninstalled and reinstalled and cleared the cache prior to my roll back. It took two weeks for the glitch to come back. Still waiting for my second roll back.
Not really an update but just spoken to EA help in the UK who said it's a known issue and was being looked at by the studio. He said it had been raised "in the last couple of days". He said he'd send me an email with some troubleshooting steps (I.e. uninstall and reinstall). If (when) that doesn't work I need to contact them again and ask for a roll back. I said I'd had three roll backs already and that the problems persist he said I may be better off waiting until an update is released with the fix.
So, like it say, nothing new really learnt other than it took less than 5 mins to call and they were willing to do a roll back. If I could be bothered doing this twice a week I might carry on but i think I'll wait and see if they can mend the game.
What update are you referring to? I’m playing iOS and have seen neither a store or in-app update. And I see no mention of a new update in General Discussion.
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
It works for as long as it lasts until you get the glitch again.
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
I’ve heard a number of users “suggest” that this should theoretically help. I have yet to hear anyone provide any evidence in support of the idea.
See the comments here https://tstoaddicts.com/2018/03/12/rollback-glitch/#comments from Ahtomcat.
Seems there is a way to rollback and refresh the game, however I just got off the phone with EA and they won't do rollbacks anymore. I was asked to just wait for the fix. Polite and patience ... Even suggesting I'm willing to try a rollback still didn't convince them to perform a rollback.
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
I’ve heard a number of users “suggest” that this should theoretically help. I have yet to hear anyone provide any evidence in support of the idea.
Thanks for posting the link. I hadn’t seen it before. But I have read similar ones and I find neither the logic or evidence particularly compelling. The poster in question argues that in order for a rollover to be effective one needs to clear the cache, etc., etc., and in support of this view offers into evidence the success of his own rollback. I would note in rebuttal that at the time I am writing this his rollback is all of one day old. We’ll see how long his luck holds. Also in rebuttal I would point to the fact that several users have stated that they have, in fact, followed the user-recommended cache deletion approach and their games nevertheless suffered re-glitching. As a final comment on this issue, I recall the first time I heard this theory presented on this forum — it was summarized by a user who suggested that it might prevent the re-glitching of rolledback games. Since that time this suggestion seems to have reified into fact.
Seems there is a way to rollback and refresh the game, however I just got off the phone with EA and they won't do rollbacks anymore. I was asked to just wait for the fix. Polite and patience ... Even suggesting I'm willing to try a rollback still didn't convince them to perform a rollback.
It seems as though EA Help is increasingly refusing to perform rollbacks. Perhaps because they see them as a waste of time? Or because too many users are requesting it? Who knows. But I personally find that policy troubling. Since EA still cannot fix this glitch in any sort of permanent way via patch/update, they ought to in the interim be willing to roll back games, even if rollbacks prove to be only a temporary band-aid.
Not only should we give a bad review on Google Play with an explanation, we should Tweet at EA about the issue too. The more methods we could get their attention the better.
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
I’ve heard a number of users “suggest” that this should theoretically help. I have yet to hear anyone provide any evidence in support of the idea.
Guys remember if you are being hit with this multiple times your device may be doing it. There's a set of values in the game that corrupt. But your game is saved to the cloud with those incorrect values saved. Once they roll you back your game is reset. But once you reload from your saved profile you overwrite the fix and re-infect yourself again. Once You do a roll back clear your cache and make sure your loading from new again and not overwriting the rollback
Have you uninstalled or cache wiped prior to the EA rollback? I heard this should help with recurring problems ... Even with this glitch. True? So far I have been unsuccessful getting a rollback from EA so I don't know if this works or not.
I’ve heard a number of users “suggest” that this should theoretically help. I have yet to hear anyone provide any evidence in support of the idea.
Guys remember if you are being hit with this multiple times your device may be doing it. There's a set of values in the game that corrupt. But your game is saved to the cloud with those incorrect values saved. Once they roll you back your game is reset. But once you reload from your saved profile you overwrite the fix and re-infect yourself again. Once You do a roll back clear your cache and make sure your loading from new again and not overwriting the rollback
Yes, I recall reading that (although I also recall seeing earlier posts of a similar nature dating back to last year). Of course, as far as I can tell from a surface reading of the post, this is all just assertion without any backing evidence. Yes, the idea has a certain face validity, but how does the poster know any of this is true? Is he a developer or has he been in contact with any members of development team who have passed along this advice. And if either of those things are true, why haven’t we heard any of this directly from the EA staff in their communications to users suffering from the glitch? And, if the cache deletion approach is valid, then why have some users reported re-glitching after applying it?
I’m not asserting that the approach/theory is definitely wrong. Perhaps indeed it might be a prudent course of action just in case. I certainly don’t see any harm in it. But in a game where we are told precious little by the developers, speculation and theory have a way of quickly turning into fact. My opinion, this is one of those cases.
My character button was fixed manually in January after six weeks of waiting. Today the glitch hit again and alls bugs are on again. :-( No working character button anymore. Will start opening tickets again...
My game was hit for a second time yesterday, just a bit over 1.5 weeks since the first time.
I called EA and requested a rollback to the prior day, which they quickly agreed to and did. It just took me 8 minutes on the phone.
Luckily, I had the prize track finished this weekend and the rollback simply returned me to the point with only the final task from Milhouse's grandma requiring a second go.
After my game worked completely fine on my Nokia 6 with 64GB by combining internal storage and the card as adopted storage (with the game residing on the card) since August of last year, I now decided to move the game to internal storage after the second occurrence. I'll see if this makes a difference. Maybe the recent move from Android 7.1.2 to 8.0 also has some influence on the problem and the upcoming upgrade to 8.1 will bring yet another player to the table...
My B game on a Moto G4 Plus with Android 7.0 and storage card as just that - external storage - has not yet been affected (game in internal storage).
Sadly, I've not yet found any info on which devices, OS versions, configuration aspects and the like are more affected than others.
Replies
I would expect it will happen over and over to those of us hit by it once already until EA fixes it or we give up on the game completely and spend our time and money elsewhere. But given how many people play the game it probably doesn't matter to EA if every person who gets hit with this quits.
It didn't help me with the glitch. A rollback didn't help at all for me and they "fixed some bugged variables" but it all came back again.
BUT either way, it only fixes what WAS broken.....not fixing what BROKE it. So even if your game was fixed properly by correcting the "bugged variables", you can still be hit with the glitch again.
I have had 9 roll backs and one legit fix by correcting the "bugged variables", and have been hit with it after both again (and again....and again.....and again.....and again....and again 7 more times.....)
The key is when you are hit with it.....demand an immediate roll back (here is how to make sure they do itHERE.
But also add pressure to EA to fix it by reporting it to Google HERE
.....and giving a 1 Star rating in the app stores with an explanation why you are rating 1 star.
I’ve heard a number of users “suggest” that this should theoretically help. I have yet to hear anyone provide any evidence in support of the idea.
So, like it say, nothing new really learnt other than it took less than 5 mins to call and they were willing to do a roll back. If I could be bothered doing this twice a week I might carry on but i think I'll wait and see if they can mend the game.
What update are you referring to? I’m playing iOS and have seen neither a store or in-app update. And I see no mention of a new update in General Discussion.
It works for as long as it lasts until you get the glitch again.
See the comments here https://tstoaddicts.com/2018/03/12/rollback-glitch/#comments from Ahtomcat.
Seems there is a way to rollback and refresh the game, however I just got off the phone with EA and they won't do rollbacks anymore. I was asked to just wait for the fix. Polite and patience ... Even suggesting I'm willing to try a rollback still didn't convince them to perform a rollback.
Thanks for posting the link. I hadn’t seen it before. But I have read similar ones and I find neither the logic or evidence particularly compelling. The poster in question argues that in order for a rollover to be effective one needs to clear the cache, etc., etc., and in support of this view offers into evidence the success of his own rollback. I would note in rebuttal that at the time I am writing this his rollback is all of one day old. We’ll see how long his luck holds. Also in rebuttal I would point to the fact that several users have stated that they have, in fact, followed the user-recommended cache deletion approach and their games nevertheless suffered re-glitching. As a final comment on this issue, I recall the first time I heard this theory presented on this forum — it was summarized by a user who suggested that it might prevent the re-glitching of rolledback games. Since that time this suggestion seems to have reified into fact.
It seems as though EA Help is increasingly refusing to perform rollbacks. Perhaps because they see them as a waste of time? Or because too many users are requesting it? Who knows. But I personally find that policy troubling. Since EA still cannot fix this glitch in any sort of permanent way via patch/update, they ought to in the interim be willing to roll back games, even if rollbacks prove to be only a temporary band-aid.
Yes, I recall reading that (although I also recall seeing earlier posts of a similar nature dating back to last year). Of course, as far as I can tell from a surface reading of the post, this is all just assertion without any backing evidence. Yes, the idea has a certain face validity, but how does the poster know any of this is true? Is he a developer or has he been in contact with any members of development team who have passed along this advice. And if either of those things are true, why haven’t we heard any of this directly from the EA staff in their communications to users suffering from the glitch? And, if the cache deletion approach is valid, then why have some users reported re-glitching after applying it?
I’m not asserting that the approach/theory is definitely wrong. Perhaps indeed it might be a prudent course of action just in case. I certainly don’t see any harm in it. But in a game where we are told precious little by the developers, speculation and theory have a way of quickly turning into fact. My opinion, this is one of those cases.
I have been going back over old threads to see when this bug originated. Although this thread was started on June 25th 2017, there are earlier threads about the same problems.
May 8th 2017:
https://forums.ea.com/en/the-simpsons-tapped-out/discussion/97861/bug-quest-progress-screwed-up-reset#latest
March 9th 2017:
https://forums.ea.com/en/the-simpsons-tapped-out/discussion/94270/did-anyone-else-have-these-bugs#latest
Although it didn’t affect many at the start, it has been around for over a year............
I called EA and requested a rollback to the prior day, which they quickly agreed to and did. It just took me 8 minutes on the phone.
Luckily, I had the prize track finished this weekend and the rollback simply returned me to the point with only the final task from Milhouse's grandma requiring a second go.
After my game worked completely fine on my Nokia 6 with 64GB by combining internal storage and the card as adopted storage (with the game residing on the card) since August of last year, I now decided to move the game to internal storage after the second occurrence. I'll see if this makes a difference. Maybe the recent move from Android 7.1.2 to 8.0 also has some influence on the problem and the upcoming upgrade to 8.1 will bring yet another player to the table...
My B game on a Moto G4 Plus with Android 7.0 and storage card as just that - external storage - has not yet been affected (game in internal storage).
Sadly, I've not yet found any info on which devices, OS versions, configuration aspects and the like are more affected than others.
They may well have no bearing whatsoever on the probability of being infected or re-infectected.