Thanks for the response. The model was trained with CPU only PyTorch so I’m not sure if it can be the problem.
My main recommendation for PyTorch mobile is to add more descriptive error messages. Most errors just show up in the logcat as a cpp file (usually backend, import, or function_schema_inl.h) and line number, which is hard to debug. Right now the platform is very new, and there isn’t much information out there on how to fix errors so we have to figure it out based on the error messages.
Overall though, I think the API is actually quite nice, and it’s really great that mobile support has been added.