Found nothing with the debugger, then again it is hard to debug without the source. Have to investigate how to provide the Android Studio Debugger with the sources. Sometimes a few roster entries seem to update, but messaging anyone fails with a nullpointer in ChatManager(139).
Have to investigate how to provide the Android Studio Debugger with the sources.
AFAIK this is not possible. That’s the main reason I don’t use Android’s gradle-plugin. With the standard Android Ant build and Eclipse I can easily debug the source of libraries of my project.
PacketParserUtils﹕ Failed to parse extension packet in Presence packet.
OTOH it could be that enabling carbons somehow adds a packet extension to some presences, a packet extensions that is causing the exception. But that would be news for me
So besides the Warning, which is usually not fatal, what’s the problem with carbons?
but messaging anyone fails with a nullpointer inChatManager(139).
Again, a full stacktrace would be helpful
Okay, i found the cause for “PacketParserUtils﹕ Failed to parse extension packet in Presence packet.”: Miranda IM. The status text is causing this i think.
The problem seems to be multiple clients/ressources active at the same tim, some with carbon support, some without.
a custom webclient, miranda, spark, and my app. When my app with carbon support is online, the other clients crash/disconnect when sending messages from itself. the target user dont receive the message, but the carbon copy shows up in my app. the app with carbon support enabled doesnt die. something doesnt work right here.(Server is Openfire 3.9.3)
Another thing is, the roster doesnt work as expected with carbonmanager enabled. the roster is not correct after connecting. everytime a client later on changes presence, the roster entry for this client is ok again. I will investigate what the cause of this is tomorrow.
Thanks for your time so far
Edit:
According to the smack log, the presence pakets arrive correct at the client.
the other clients crash/disconnect when sending messages from itself.
Does the client disconnect or the server? If the later, then you may find the reason in the openfire logs.