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

[BUG] App crashes immediately on launch (Version 6.1.0, Android) #93

Closed
Gituser436 opened this issue Dec 3, 2024 · 13 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@Gituser436
Copy link

Description:
In version 6.1.0 of the Android app, the application crashes immediately upon opening. This happens consistently every time I try to launch the app.

Steps to Reproduce:

  1. Install version 6.1.0 of the app.

  2. Open the app on a device running Android 14.

  3. Observe that the app crashes immediately.

Expected Behavior:
The app should launch without crashing.

Environment:

App Version: 6.1.0

OS: Android 14

@Gituser436 Gituser436 added the bug Something isn't working label Dec 3, 2024
@DatL4g
Copy link
Owner

DatL4g commented Dec 3, 2024

Should work as expected on Android 14, tested on Google Pixel 9 Pro and Emulators.

Since it happens before the app fully launches I don't have any logs.
To be able to fix this issue I need the error log, if you don't know how to do this, here a small and easy explanation that should do the job:

  • Close the app fully
  • Install adb on your system
  • Connect your smartphone using USB
  • In CMD or a terminal (depending on your OS) call: adb devices
    • Your device should be listed then
    • If not make sure to follow any instructions popping up on your smartphone
  • Then call: adb logcat -c to clear previous logs
  • Finally call: adb logcat and start the app

@Gituser436
Copy link
Author

Should work as expected on Android 14, tested on Google Pixel 9 Pro and Emulators.

Since it happens before the app fully launches I don't have any logs. To be able to fix this issue I need the error log, if you don't know how to do this, here a small and easy explanation that should do the job:

* Close the app fully

* Install `adb` on your system

* Connect your smartphone using USB

* In CMD or a terminal (depending on your OS) call: `adb devices`
  
  * Your device should be listed then
  * If not make sure to follow any instructions popping up on your smartphone

* Then call: `adb logcat -c` to clear previous logs

* Finally call: `adb logcat` and start the app

I just wanted to follow up and confirm that I have tested the feature on three Samsung devices: two smartphones and one tablet. All devices are running One UI 6.1, and unfortunately, the issue persists across all of them. The feature still doesn't work as expected.

Additionally, I’ve tried clearing the app's cache, deleting the data, and even uninstalling and reinstalling the app, but the issue remains unresolved.

@DatL4g
Copy link
Owner

DatL4g commented Dec 3, 2024

As I said nothing I can do here without the logs, tested and works on all my devices.

@Gituser436
Copy link
Author

As I said nothing I can do here without the logs, tested and works on all my devices.

12-03 04:38:28.952 1031 1031 E audit : type=1327 audit(1733197108.947:6954): proctitle="dev.datlag.burningseries"
12-03 04:38:28.954 30039 30039 E g.burningseries: No implementation found for java.lang.String dev.datlag.burningseries.Sekret.githubClientId(java.lang.String) (tried Java_dev_datlag_burningseries_Sekret_githubClientId and Java_dev_datlag_burningseries_Sekret_githubClientId__Ljava_lang_String_2) - is the library loaded, e.g. System.loadLibrary?
12-03 04:38:28.954 30039 30039 D AndroidRuntime: Shutting down VM
12-03 04:38:28.955 30039 30039 E AndroidRuntime: FATAL EXCEPTION: main
12-03 04:38:28.955 30039 30039 E AndroidRuntime: Process: dev.datlag.burningseries, PID: 30039
12-03 04:38:28.955 30039 30039 E AndroidRuntime: java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String dev.datlag.burningseries.Sekret.githubClientId(java.lang.String) (tried Java_dev_datlag_burningseries_Sekret_githubClientId and Java_dev_datlag_burningseries_Sekret_githubClientId__Ljava_lang_String_2) - is the library loaded, e.g. System.loadLibrary?

Repository owner deleted a comment from Gituser436 Dec 3, 2024
Repository owner deleted a comment from Gituser436 Dec 3, 2024
Repository owner deleted a comment from Gituser436 Dec 3, 2024
@DatL4g
Copy link
Owner

DatL4g commented Dec 3, 2024

Does the same happen when you uninstall the app and then install the 6.0.0 one?

@Gituser436
Copy link
Author

Does the same happen when you uninstall the app and then install the 6.0.0 one?

Version 6.0 runs perfectly!

@DatL4g
Copy link
Owner

DatL4g commented Dec 3, 2024

I added android-samsung to the releases, that should work for you

@Gituser436
Copy link
Author

Does the same happen when you uninstall the app and then install the 6.0.0 one?

Version 6.0 runs perfectly!

I added android-samsung to the releases, that should work for you

It works. Thank you very much for the quick support.

@Panagel
Copy link

Panagel commented Dec 3, 2024

Uploading log.txt…

Pixel 6a
Android 14

Same behavior

@DatL4g
Copy link
Owner

DatL4g commented Dec 3, 2024

@Panagel use the Samsung version as well.

It's a Kotlin bug which has already been reported

@DatL4g DatL4g closed this as completed Dec 3, 2024
@DatL4g DatL4g pinned this issue Dec 3, 2024
@ngelus
Copy link

ngelus commented Dec 5, 2024

Also didn't work on my OnePlus 11.
The Samsung release die work tho 👍

@High-village
Copy link

ye app only crashes since 6.1 cant use it anymore

@High-village
Copy link

ok so the samsung version works on my rog phone, on the TV tho the normal signed one is fine. I noticed on the tv everything works okay so far just not the home screen basically bc I think you made it so only touch inputs are recognized there to scroll through the newest stuff. so you have to directly know which series you wanna watch and search for it directly then you can navigate again on the page of the series itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants