IIUC we _can_ catch the exception in Kotlin code if we just want this specific crash to go away. However, that would imply a few things: - Users on those devices won't have access to a feature without any indication as to why. Our solve here would be to basically silently fail downloading wallpapers forever. - The underlying issue that Samsung has caused here is liable to appear in other places throughout the app, so we either 1. Litter the codebase with exception handling (and random dead spots in the app for users) 1. Undertake a pretty massive technical initiative to solve it more generally IMO the short-term solution is not worth the damage to the user experience or the long-term health of our code, and the long-term investment is not worth the effort given the (shrinking) size of the device segment of Samsung users on Android 5.0.x. We are already actively monitoring for when we can stop targeting that API level completely.
Bug 1851704 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
IIUC we _can_ catch the exception in Kotlin code if we just want this specific crash to go away. However, that would imply a few things: - Users on those devices won't have access to a feature without any indication as to why. Our solve here would be to basically silently fail downloading wallpapers forever. - The underlying issue that Samsung has caused here is liable to appear in other places throughout the app, so we either 1. Litter the codebase with exception handling (and random dead spots in the app for users) 1. Undertake a pretty massive (and hacky, ultimately) technical initiative to solve it more generally IMO the short-term solution is not worth the damage to the user experience or the long-term health of our code, and the long-term investment is not worth the effort given the (shrinking) size of the device segment of Samsung users on Android 5.0.x. We are already actively monitoring for when we can stop targeting that API level completely.
IIUC we _can_ catch the exception in Kotlin code if we just want this specific crash to go away. However, that would imply a few things: - Users on those devices won't have access to a feature without any indication as to why. Our solve here would be to basically silently fail downloading wallpapers forever. - The underlying issue that Samsung has caused here is liable to appear in other places throughout the app, so we either 1. Litter the codebase with exception handling (and random dead spots in the app for users) 1. Undertake a pretty massive (and hacky, ultimately) technical initiative to solve it more generally IMO the short-term solution is not worth the damage to the user experience or the long-term health of our code, and the long-term investment is not worth the effort given the (shrinking) size of the device segment of Samsung users on Android 5.0.x.