You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell, iOS will throw an exception when this method receives a path like /foo/bar but behaves normally when it receives file:///foo/bar because [VNImageRequestHandler initWithURL] isn't receiving a URL, so it completes requests with blank results. IMO,
This library's JS layer should validate the format of the uri "option" (it's not really optional) to ensure it's a string that both the iOS and Android implementations can process. If the uri is not valid, it should throw an informative error
IDK if there are other ways these classification requests can complete with blank results, but we might want to error out sooner in the iOS implementation if that happens with something more informative than saying a node has no score, b/c really there are no nodes at all in the response
The text was updated successfully, but these errors were encountered:
As far as I can tell, iOS will throw an exception when this method receives a path like
/foo/bar
but behaves normally when it receivesfile:///foo/bar
because[VNImageRequestHandler initWithURL]
isn't receiving a URL, so it completes requests with blank results. IMO,uri
"option" (it's not really optional) to ensure it's a string that both the iOS and Android implementations can process. If theuri
is not valid, it should throw an informative errorThe text was updated successfully, but these errors were encountered: