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
Not sure if this is the place to report issues on mobile. Please direct me to the correct venue if not.
I was able to download the dataserver after my previous issue was resolved. Is the dataserver suppose to serve both the i3m and the i3m.1dt transfer function together to the mobile app?
Right now, if I just simply let the dataserver do the transfer, the image on the mobile app is always black. However, if I combine the i3m and the i3m.1dt file into a i3m.zip archive, the image will load properly.
I am not sure if this is the correct behaviour, in any case, it does not seem to be documented.
The text was updated successfully, but these errors were encountered:
Using ZIP-archives to deploy the datasets on the mobile devices is in fact the recommended way as it also saves a lot of disk space. I guess the documentation should be updated in this regard.
Not sure if this is the place to report issues on mobile. Please direct me to the correct venue if not.
I was able to download the dataserver after my previous issue was resolved. Is the dataserver suppose to serve both the i3m and the i3m.1dt transfer function together to the mobile app?
Right now, if I just simply let the dataserver do the transfer, the image on the mobile app is always black. However, if I combine the i3m and the i3m.1dt file into a i3m.zip archive, the image will load properly.
I am not sure if this is the correct behaviour, in any case, it does not seem to be documented.
The text was updated successfully, but these errors were encountered: