TestFlight beta feedback for Subsurface-mobile.

[Scott Ireland]

Since I’ve just finished the last dives of a trip and won’t have more samples to import for a while, I went into local mode (which, incidentally, caused the app to crash) and did another import which managed to reproduce the issue with one line “missing”.  One (cropped) screenshot was taken after initially scrolling down the list (there were about 40 dives imported this time and the fault was near the bottom of the list), and the other after scrolling up and down and causing enough of a redraw to make the missing line reappear (there should be two dives on Sep 28).

> On Dec 2, 2017, at 15:49, Dirk Hohndel <dirk at hohndel.org> wrote:
> 
> Hi Scott,
> 
> Thanks for the feedback - this is super helpful.
> I noticed (sadly, after pushing to TestFlight) that only the Shearwater dive computers populate. The other ones are missing and I haven't figured out why, yet.
> 
>> On Dec 2, 2017, at 12:33 PM, Scott Ireland <sireland at ualberta.net> wrote:
>> 
>> Successfully imported 35 dives from a Shearwater Perdix (non-AI) to the mobile app on iPad.
>> 
>> Had a little confusion at the start as to exactly what process had to be followed, which is more a documentation thing than anything.  I initially tried BT pairing (which fails at discovery) and am used to the workflow from desktop where I would open the app, start BT on the Perdix, then initiate the download, but here it seems that BT has to be started before the app opens for the Perdix to be picked up.  Once I tried it in that order, it worked.  Maybe some kind of “rediscover” option would help here (and I’ll admit I didn’t wait long enough to see if this was being done automatically).
> 
> Yes, this is something that we need to work on - the overall flow is not intuitive and assumes that you know what to do in which order. Part of the problem is, of course, that this is different on pretty much every OS we support :-(

Fair enough.. and in this case, the current docs (which are more Android-focused) seem to suggest that pairing is necessary, which is what tripped me up at first.

>> The dive list for the import confirmation was a bit strange; some of the lines wouldn’t display at first showing a fractured list with gaps in it but after I scrolled back and forth they reappeared.  Once they all showed up I couldn’t reproduce the problem from that import.
> 
> Hmm - when you run into things like this it's always good to take a quick screen shot. From the description this doesn't sound like something we've seen before.
> 
> Again, thanks for testing and thanks for the report!
> 
> /D

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image2.jpeg
Type: image/jpeg
Size: 153303 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20171202/f2b384ca/attachment-0002.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image3.jpeg
Type: image/jpeg
Size: 184891 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20171202/f2b384ca/attachment-0003.jpeg>
-------------- next part --------------


-- 
Scott