Accidental file delete on mobile.

[Chirana Gheorghita Eugeniu Theodor]

i can work on ssrftest... but i will need a pass also.

logs I get right after app crashes from the documents folder in the
internal phone storage. That is where I find the log for subsurface. And
after I send it I delete it so it gets recreated with new info of new
tests.

Fot the builf part.... I think I can setup something. I work with nix* and
compiling stuff for over 19 years now soo... android should not be very
very difficult

I am surprised you cannot replicate. It's just adding a blank dive with no
data, save and from list of dives screen delete from 3 dots or by long
press.... One more thing i realize now: sometimes the delete option does
not appear right away. I have to bring the menu second time up so I get the
delete option.

I even tried now after saving the dive, exit app, relaunch it and delete.
Delete option is there at first time but still crashes the app. but the
empty dive is gone ... so it deletes something... next empty dive created
gets dive number as normal ... every time after delete the new empty dive
has the same number
Even cresting a second empty dive and deleting the first crashes the app...
weird

On Tue, Jan 19, 2021, 22:50 Dirk Hohndel <dirk at hohndel.org> wrote:

>
>
> On Jan 19, 2021, at 12:40 PM, Chirana Gheorghita Eugeniu Theodor <
> office at adaptcom.ro> wrote:
>
> Can I do something? maibe create a more compressive test enviroment on a
> pc with a android on windows test enviroment?
>
>
> The challenge really is the lack of reproducibility.
> You say this crashes for you every time. Does it crash for you if you try
> this on top of the ssrftest at hohndel.org cloud log?
> This way I'd have an "even more similar" environment to you that I could
> try to reproduce this in.
>
> Without an ability for you to build from source I don't think there's much
> you can do locally as far as getting more debug output.
> I can of course create a version that dumps OODLES of debug data into the
> log and hope that we'd stumble across the issue there, but even that is
> hard unless I have at least some inkling of WHAT exactly gets deleted.
>
> I'm just about to merge what I have into master and I'll create a new
> build based on that. This removes the last hack that I tried (as that
> clearly didn't help).
>
> Once that is done I'll try to add a "moderate" amount of additional debug
> information to the next beta build.
>
> One question occurred to me. You talk about it crashing, yet you have the
> log file. How are you doing that? After the app crashed usually you cannot
> easily get to that information - and the files you send don't look like
> they come from `adb`...
>
> /D
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20210119/7f66c281/attachment.htm>