Expose runtime error codes / results in JNI #8260
Labels
module: android
Issues related to Android code, build, and execution
module: user experience
Issues related to reducing friction for users
triaged
This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone
🚀 The feature, motivation and pitch
Currently, the Android JNI bindings do not expose error codes or results through the API. Failure is indicated with empty EValues. It would be desirable to either implement a Result type (similar to the native API), or use Java exceptions to communicate failure. Ultimately, the goal is to clearly provide error codes / information on inference or model load failures. This will be a big improvement for debuggability, as logging is not always easily available (for example, in production).
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @kirklandsign @mergennachin @byjlw
The text was updated successfully, but these errors were encountered: