Hey @rgralak
So... looking through the SGPro logs and API code, I have noted a few things:
- PEMPro looks like it is relying on camera status response to determine when to start asking for the image path on the file system. Nothing wrong with this, but our camera status was broken in 2.5.2 from a bug we fixed.
- An alternate approach that is just as fast and immune to bad status reporting is to just ask for the image's path about once every second. If the image is ready, you get a path, if not, you keep trying until you do (or some reasonable timeout period is reached). Additionally, if you get a path back of "abort" or "error" for your receipt, you can also quit polling then as well.
- Despite that, the status of the camera, as given from the API, has been fixed (in 2.5.2.3). Along with this, "CAPTURING" has been removed and renamed "INTEGRATING" for general consistency within SGPro (breaking change for you and mortal sin for me).
- Allowed camera statuses are now (most refer to the camera image): IDLE, INTEGRATING, DOWNLOADING, READY, ABORTED
I "think", from looking at the logs that this the only problem... I will release 2.5.2.3 very soon to test this theory.