This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mobile Studio 2020.3 capture on hold

Hi,

I was giving a try to 2020.3 but I can't find an option to avoid capturing straight from app start. The point of capture I'm (typically) interested in is a few good seconds away from the start of the app and this generates a very large apc file. Is there a way for the capture to start paused or something along those lines? 

In addition to this when I stop the capture it kills the application. I would be great to keep it alive to do more captures if I need to.

Parents
  • Hi Pete,

    Thanks for the clarification!

    File size is one of the main reasons, yes, but ... I just had a look at what's getting stored in the apc directory and found out, to my surprise, (and fault) that the apk together with symbols files have been stored from old capture sessions in many of my captures (due to me adding it to the configuration a long time ago). Having those removed really makes the capture size much much less important, so my apologies here.

    Having said this, in my particular case, I also find it quite useful to have multiple captures that I know have started at roughly the same time as I tend to compare multiple captures "side-by-side". I understand I can just add a bookmark but I just find it easier to have multiple captures where I know, say, second 1/2 in the capture roughly matches second 2 in the other capture and vice-versa. Both options you mention above sound quite useful though, and not exclusive. I would certainly find myself using both!

    Keeping the app alive after the app is also something quite important for me as I tend to make multiple captures most of the time (multiple levels, etc..). If there's something I can manually tweak locally until you add an option to avoid this it would be great to know. I'll have a look at the script to see if something obvious pops out.

Reply
  • Hi Pete,

    Thanks for the clarification!

    File size is one of the main reasons, yes, but ... I just had a look at what's getting stored in the apc directory and found out, to my surprise, (and fault) that the apk together with symbols files have been stored from old capture sessions in many of my captures (due to me adding it to the configuration a long time ago). Having those removed really makes the capture size much much less important, so my apologies here.

    Having said this, in my particular case, I also find it quite useful to have multiple captures that I know have started at roughly the same time as I tend to compare multiple captures "side-by-side". I understand I can just add a bookmark but I just find it easier to have multiple captures where I know, say, second 1/2 in the capture roughly matches second 2 in the other capture and vice-versa. Both options you mention above sound quite useful though, and not exclusive. I would certainly find myself using both!

    Keeping the app alive after the app is also something quite important for me as I tend to make multiple captures most of the time (multiple levels, etc..). If there's something I can manually tweak locally until you add an option to avoid this it would be great to know. I'll have a look at the script to see if something obvious pops out.

Children