0👍
✅
After doing further testing, it looks like this warning is displayed when a route that uses NetworkFirst
with networkTimeoutSeconds
and the response from the route exceeds the number of seconds set in networkTimeoutSeconds
.
Source:stackexchange.com