This is related to the a11y changes, setEnabled is correctly called on the View, however the accessibilityState is not changed, and appium ends up reading the wrong state.

A simple workaround would be to add the following css:

*:disabled { 
  a11y-state: disabled; 
}

However a proper fix would be required in core.

@m-abs I was thinking of setting it here inside the valueChanged callback:

however I'm not sure if there would be any implications of that change.

It might cause some inconsistency problems, if a11y-state: disabled and isEnabled = false are used at the same time. But if you handle that corner-case, I agree.

do you think it can be fixed for next patch?

@rigor789
I think your workaround is not complete:
it worked only for the case where the button isEnabled was set to false to begin with (Appium showed enabled=false as expected)
but now I have noticed that when we dynamically change the button isEnabled from false to true
Appium still shows enabled=false...

btw,
when changing from true to false dynamically (the other way around) it seems to work...
so as I mentioned- the issue is on changing from false to true dynamically, where it stays false

can you try and help us to come out with better solution?

The following workaround (the css one can be removed, this one replaces it) will fix the issue until we implement a fix in core:

import {  Observable,  AccessibilityState } from '@nativescript/core'

Observable.on('isEnabledChange', (args) => {
  args.object.accessibilityState = args.value ? undefined : AccessibilityState.Disabled;
})

This can be placed in the application entry file (main.js/ts, app.js etc).

Nativescript 8.5.0 , Angular 15.2.0

Added

import {  Observable,  AccessibilityState } from '@nativescript/core'

Observable.on('isEnabledChange', (args) => {
  args.object.accessibilityState = args.value ? undefined : AccessibilityState.Disabled;
})

to my main.ts file, but it didn't help. So, I decided to add some console logs to review the behavior. It turned out that callback was not called on enabledProperty change.

To debug place where event is triggered, I added console logs in
/node_modules/@nativescript/core/ui/core/properties/index.js as well

// beginning of my logs
if (eventName === 'isEnabledChange') {
    console.log('event name: ', eventName)
    console.log('object: ', this)
    console.log('has listeners:', this.hasListeners(eventName))
}       
// end of my logs

if (this.hasListeners(eventName)) {
    this.notify({
        object: this,
        eventName,
        propertyName,
        value,
        oldValue,
    });
}

And got:

Since the listener for isEnabledChange is not set for every view by default, this.hasListeners(eventName) returns false for each view -> the isEnabledChange event is not triggered -> the global handler has nothing to process -> the enabled property is not changed in appium.

Is there any way to overcome this problem?

@IlIAntonIlI I think we'll need to reconsider few things for accessibilityState property.
I tend to resort to updating enabled and trait -> UIAccessibilityTraitNotEnabled at the same time which is the most recommended approach.

+1 still seeing this problem in Appium