Do you mean that it's going to the search page in Panel? If so, what we could try doing is moving the search page button to the main menu instead.
Open JRiver for Android
It connects to the last Library. (This took some time and just showed a white screen with no indication it was working. I nearly killed it before it opened.)
Select Audio > Album View > Album
Tap first track > Play All
Tapping the thumbnail on the left in bottom Playing Now bar opens Playing Now.
Press Android Back button to see Search bar. (Ah, Back button didn't work. JR4A not responding. Multiple taps. Android screen sleeps. Wake Android to see request to log in to Cloudplay!)
Start again... stops responding except for the Play/Pause button.
Leave it paused while I type. Go back and press Play. Search bar opens. See image. The onscreen keyboard was also open, so only two tracks were visible, but that closes when I try to take an image.
This wasn't the method I intended to produce the result, but the end point was the same.
It could be that the Search Bar opens when I tap the metadata in the middle of the bottom Playing Now bar, rather than the thumbnail. That may actually be intentional. Because if I tap on the Artist name, the search seems to show all tracks from that Artist, rather than what is in Playing Now. But tapping the [Name] or [Album] doesn't seem to have the same effect. I don't know. But I mostly find it annoying.
EDIT: I just compared JR4A to what Panel does. Yes, it is clicking on the metadata that opens the Search Bar at the top in the panel interface. Also, if I click on say the Album, which opens the Serch bar, then the thumbnail, which shows Playing Now, and then click the Back button Panel does take me back to the open Search Bar. So it is a Panel interface function. That works okay in Panel on a PC with a large screen, but not so much for JR4A on a phone. Plus sometimes the Search Bar seemed to open when I hadn't clicked any metadata. I don't know what the answer is. I don't think making the Search function harder to get to is the answer. It could be that this is just a user training issue. But it isn't a good user experience.
Once you have entered the credentials and successfully loaded a library server that requires authentication, it should store the credentials.
That the user needs to know the server requires Authentication and must tick the checkbox to enter credentials is very annoying. Surely JR4A could remember which Libraries require credentials? Or better, query the Library?
When I was connected to an Authenticated Library, then switched to the local Library, then switched back to the Authenticated Library, I didn't tick the checkbox, it wasn't ticked, but JR4A still connected. There was no indication that JR4A already had the credentials saved for the Library I was trying to connect to. This is not intuitive at all.
The credentials were being remembered though, and JR4A was reconnecting to Libraries where I had previously provided credentials. I switched between two Authenticated servers and the local Library no problem.
It's slow.
The second Confirm message and button tap to allow a restart of JR4A is annoying.
That JR4A doesn't restart by itself, but does seem to remain running in the background is confusing. It seems that only the Notification area is updated to close the JR4A notification.
It is concerning that JR4A requires a restart on changing the Library at all. Android reported that the App kept stopping at one point, but I don't know if that was because of the "normal" restart, or some other problem. Feedback sent.
That after confirming a restart it takes some time to do whatever it is doing, showing the "Loading Library" message again for a while, then shows a fully black screen, then a fully white screen, then disappears, is concerning.
That (re)opening JR4A shows a blank white screen for some time with no indication of working is concerning.
That I can tick the "Requires Authentication" checkbox for a Library that requires Authentication, but then enter no credentials, and JR4A still connects, is both concerning and confusing.
I would prefer JR4A to know when Authentication is required, and then ask for credentials. If it already had credentials then it should just connect without asking. If the connection failed JR4A should ask for credentials again, and if changed store the new credentials. There should be a way to change credentials before trying to connect. Or maybe there should still be a Confirm message after selecting the Library to connect to, and if that Library required Authentication, the Username and Password fields should be shown on that screen so a user could change them.
Currently, I don't think JRiver for Android is ready for prime time.