Selecting "Library" causes Tempo to halt

c0utta commented 1 year ago

Pixel Pro 7.

Was hoping the latest version fixed this, but unfortunately no.

Selecting "Library" causes "Tempo keeps stopping" - I have not been able to see the library view yet!

How can I help isolate this issue?

Cheers

CappielloAntonio commented 1 year ago

Hi, sorry to hear that. Could you tell me what server you use? I would like to try to replicate the problem. Thank you!

c0utta commented 1 year ago

I'm using Navidrome. Thanks

CappielloAntonio commented 1 year ago

Hi C0utta, I need your help with this one. I also use Navidrome as my main server, so the problem might be something else. To reproduce it or at least have a log of what is happening, these are the viable ways:

would it be possible for you to let me have the app crash log? For that you should install an unsigned version of the app (which I should upload) so that the log is in cleartext.
an option that I consider a last resort, however, would be to temporarily grant me access to your server so that I can do this debug
in the near future I think I'll rely on Firebase Crashlytics to help me with reports, for anyone who wants to download the app from the Play Store.

Thank you for your collaboration!

c0utta commented 1 year ago

Hi Antonio,

At this stage I’m happy to run an unsigned version – just let me know what you’d like me to do.

Cheers

From: CappielloAntonio @.> Sent: Tuesday, July 18, 2023 6:30 PM To: CappielloAntonio/tempo @.> Cc: c0utta @.>; Author @.> Subject: Re: [CappielloAntonio/tempo] Selecting "Library" causes Tempo to halt (Issue #15)

Hi C0utta, I need your help with this one. I also use Navidrome as my main server, so the problem might be something else. To reproduce it or at least have a log of what is happening, these are the viable ways:

would it be possible for you to let me have the app crash log? For that you should install an unsigned version of the app (which I should upload) so that the log is in cleartext.
an option that I consider a last resort, however, would be to temporarily grant me access to your server so that I can do this debug
in the near future I think I'll rely on Firebase Crashlytics to help me with reports, for anyone who wants to download the app from the Play Store.

Thank you for your collaboration!

— Reply to this email directly, view it on GitHubhttps://github.com/CappielloAntonio/tempo/issues/15#issuecomment-1639820753, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36PJ5FC46573ZI555AM2MLXQZGAFANCNFSM6AAAAAA2HQTOAA. You are receiving this because you authored the thread.Message ID: @.**@.>>

CappielloAntonio commented 1 year ago

So, I just uploaded a debug version of the app, you can find it in the Release section. Do you know how to capture a crash log? Do you have ADB installed on your machine?

c0utta commented 1 year ago

Downloaded and installed (had to remove the old version of Tempo) Have never captured a crash log. Never heard of ADB until now.

Although I’m in IT, this is new ground for me.

Cheers

From: CappielloAntonio @.> Sent: Tuesday, July 18, 2023 10:07 PM To: CappielloAntonio/tempo @.> Cc: c0utta @.>; Author @.> Subject: Re: [CappielloAntonio/tempo] Selecting "Library" causes Tempo to halt (Issue #15)

So, I just uploaded a debug version of the app, you can find it in the Release section. Do you know how to capture a crash log? Do you have ADB installed on your machine?

— Reply to this email directly, view it on GitHubhttps://github.com/CappielloAntonio/tempo/issues/15#issuecomment-1640132407, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36PJ5D3ESUSIAQCYTLIF7TXQZ7NPANCNFSM6AAAAAA2HQTOAA. You are receiving this because you authored the thread.Message ID: @.**@.>>

CappielloAntonio commented 1 year ago

Use a desktop/laptop to download the android platform tools from here and extract the downloaded file to a folder.
Connect your Android device to your computer using a USB cable.
Enable USB debugging on your Android device by going to "Settings" > "Developer options" > "USB debugging." If you don't see the "Developer options" menu, go to "Settings" > "About phone" > Tap on "Build number" 7 times to enable developer options.
Open a command prompt or terminal window on your computer.
Check if your computer recognizes the connected device by typing the following command and pressing Enter: ./adb devices
If your device appears in the list, you are ready to proceed.
If your device does not appear, make sure you have proper USB drivers installed for your device or try reconnecting the USB cable.
To access the crash log, use the following command: ./adb logcat -b crash
This command retrieves the logs from the "crash" buffer, where crash-related logs are typically stored. You should see a continuous stream of logs in the terminal window. These logs might include crash logs from various applications.
Filter the logs for the specific application you're interested in by appending the application's package name to the previous command: ./adb logcat -b crash -s com.cappielloantonio.tempo
As the command executes, you will see the crash logs specific to the application you have targeted. Copy it, save it in a text file and upload it here.

c0utta commented 1 year ago

Wow, way past me since I don't have my own PC.

Next (or last) resort is access to my server. Happy to do this, just need a secure method to transfer login details.

Cheers

CappielloAntonio commented 1 year ago

This is my junk mail where you can send me your address and login credentials.

Possibly create a secondary account on your server so as not to compromise your main user. As soon as I'm done with the tests and after verifying that the problem is actually solved, you can delete the user.

antonio*********@*****.***

CappielloAntonio commented 1 year ago

Hi @c0utta, thanks for your help. Could you try this new version of the app? If there are no further problems, you can delete my user from the server.

app-tempo-debug.zip

(apk files are not supported so I've zipped it and uploaded as a zip file)

c0utta commented 1 year ago

Yes, this version works.

I will keep your access open, just in case....

From: CappielloAntonio @.> Sent: Thursday, July 20, 2023 5:03:22 PM To: CappielloAntonio/tempo @.> Cc: c0utta @.>; Mention @.> Subject: Re: [CappielloAntonio/tempo] Selecting "Library" causes Tempo to halt (Issue #15)

Hi @c0uttahttps://github.com/c0utta, thanks for your help. Could you try this new version of the app? If there are no further problems, you can delete my user from the server.

app-tempo-debug.ziphttps://github.com/CappielloAntonio/tempo/files/12103245/app-tempo-debug.zip

(apk files are not supported so I've zipped it and uploaded as a zip file)

— Reply to this email directly, view it on GitHubhttps://github.com/CappielloAntonio/tempo/issues/15#issuecomment-1643424151, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A36PJ5GJOYTFWJSJ5IMQL43XRDNMFANCNFSM6AAAAAA2HQTOAA. You are receiving this because you were mentioned.Message ID: @.***>

CappielloAntonio commented 1 year ago

Okay, thanks a lot and again, thanks for your cooperation! I'm closing this issue now but feel free to reopen it should there be other problems or open a new one.

make-42 commented 1 year ago

I seem to be experiencing the same issue

make-42 commented 1 year ago

I'm using a Google Pixel 6 Pro on Android 14 (UPB5.230623.005). I've tried the APK on F-Droid, the APK in this thread and the latest CI build.

make-42 commented 1 year ago

For some reason tapping scan library in the settings makes this issue go away...

make-42 commented 1 year ago

However it does still crash when playing a track

CappielloAntonio commented 1 year ago

Hi @make-42, would it be possible for you to capture a crash log with the attached apk? Alternatively, would it be possible to have access credentials, even for a demo user, in order to reproduce the problem as quickly as possible?

app-notquitemy-debug.zip

make-42 commented 1 year ago

Well, in the meantime I changed from Subsonic to Navidrome and it now works fine (I just figured this out using your APK because I used Ultrasonic for testing Navidrome. The issue is with me using Subsonic. If you want me to host my Subsonic instance again for you you to try to debug I can do that.

CappielloAntonio commented 1 year ago

If that's okay with you, we could put the Subsonic instance back up and fix the bug. We would be doing a favor to those who still use Subsonic.

Tell me when I can send you my "trash" email so you can pass me the login credentials for a demo user. In case you need to create it, please make sure the error repeats and tell me how I can reproduce it.

make-42 commented 1 year ago

That's okay with me. You can send your email address to x@x.x and the instance will be up at https://x.x.x the issue only happens when playing a FLAC file from what I can understand.

make-42 commented 1 year ago

So this is weird. The debug APK you sent me works fine for subsonic but the APK from F-Droid doesn't.

make-42 commented 1 year ago

And this is an issue for all file types

make-42 commented 1 year ago

To reproduce: Using Android 14 (Google Pixel Beta) open Tempo, log-on and play a track. It crashes.

CappielloAntonio commented 1 year ago

Email sent!

CappielloAntonio commented 1 year ago

I'm publishing a new version of the app in pre-release, maybe you can test it with me too.

May I ask if the version of Tempo that had problems was downloaded from F-Droid using IzzyDroid's repositories? If so, when did you download that version?

I'm trying to reproduce the problem using the latest v3.5.3 release (whether signed for release on GitHub or not) but I can't. I can easily navigate the Library section and play any file. Could you possibly test that the problem also occurs with the test account?

Could it be that the problem occurred with versions of the app prior to the one released on August 25th? With the latest version published here on GitHub does the problem reoccur on Subsonic?

make-42 commented 1 year ago

It was downloaded using IzzyDroid's repositories. It's version 3.5.0. It works fine using the latest v3.5.3 release.

make-42 commented 1 year ago

Which is very weird. I even thought I tried the CI build too...

make-42 commented 1 year ago

And CI build works...

make-42 commented 1 year ago

Man what...

CappielloAntonio commented 1 year ago

IzzyDroid probably hadn't updated to the latest version yet when you downloaded the app. Just for the latest version, a couple of fairly important bugs that caused the app to crash had also been fixed. If a similar bug reappears, feel free to reopen the issue or create a new one.

make-42 commented 1 year ago

Yes. Thank you very much for your time.

CappielloAntonio / tempo

Selecting "Library" causes Tempo to halt #15