修正不能真正保持token的bug #36
Closed
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
因为`@token_data ||= JSON.parse(File.read(token_file))`需要json格式的文件，但在`client.get`时已被转换成hash对象了，写入临时文件时，也是hash后的字符串，导致每次`JSON.parse`时发生异常，直接再次从服务器直接获取了
|
请问一下，他是在哪判断access_token是否过期的？？？ |
|
@xuyao91 他没有判断过期,只是一直带着tmp下缓存的token去访问,当出现42001, 40014 时就抛出AccessTokenExpiredError ,然后上层捕获该错误,重新取得token,并retry ps,根据现在的微信文档,发现错误码40001也应当抛出AccessTokenExpiredError |
|
@zyxstar 这样做不好吧，还是要有一个处理过期的机制，看了一下其它的这种Gem，都有过期处理。 |
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.
因为
@token_data ||= JSON.parse(File.read(token_file))需要json格式的文件，但在client.get时已被转换成hash对象了，写入临时文件时，也是hash后的字符串，导致每次JSON.parse时发生异常，直接再次从服务器直接获取了