Share this question

Welcome to Teachnovice Q&A, where you can ask questions and receive answers from other members of the community.

This is a collaboratively edited question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

How to avoid TagManager "IllegalStateException: Results have already been set"?

0 like 0 dislike

I have recently introduced Google TagManager into my Android app in order to push changes to app config without needing to redeploy the app.

But I am getting instances of:

java.lang.IllegalStateException: Results have already been set
at Source)
at$a.a(Unknown Source)
at Source)
at Source)
at$b.a(Unknown Source)
at$b.a(Unknown Source)
at Source)
at Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

They occur across a variety of devices from Android 4.4 to 5.0.1

As you can see there is no element of my app in the stacktrace, and I am really at a loss and to what I can do (other than remove TagManager) to avoid or mitigate the error.

I have found one reference to the same error message associated with GooglePlus login so I am thinking it might be to do with the Google Play Services library.

Anyone else seen it? Any ideas?

Have raised issue with Play-Games project:

asked Jan 24, 2015 by William  
Have you tried downloading TagManager SDK & decompile everything + grep a "Results have been already set"? That will explain exactly when this error is thrown, it'll lead you eventually to a solution.
What Google Play Services version are you using? Have you seen the latest docs, updated Dec 18th?
@JaredBurrows 6.1.71 and yes I have thanks

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please log in or register.