The root issue seemed to be, if a keyboard was shown for a focused EditTextView that was also disabled, older versions of android would crash inside the input manager which was impossible to catch with a try/catch block. The end result was major: some users could not restore their wallets. This work around addresses the problem by keeping the focused view enabled at all times. In theory this could result in some weird behavior but in practice, that's unlikely.
Mainly involves using a network parameter rather than a separate build for testnet and mainnet. This network object is also now the source of the SAPLING_ACTIVATION_HEIGHT, which varies by network. The other major change is the way wallet initialization works, particularly around viewing keys. Under the hood, this involves a database migration so it is worth testing the upgrade path.
Primarily a developer feature to warn when a local build of the SDK is broken because the Rust libraries did not properly link, which happens occasionally and can be frustrating but should never be seen by an end user. In the event that a broken build does make it to a user, this would at least improve the experience.