Does your mention of Legacy mean that you are using the Legacy mobile testing rather than the Cloud-compatible?
If so, that only supports up to Android 11 from what I see here
https://support.smartbear.com/testcomplete/docs/app-testing/mobile/device-cloud/requirements.html
Hi - Thanks for the reply, yes, that is indeed what it means. Legacy Mobile Testing... sure hope the intent is to support Android 12 as well.
Ron F.
------------
You can check with Support here
https://support.smartbear.com/testcomplete/message/
Let us know what they say!
Hello Marsha, seems ya'll are correct... Android 12 from what I understand, not supported in Legacy manner... I am working an Appium solution.... as I type. Lol
I have appium set up as Local Server... and it now does "see" my new tablet... some of my current test script commands work, and some... not so much. I am in tuning and tweeking mode. Getting some strange behavior as well... for example in a simple login script.... I have 4 commands as an example)...
they are:
1.) Click the tablet Apps "Login Via Email" button
2.) Enter a valid Email address
3.) Enter associated password
4.) Click Submit
Easy. Not yet. Lol
If I run this script.... with all statements uncommented....
Step 1, runs
Then subsequent 3 steps say Object Not Found type of errors...
- and yes, I have delayed the Steps 2-4 ... no change... can't find the objects
But.... if I have the app at the "Step 1" position.... and Comment Out Step 1, as I did it manually, then run the same script... (with Step1 commented out).... all 3 subsequent steps run fine and dandy.
Yep... confused at this point.
So, literally... I can have all 4 commands, uncommented.... run, have step1 run, no prob, gets to next command (step 2) and generates errors.... then, simply comment out step 1, re-run and all the next 3 statements magically find the objects.
Anyways, I may be back in touch with Support. Good folks. Very helpful.... I'm sure its something I just can't put a finger on - yet.
Also, something that may or may not be helpful to others using the Local Appium solution for their Android (others?) mobile tests... when you set up your capabilities... I had a heck of a time getting it to work... long story short... I needed to include the "appActivity" then mine worked. For "my" local Appium CAP settings, I ended up using:
"deviceName": "<your dev name here>",
"platformVersion": "<My devices android version here>",
"platformName": "Android",
"automationName": "UIAutomator2",
"app": "<your apk name here>",
"appActivity": "<I used login activity>"
Anyways, not sure if this will be useful as these are "my" settings as an example.... but not having that
last one set... cost me several hours of checking around etc.
I'm sure will be different for many, but for me.... things worked after adding the last entry. Lol
