Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsafe app? #6

Open
Sushnata1 opened this issue Sep 18, 2024 · 9 comments
Open

Unsafe app? #6

Sushnata1 opened this issue Sep 18, 2024 · 9 comments

Comments

@Sushnata1
Copy link

Sushnata1 commented Sep 18, 2024

Google play protect flags this app as unsafe when I try to install it in my Samsung Galaxy A31 phone. When I install it anyway it gets installed but when I try to open it, it closes automatically and shows the following. :
Screenshot_20240919-005809_Device care.jpg
The following is my system software information. :
Screenshot_20240919-010648_Settings.jpg
Why does it happen? Can it be fixed?

@RainbowC0
Copy link
Owner

RainbowC0 commented Sep 20, 2024

This app has a target sdk 30 (Android 10), lower than Android 12, so google play protect did that. But that's can get ignored.

I'm afraid of improving the target sdk because the higher it is, the more limited permissions there are. Even one contributor had tried to decline the target sdk while I kept it still. 😂

The reason for the crash varies in different phones and is hard to fix without crash infos. Maybe you encountered the situation similar with #3, and a new version 0.1.3 is out. You can have a try.

@Sushnata1
Copy link
Author

In fdroid?

@RainbowC0
Copy link
Owner

In fdroid?

Yes.

@Sushnata1
Copy link
Author

Screenshot_20240920-195926_Device care.jpg

Still the same problem

@RainbowC0
Copy link
Owner

RainbowC0 commented Sep 20, 2024

The new version is 0.1.3 rather than 0.1.2 😓, please refresh F-Droid first.
IMG_20240920_223425

@Sushnata1
Copy link
Author

This time I downloaded v0.1.3 but still no luck Screenshot_20240921-054711_Device care.jpg

🥲

@RainbowC0
Copy link
Owner

Please check if TermuC has the Access all files permission, and install Termux if necessary.

Or please feedback the log info through Termux:

  1. Install adb in Termux: (one-off)
pkg i android-tools
  1. Enable "Wireless Debugging" on your device in Settings -> Developer Options.
  2. Pair your device via pairing code. Use "Split Window" mode to open Termux and Wireless Debugging Interface together. Run adb pair 127.0.0.1:[pairing ip port] [paring code] to pair your device.
  3. Run adb connect 127.0.0.1:[ip port] to connect to your device.
  4. Run adb logcat -c to clear current logs and then run adb logcat -v color *:E to record error logs.
  5. Then open TermuC. If it crashed, some according error information will get printed in Termux. Press Ctrl + C to finish the recording process. Please give me a screenshot of these or paste them here.

See also:

@Sushnata1
Copy link
Author

I will not be able to do this now. I will try after a week

@RainbowC0
Copy link
Owner

I seem to know that in my phone, iQOO Neo 5 SE, it will automatically request the RUN_COMMAND permission after crashed 😂. In the new version v0.1.5 I have fixed the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants