Crash while scrolling comments section or playing popup and rotating the phone

[Jotalea]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

0.27.2

Steps to reproduce the bug

1. I searched for a chinese song.
2. I clicked on a video, and listened for a moment.
3. I minimize the video, then pick another one (also in chinese) and open it.
4. The app crashed and told me to report this bug.

Couldn't replicate, sorry.

Expected behavior

Open the video normally, and listen to the song.

Actual behavior

Crash screen with the log below.

Screenshots/Screen recordings

No response

Logs

Exception

• User Action: ui error
• Request: ACRA report
• Content Country: US
• Content Language: es-US
• App Language: es_US
• Service: none
• Version: 0.27.2
• OS: Linux Android 14 - 34

Crash log

java.lang.IllegalStateException: Fragment CommentsFragment{88896fb} (7b68c86b-62b9-4fc9-981a-bdbba4bafcf5) not attached to a context.
	at androidx.fragment.app.Fragment.requireContext(Fragment.java:972)
	at androidx.fragment.app.Fragment.getResources(Fragment.java:1036)
	at androidx.fragment.app.Fragment.getString(Fragment.java:1058)
	at org.schabi.newpipe.fragments.list.BaseListFragment.onSharedPreferenceChanged(BaseListFragment.java:477)
	at android.app.SharedPreferencesImpl$EditorImpl.notifyListeners(SharedPreferencesImpl.java:637)
	at android.app.SharedPreferencesImpl$EditorImpl.lambda$notifyListeners$0(SharedPreferencesImpl.java:643)
	at android.app.SharedPreferencesImpl$EditorImpl.$r8$lambda$TQ_9B5e1x2X557KXM5HWBb4Ihjc(Unknown Source:0)
	at android.app.SharedPreferencesImpl$EditorImpl$$ExternalSyntheticLambda0.run(Unknown Source:4)
	at android.os.Handler.handleCallback(Handler.java:958)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:230)
	at android.os.Looper.loop(Looper.java:319)
	at android.app.ActivityThread.main(ActivityThread.java:8919)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:578)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

---

Affected Android/Custom ROM version

Android 14 - One UI 6.1

Affected device model

Samsung Galaxy S21FE 5G

Additional information

App works totally fine after that, can't replicate crash.

[ShareASmile]

A Similar issue was reported in #10098 So we would accept this as bug but Try to find steps to reproduce it reliably/consistently.

[ShareASmile]

Please try these or similar steps to get the crash as tried in this issue #11444 comment

[Thompson3142]

Seems to be related to this: https://stackoverflow.com/questions/50257505/fragment-not-attached-to-a-context.
If somebody can reproduce it, something like this is probably worth a try:

    @Override
    public void onSharedPreferenceChanged(final SharedPreferences sharedPreferences,
                                          final String key) {
        if (getActivity() != null
                && getActivity().getString(R.string.list_view_mode_key).equals(key)) {
            updateFlags |= LIST_MODE_UPDATE_FLAG;
        }
    }

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[github-actions]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.