ep

@Shilpa26v and @ttb-inc I'm just seeing these. Are either if you having this problem in release builds? I closed the issue because it was only an issue during debug runs...

Everything is pretty great as is, but this would certainly be lovely.

Without knowing more, I can say that I get these sorts of errors when there is a library conflict between this package and e.g. the Camera lib

@martin-robert-fink have you had any issues? is your app live? i don't get the follow up errors, sending and canceling are fine. but it's disconcerting anyway.

@martin-robert-fink indeed, good luck with the threading. So you haven't gone through the Apple store yet, or any such ?

If anyone comes across this, check the format of your .toByteData() wherever that is. I know this is a random stab at what must be a varied problem set, but...

I'm dealing with a (perhaps) similar(ish) issue where the memory doesn't drop down if I close the part of the app that's doing that intepreting at certain parts of its...

I think this is a function of any image detection situation operating on a mobile device like this, that works out of the box. I mean the same is true...

@batkhishign55 I found that I had to do this as well. Quick side question-- have you found any memory leak issues on ios ? If you look at the runtime...

@batkhishign55 i'm still not totally confident but the solution seems to be loading the model from file rather than asset-- if anyone is loading from asset. he's got a little...