-
Notifications
You must be signed in to change notification settings - Fork 212
ConcurrentModificationException in the Hue SDK #7
Comments
Firstly apologies for the delay in responding. I have an issue with github notifications but no excuse. I have checked the code and I can't see anywhere which can result in a ConcurrentModificationException. The onReceived method (PHNotification manager) is just calling the onError method in the PHSDKListener (which is created by yourself). If you are still experiencing issues, can you check your onError method (in your PHSDKListener object). |
I am seeing this issue as well. I'd appreciate it if someone could look into it again, thanks! |
Sure, I will take another look. If you have any more details, as to what happened exactly to cause the exception it would be helpful. |
@SteveyO I have been debugging this, and I think it occurs when we call |
@iagreen Thanks, this info was helpful, I have been looking at this issue again. Generally in the SDK, any http call (heartbeat, updates, find new lights etc) is called on a separate thread and the onError is called from this thread. However, saying that am still a little baffled. Normally, I would expect the registerSDKListener to be called when the app is first created and only once (before any http calls are made and before the connection to the bridge has been established). And I will take it from there. Sorry I don't have anything more concrete, it's a tricky one this. |
We were accidentally registering the listener way more than we should have On Fri, Dec 12, 2014 at 5:05 AM, Steve notifications@github.com wrote:
|
We are busy with a Hue app on Android, and often when the bridge becomes unavailable we get the error below. Our implementation of PHSDKListener will post all callbacks to a handler, so we are pretty sure it is not something in our code. Can you please look into it?
The text was updated successfully, but these errors were encountered: