In the current code using `startInLoadingState` and `injectedJavaScript` will result in an infinite loading state if `injectedJavaScript` fails to evaluate for some reason. This adds a red box error explaining there was a failure to evaluate javascript. In my case this was do to the JS string not returning a valid type so I've added a that as a potential solution in the error message and added some documentation to the API Reference with some additional warnings. To reproduce the existing behavior setup a webview with `startInLoadingState` and `injectedJavaScript` that returns an invalid type (in my case it returned a function). You should see an infinite loading state as `onLoadEnd` is never called. Try the same with this branch and you'll get a nice red box error suggesting one potential solution to the problem. 
|
||
| 102 | 102 |
|
| 103 | 103 |
|
| 104 | 104 |
|
| 105 |
|
|
| 105 |
|
|
| 106 | 106 |
|
| 107 | 107 |
|
| 108 | 108 |
|
|
||
| 512 | 512 |
|
| 513 | 513 |
|
| 514 | 514 |
|
| 515 |
|
|
| 516 |
|
|
| 515 |
|
|
| 516 |
|
|
| 517 |
|
|
| 518 |
|
|
| 519 |
|
|
| 520 |
|
|
| 517 | 521 |
|
| 518 | 522 |
|
| 519 | 523 |
|