@nayelyz When preferences that are
required:false, default:null are changed, the value is not saved and the infoChanged lifecycle handler is not called. I’ve tried with both explicit and embedded preferences to the same effect. After changing one of these preferences, changes to any other preference do not trigger the infoChanged lifecycle handler until the settings menu is exited and re-entered.
The simplest example is a driver using the two stock explicit preferences below. The tempOffset preference has a default value of 0 and properly triggers the infoChanged lifecycle. However, if the password preference, which has a null default, is changed it does not trigger the infoChanged lifecycle and renders the tempOffset preference non-functional until the settings screen is exited and reentered.
I’m using the Android app, if that matters.
preferences: - preferenceId: tempOffset explicit: true - preferenceId: password explicit: true