Courier Fetch Error when refreshing Discover screen with an already caught error

[ppf2]

Here is a screenshare recording of the steps to reproduce. Discovered while reproducing #4777

https://drive.google.com/file/d/0B1rxJ0dAZbQvRHIyUnN6dzVoMFk/view?usp=sharing

In short, once the error in 4777 shows up, if you click on Discover screen again, then it throws a fatal error like the following:

 Fatal Error
Courier Fetch Error: unhandled error ErrorAbstract@http://localhost:5601/index.js?_b=7489:83946:19
StatusCodeError@http://localhost:5601/index.js?_b=7489:84095:5
respond@http://localhost:5601/index.js?_b=7489:85288:15
checkRespForFailure@http://localhost:5601/index.js?_b=7489:85256:7
[24]</AngularConnector.prototype.request/<@http://localhost:5601/index.js?_b=7489:83894:7
qFactory/defer/deferred.promise.then/wrappedErrback@http://localhost:5601/index.js?_b=7489:20902:31
qFactory/defer/deferred.promise.then/wrappedErrback@http://localhost:5601/index.js?_b=7489:20902:31
qFactory/defer/deferred.promise.then/wrappedErrback@http://localhost:5601/index.js?_b=7489:20902:31
qFactory/createInternalRejectedPromise/<.then/<@http://localhost:5601/index.js?_b=7489:21035:29
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://localhost:5601/index.js?_b=7489:22022:16
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://localhost:5601/index.js?_b=7489:21834:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://localhost:5601/index.js?_b=7489:22126:13
done@http://localhost:5601/index.js?_b=7489:17661:34
completeRequest@http://localhost:5601/index.js?_b=7489:17875:7
createHttpBackend/</xhr.onreadystatechange@http://localhost:5601/index.js?_b=7489:17814:1

[dfr0]

+1

[cjcenizal]

@ppf2 Do you think this is still valid, or can we close this issue?

[lukasolson]

Closing as the original video regarding how to reproduce is no longer available, and we haven't heard any complaints about this in a long time.