PlexAmp iOS hangs when clicking on track search results

Anyone else seeing an issue, where if you search for a song, and then select on it in the resulting track list the app just hangs… Been doing it for quite a while (year +), just been too lazy to report it…

Does it both in wifi and cellular connections…

I’m currently running 4.2.2 of the app on a Plex Server running the latest build on a Synology NAS as an FYI. 64,408 tracks on my server, in case the thinking is related to

Thanks!

Please post Plexamp logs because without them it is very hard to even diagnose such issues.

I’m not seeing this behaviour myself.

Some things come to mind:

  • don’t let your hard drives spin down their platters when idle
  • Let the server run during the scheduled server maintenance hours
  • Check if the DNS resolver (usually located in your router) of your local network performs “DNS rebinding protection”.
    If you can, tell it to exempt the domain name plex.direct from this protection.
  • Check the main Plex database file for damage:
  1. activate debug logging (not ‘verbose’!)
  2. quit Plex Server
  3. wait 1 minute
  4. start Plex Server
  5. wait 5 minutes
  6. fetch log files and attach them here

Or inspect them yourself. Take a look at the Plex Media Server.log file and seek for messages about database corrupt or malformed.
If you find these, you may have to repair your database.

Synology FAQ - Questions, Answers, and a few How-To's - #23 by ChuckPa

Thanks @OttoKerner

Did that and did not see any corrupt or malformed issues in the plex server logs. I’ve also attached the PlexAmp log from iOS to see if that aids in diagnosing.

After I completed the shutdown … pause … restart of PMS, I did go into PlexAmp and did a search — hang scenario in the App… to see if the logs would catch it…

Plex Media Server Logs_2022-07-18_13-59-26.zip (1.7 MB)
Plexamp-Logs-2022-07-18-1.zip (324.8 KB)
a

Commonality here, Synology, Apple, and delay changing tracks
wasn’t able to lock down the scope of it though

There’s nothing weird in there, and there’s a lot of other stuff going on. Please start the app, let it sit for a bit, then search for a track, tap on it, and when it hangs, wait for a few seconds, kill and restart the app, and then submit logs.

For clarification, by “hang” do you mean the UI becomes unresponsive?

Anything else relevant in terms of being local vs remote, connected to a remote player, etc.?

That is not a commonality.

Thanks Elan,

I’ve done as request and attached the logs.

By hang, I mean the app becomes unresponsive to any interaction … only way forward is a force quit.

This happens both locally (on the same Wi-Fi) as well as remotely (another wifi or cellular)

Thanks

Patrick
Plexamp-Logs-2022-07-19-1.zip (317.9 KB)

I see you searching for “Youve got”. Then pretty much nothing until you kill the app. Very confusing. If you long press the track result, do you get a menu? Anything else different/unique you can think of?

Elan, check this out. I did a screen recording because when I press and long hold a screen appears and then disappears really quickly.

I pressed and long held on the second item - you can see the pop up come up and then immediately disappear. Makes me wonder when I just tap if it displays in the background or something which I why I can perform any other functions.

RPReplay_Final1658271337.zip (3.1 MB)

OK, so I think I see what’s going on here, based on your video.

The context menu is coming up and then flying off the top of the screen (see screen capture below):

So you’re left with a hidden context menu, and somehow the background can’t be tapped to dismiss.

However…I have no idea why that’s happening, and I can’t reproduce locally on a few different devices.

Any idea what might be different on your device?

Wish I new.

Not running anything special software wise or anything. Just a stock iPhone 12 (MGFJ3LL/A) on iOS 15.6…

Anything you want me to try or look at on the device??

Patrick

Anyone else seeing this behavior?

Hi @elan - just to add, I also tested this on my iPad Mini (current Generation) running the latest iOS and I can see the exact same behavior, where the context menu floats up the screen and disappears…

:man_facepalming:

I can’t imagine if it is tied to the underlying PMS … It seems that it would be App related…

Hoping that others will chime in if they also see the issue so that we can help figure out how to recreate. (I work enterprise software engineering, so I recognize the frustration with not being able to recreate user defects…)

Patrick

Do you observe the same behavior if you reset to default plexamp settings (Advanced → Reset to Defaults)?

Wonder if it requires some combination of plexamp and/or iOS settings

Good question @tgp-2 … just tried it (advanced → reset) and force close and restart … and still see it … cracky… :man_facepalming:

Wow, I’m amazing you see it on multiple devices…

Any interesting accessibility settings on? External displays or keyboards?

Eureka @elan - I think I figured it out. I’ve attached another video so you can see what I am describing.

It has to do with where the focus is when selecting a track on the search results. If the focus is inside the search text box, and you tap on a track result, the pop-up scrolls away and becomes hidden … if the focus is outside the search text box and you tap on a track result, the pop-up appears and stays on the screen.

So I think it all has to do with where the focus is when trying to select from the results list…

kudo’s to my son for catching it when I was showing the defect to him :wink:

RPReplay_Final1658784450.mov.zip (20.9 MB)

Hmmm, that’s still very strange, I can’t reproduce with or without focus. Do you have any special accessibility/keyboard/anything in the mix?

I had “Prefer Cross-Fade Transitions” on .. not sure why tbh…

I turned it off and now it seems to be working … :person_facepalming:

Might be something about that setting that impacts the behavior of apps …

1 Like

Wow! That is really random :joy: I will make a note to see if there’s anything we can do to make it work with that enabled.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.