Known Issues

Functionality with testing an application by bundle identifier was broken in version 2.8.1 which resulted in an error titled "No target application path specified via test configuration: ...". Update to 2.8.2 or the latest version to resolve the error. Update to the latest within the iOS Analyzer project.

With version 2.8.0 (View Release Notes), results are no longer reported on views that are not visible, including off-screen or hidden by another view. We've discovered in SwiftUI applications being tested in iOS 17, some results still show. (#1383)

There is an issue affecting the iPhone 15 Pro simulator that prevents the Supports Dynamic Type rule from running. If you are opted in to the Supports Dynamic Type rule, you will not be able to test it using an iPhone 15 Pro simulator. A bug has been filed with Apple.

While looking at an improvement for our rules, we found that in XCTest, nested controls are not returned in the accessibility tree. A bug has been filed with Apple. (#1110)

We are actively working on fixes for the following false positives and will update this list as fixes are released.

In Scroll View
May report issues for text within banner-behaving elements. To make these elements available to those that require larger text, use UILargeContentViewer. (#622) ActiveControlName
If an UIImageView has an `accessibilityIdentifier` set but is not focusable by VoiceOver, and it has focusable controls nested within it, ActiveControlName may report a false positive on the UIImageView. Removing the `accessibilityIdentifier` resolves the issue. A bug has been filed with Apple. (#1226)

We are actively working on fixes for the following false negatives and will update this list as fixes are released.

Image View Name
If an UIImageView has an `accessibilityIdentifier` set but is not focusable by VoiceOver, ImageViewName may report a false negative on the UIImageView. Removing the `accessibilityIdentifier` resolves the issue. A bug has been filed with Apple. (#1226) Focusable Text
Elements marked as non-accessibility elements may report improper results due to a bug in Apple's framework.

If minifying your build, you'll see a crash with an error log reporting an adapter could not be found when trying to login to the axe DevTools library. Disable minify for your debug builds with axe DevTools implemented. (#729)

A build with r8 enabled may attempt to minify the axeDevTools library resulting in an error similar to:

Caused by: java.lang.NullPointerException: throw with null exception
at g.b.b.a$a.a(Unknown Source:1)
at g.b.b.a$a.a(Unknown Source:0)
at g.b.b.a.a(AccessToken.java:190)
	

If you encounter an error along the lines of `Expected exactly '1' node but found '2' nodes that satisfy: (isRoot)` or `No View initialized, did you call AxeDevToolsCompose.setComposeTestRule()?`, please refer to Compose setTestTag API.

If the screenshot is missing from the scan details page, your app may be preventing screenshots from being taken. Often this is for security reasons in your production application. Consider removing this requirement for your testing build to allow for full functionality in the axe DevTools Mobile Dashboard.

• Android - FLAG_SECURE

Some Android scan names that are defaulted to the screen title will appear as the full class name including the bundle identifier. In a future release, this will be resolved so that the screen title is formatted into a more readable name. As a workaround, you can set the scan name from the dashboard or frameworks. (#1643)

Due to limitations in information available via the Appium platform, we've identified a false positive for Active View Name when using the labeledBy property to provide a label for a button element. We are exploring solutions and expect a fix in a future release.

Due to limitations in information available via the Appium platform, we've identified the Label In Name & Label At Front rules aren't able to run for apps built with React Native. We are exploring solutions and expect a fix in a future release.

Sometimes the Appium page source property needs extra time to get updated between scans. If this happens, you'll see a previous screen's view hierarchy when using the inspect feature on the dashboard. To fix, add a small timeout before calling the page source API to prompt the accessibility scan. Example:

			await driver.pause(1000);
    		const result = await driver.getPageSource();
		

Due to limitations in information available via the Appium platform, we've identified the Image View Name rule is unable to accurately test for decorative image success criteria in Android. Results for images without an accessible name will display as 'Needs Review' in the dashboard for further analysis.