On Android, accessibility says whether an Accessibility service pressed
your app's buttons, as banking trojans do to move money on their own: which services can tap the screen, which
declare themselves tools for users with disabilities, and, while your app has the measurement on, how many
touches your app's screen had, how many of them a service made and how many clicks came with no touch behind
them. Counts only: no position, no screen and no text. Kotlin, React Native and .NET send it.
On iOS, app_identity says whether the app's code is stored encrypted, as
Apple stores an app it delivers through the App Store or TestFlight; a copy decrypted and installed some other
way keeps it in the clear. Swift, React Native and .NET send it.
The integration guide's section 7.7 says who shows these readings genuinely
and what to do. As always, the SDK only measures; your backend decides.
Necessary for Flutter 0.1.10 tells when an Accessibility service presses your app's buttons, as banking
trojans do to make transfers on their own. With accessibility
turned on, the SDK counts the touches on your app's screen, those a service made and the clicks a service
performed, and names the services that can tap the screen and those that declare themselves tools for
users with disabilities. Counts only: no position, no screen and no text.
On iOS, app_identity says whether the app's code is stored encrypted,
as Apple stores an app it delivers through the App Store or TestFlight; a copy decrypted and installed
some other way keeps it in the clear.
The measurements page says what each reading showed on devices, and the integration guide's
section 7.7 who shows them genuinely and what to do. As always, the SDK
only measures; your backend decides.
Every Android scan now carries app_host, which tells your backend
whether another app is running yours inside its own: where Android says your app's files and data are,
whether it runs under its own user ID, which other apps share that ID, and which other apps' code is loaded
into it or into the processes it starts. debug_state says whether the
runtime's debugger thread is running, other_access names the app that
handles calls when your app turns it on, and emulator also reads the
processor and the kind of device, which a tool that rewrites the build values does not change.
A command that fails is no longer taken as a reading: The root and system-property checks now say why they
could not read. The integration guide's section 7.7 covers genuine users who
show a strong reading, and what to do. As always, the SDK only measures; your backend decides.
Necessary for Flutter 0.1.9 adds Android measurements whose readings come close to proof of an attack.
Every scan now carries app_host, which says whether another app runs
yours inside its own, where it can see and change everything your app shows and sends.
debug_state says whether a debugger thread runs in your app,
other_access names the app that handles calls and the store that
installed it, and emulator reads the processor, so an emulator is told
even when its build claims to be a real device.
A reading the SDK could not take now says so, rather than being taken from what a failed command printed.
The integration guide's new section 7.7 lists the genuine users who can
show each of these readings, how to tell them apart, and what to do. As always, the SDK only measures;
your backend decides.
NecessarySdk 0.1.10 adds a new measurement, runtime, to every scan on
Android and iOS. It reports the version of the .NET runtime an app was built with, whether the app carries
a Brotli decoder, and that decoder's version where it can be read. With it, your backend can find the
installs still running a release built on a runtime with a known flaw, such as the Brotli decoder flaw
CVE-2026-111497, fixed in .NET 8.0.33, 9.0.22 and 10.0.14. It can then ask people to update, or hold back
sensitive requests until they do. As always, the SDK only measures; your backend decides.
On iOS, the comparison of the app's code in memory with its files now also covers apps built with
NativeAOT, which keep their .NET code in a section of their own.