You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know what my device, OS and App Manager versions are
I know how to take logs
I know how to reproduce the issue which may not be specific to my device
Describe the bug
It seems that Pithus Report card inside Scanner page is not returning any info back but "Not Available". Since Pithus is still in Beta themselves, I am guessing they have changed the API access?
To Reproduce
Go to a random app in the app list
Click on Scanner
Scroll (if needed) to Pithus Report card
Error : Not Available
Expected behavior
Getting results from Pithus Security platform.
Screenshots
No response
Logs
No response
Device info
Device: Samsung s22U
OS Version:A 14 (OneUI 6.1)
App Manager Version: 4.0.0 beta01
Mode: Non Root
Additional context
No response
The text was updated successfully, but these errors were encountered:
I understood. So it is not automatically uploading (or initiating a dialog for...) the app if it is not in their DB - like in the implementation of Virus Total. This is why it shows Not Available.
Thank you for your answer. You are correct, once I uploaded the apk it returned the link in the scanner.
Pithus does not provide an API. So, App Manager can only check for reports by appending the APK hash to https://beta.pithus.org/report/. Technically, it might be possible to upload the APK, but I can't do this without prior permission from them.
Please check before submitting an issue
Describe the bug
It seems that Pithus Report card inside Scanner page is not returning any info back but "Not Available". Since Pithus is still in Beta themselves, I am guessing they have changed the API access?
To Reproduce
Go to a random app in the app list
Click on Scanner
Scroll (if needed) to Pithus Report card
Error : Not Available
Expected behavior
Getting results from Pithus Security platform.
Screenshots
No response
Logs
No response
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: