Bug Report

Describe the issue: The nsfw filter seems to reset to Show after restarting the app. If you try to change this setting, it resets your theme to “light mode”. Looking in the theme section of the app, there is nothing selected in the drop down, but at the bottom of the modified settings list, I can see my theme was changed from amoled to “darkly-pureblack”.

Theme is the only setting that seems to change (asside from nsfw not persisting), and I haven’t noticed changing any other settings causing the theme to switch to light mode.

Theme reset

Steps to reproduce:

  1. Select a theme
  2. Change the nsfw filter from Show to hide/blur/transparent
  3. Restart app
  • The apps theme should now be white, and navigating to themes will show no selected theme.
  • The nsfw filter will also be reset to Show.

Device Information

  • App Version: 1.0.403 (403)
  • Platform: android
  • OS Version: SP1A.210812.016.G973WVLU9IXE1

Modified Settings

The following settings have been changed from defaults:

  • shouldDisplayTitleAbove: true (default: false)
  • shouldLoadCrosspostComments: false (default: true)
  • commentTextStyle: bodyMedium (default: bodyLarge)
  • customColoursPreset: 1 (default: 0)
  • enableCommentNavigator: true (default: false)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • shouldHighlightNewComments: false (default: true)
  • shouldStackDuplicatePosts: false (default: true)
  • defaultRoute: /community?postCommonListingType=Local&hint=Local (default: null)
  • defaultPostSort: New (default: Active)
  • defaultCommentSort: New (default: Hot)
  • nsfwView: Show (default: Blur)
  • shouldVideoAutoplay: never (default: always)
  • shouldUseProfileBanner: true (default: false)
  • shouldFilterUsernameUnicode: false (default: true)
  • shouldShowFeedInstanceThumbnail: true (default: false)
  • stickySortSettings: true (default: false)
  • theme: darkly-pureblack (default: system)
  • imageDomainRewrites: {} (default: {})
  • kuroM
    link
    fedilink
    arrow-up
    3
    ·
    1 month ago

    Hi, thank you for the report and this should now be fixed on version 405. Cheers!