信道服务器返回格式不统一的问题解决 #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
在这里将body.getString("data")改为body.get("data").toString()可以暂时解决这个问题。
但是对于JSON对象的话，可能会因为对象转成了字符串再转换成对象，而造成的一些运算冗余。
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
在返回无效信道的时候data字段返回的是JSON对象，而请求信道的时候却为JSON格式字符串。
在这里将body.getString("data")改为body.get("data").toString()可以暂时解决这个问题。
但是对于JSON对象的话，可能会因为对象转成了字符串再转换成对象，而造成的一些运算冗余。
如果不修改的话，onTunnelClose函数永远不会调用，就不会自动清理信道了。