Dealing with mobile APK

Help Mobile Automation
,
1

I have an application that I am trying to create automated processes for.
When I load the APK to MOBILE DEVICE MANAGER, it starts with terms of use that need to be scrolled and confirmed, and then you get to the login screen.
Is there a way for me to start the application and skip this step of the very long scrolling through the terms every time?
Is it possible to save this completed part and start only from the next Login screen?
Thank you

3

@henry102lopez
This post was flagged by the community and is temporarily hidden. ?

6

This is a common challenge when automating apps with an onboarding or EULA screen. Here are a few approaches you might consider:

  1. Shared Preferences / App Data: Many apps store the “Terms Accepted” flag in shared preferences or local storage. If you’re using an MDM or automation tool like Appium or Android Debug Bridge (ADB), you might be able to:
  • Launch the app once manually,
  • Accept the terms,
  • Then pull the app’s data (usually found in /data/data/your.package.name/shared_prefs/),
  • And push it to devices as part of your automation setup.
  1. Instrumented Automation (e.g., UI Automator / Appium): If bypassing isn’t possible via data manipulation, you could automate the scrolling and button click using UI automation frameworks. Though a bit slower, this ensures consistency.
  2. Custom APK Build (If You Control It): If this is your own app or you have access to the source, you can add a development flag (e.g., skipEULA=true) and check for it at runtime to bypass the EULA screen during testing.
  3. MDM Configuration (If Supported): Some MDMs allow you to predefine app states or inject configurations. Check your MDM’s documentation to see if it supports passing flags or presets to apps during provisioning.

Would love to hear what MDM and automation tools you’re using—sometimes there are tool-specific tricks that can help even more.