Skip to main content
J
JackAxe
Participant
September 12, 2013
Question

APKs compiled with 3.9 do not register in Scout.

  • September 12, 2013
  • 1 reply
  • 800 views

Hi,

I've tried this on my Tegra 2 and Exynos tablets.  I've tried both debug and release builds with no luck.  But If I set my SDK back to 3.8, Scout can see the APKs I've compiled in it just fine.

I'm using Scout version 111.354079 and AIR SDK is 3.9.0.790.

***** EDIT *** Please disregard this second part.   A project rebuild and some vodoo fixed my strange behavior.   Still have an issue with the top part, but am testing with more projects.

Thanks,

Chris

This topic has been closed for replies.

1 reply

Jeff__Ward
Jeff__Ward
Inspiring
September 12, 2013

I had no trouble profiling my Nexus 7 with Scout, comparing AIR 3.6 and AIR 3.9 builds to verify Worker performance.  I'll go back and try again when I get a chance, but I'm 99% sure this wasn't a problem for me.

I didn't notice a way to profile the background Worker - though an Adobe page (which I can't seem to find just now) suggests it should simply show up as a separate session, or some such.  I'll try to find this link.

J
JackAxeAuthor
Participant
September 14, 2013

I'm almost to a point that I'm going to try out workers and It would be nice if the CPU usage graph split for each worker, so that I couild monitor them in one view.

I finally got Scout to profile.  I had to do a captive release build and it worked and I guess I was overly tired, but I hadn't instaleld AIR 3.9 on my tablets -- which is used during testing, even thought I thought all APKs were generated as Cpative runtimes now?

I have to wonder though, how I do a release build that doesn't profile at all?   Even though it's not that important, I don't want my final app being profiable by somone running scout.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices