TimNew
TimNew
@MaikuB Maybe considering let exception caused by `checkAndSetPendingOperation` has a different error code? So it can be identified from flutter code easier. Or having an parameter to ignore the later...
I can make a PR for this change later, but right now, I'm quite occupied.
Go through the issue again, I think in general, `ConcurrentOperation` should be considered as an error instead of an exception in dart language semantics. As it is generated on by...
我的 app 有完備的測試例 用 QueuedInterceptor 重寫了 Token 相關的代碼後 所有處理連續異常的場景的測試例都超時了 我的感覺是 QueuedInterceptor.onError 裡調用同一個 dio 實例會導致死鎖。 感覺是個設計缺陷: https://github.com/flutterchina/dio/issues/1612
I ran into the exactly same issue
@MaikuB Check PR https://github.com/MaikuB/flutter_appauth/pull/395
Yep I aware that the error code would be different, in fact the PR doesn't try to unify the error code too. It just expose the native error code to...
In fact, I had looked into the feasibility to unify the error, actually tried to do it at very beginning. But I ended up with current solution without touching them,...
@MaikuB I'll try to do it asap! Got a bit snowed by the daily work
Failed to build on `ruby-2.2.3` ``` [rtanque] gem install texplay -v 0.4.4.pre Building native extensions. This could take a while... ERROR: Error installing texplay: ERROR: Failed to build gem native...