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

Rekado crashes on launch #33

Closed
neogohan324 opened this issue Dec 23, 2018 · 30 comments

Comments

Projects
None yet
@neogohan324
Copy link

commented Dec 23, 2018

Maybe this is unique to me, but Rekado crashes immediately upon launch. This is true of v2.4 and above. However, v2.3 and below work fine.

I'm using a Verizon Google Pixel on the latest Android and security updates (Android 9, December 9th update). I'm not rooted, nor is my bootloader even unlocked. This error also occurred on earlier versions of the OS prior to 2.5.2's release.

I've tried uninstalling completely (clear the app's cache, clear the app's data, uninstall the app) before reinstalling, but that doesn't fix it. I've also made sure to go into "App info" and enable storage permissions since the app crashes before it can request them. Not sure what else to check or where any logs may be stored that could be useful.

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2019

@neogohan324 sorry for late response. I am sure, that without root you can't get any system logs. Could you try one more time uninstall Rekado and remove Rekado folder in root of your file system?

@neogohan324

This comment has been minimized.

Copy link
Author

commented Jan 15, 2019

Done. I uninstalled Rekado. I then went to the root of the internal shared storage and deleted the "Rekado" folder which contained 3 payload bin files. I then freshly downloaded Rekado 2.5.2 from Github and reinstalled. Unfortunately, the application still crashes.

However, upon tinkering more, I got it to work. I went into system, applications, and then Rekado's information page. In the "Storage" pane, I hit "Clear storage" and "Clear cache". After that, it seems to work fine. I know I did that before in testing, but maybe just not in the right order or something.

Anyways, it appears to be cleared up after that. Thanks again for your work on this project!

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Jan 15, 2019

Which payloads have you used?

@neogohan324

This comment has been minimized.

Copy link
Author

commented Jan 15, 2019

Just ReiNX -- all versions at some point except for 1.7.1.

@MenosGrante MenosGrante added bug and removed question labels Jan 28, 2019

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 12, 2019

Should be resolved in 2.6 update.

@neogohan324

This comment has been minimized.

Copy link
Author

commented Feb 12, 2019

Strangely, 2.6 has reintroduced the issue. After upgrading from 2.5.2 to 2.6, Rekado now once again crashes on launch. If I revert to 2.5.2, the application starts without issue.

My only payload is ReiNX 2.0. Removing it and upgrading to 2.6 again doesn't resolve the issue -- still hard-crashes on launch. I assume that repeating the steps of wiping the cache and storage will resolve it, but let me know if there are some tests or diagnostics I can provide, since once I 'fix' the issue, I can't seem to replicate it.

Or let me know if this should just be dropped and tagged as "your phone is just weird, man".

@pinn73

This comment has been minimized.

Copy link

commented Feb 15, 2019

same issue here on s8+ 9.0. Cleared cache/ data and works

@5H00T4

This comment has been minimized.

Copy link

commented Feb 15, 2019

And same on a Pixel 2 when going from v2.5 to 2.6.
Clearing data and cache solves the issue.
Maybe just add a comment to the release page for now.
Not a huge issue by any means, but I was thoroughly confused.

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 15, 2019

Well, I will retest this issue one more time.

@MenosGrante MenosGrante reopened this Feb 15, 2019

@DavidOliM

This comment has been minimized.

Copy link
Contributor

commented Feb 15, 2019

I had the same issue here. I went to the app info and allowed storage access manually and it opened normally

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 18, 2019

Guys, I have just released another update - 2.6.1, which should fix this annoying issue. Could you retest this please?

@MenosGrante MenosGrante reopened this Feb 18, 2019

@neogohan324

This comment has been minimized.

Copy link
Author

commented Feb 18, 2019

Unfortunately, it does not. I updated to 2.6.1 from 2.6 and when that didn't work, I uninstalled and installed 2.6.1 'fresh'. Still crashes on launch. I have not cleared the cache or storage.

I also tried reverting to 2.5.2 then updating to 2.6.1. And while 2.5.2 still works fine, it crashes once again after the update to 2.6.1.

If there are any steps I can do to help troubleshoot, let me know.

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 18, 2019

Oh, try to uninstall application and remove Rekado folder from root of your storage. Then install as always.

@neogohan324

This comment has been minimized.

Copy link
Author

commented Feb 18, 2019

Uninstalled then deleted the "Rekado" folder at the root of storage. Reinstalled 2.6.1, and it still crashes at launch.

Note that I didn't use Androids "clear cache" or "clear storage" functions. Just manually deleted the folder.

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 19, 2019

Well, I will revert 2.6.1 update for now, thank you!

@neogohan324

This comment has been minimized.

Copy link
Author

commented Feb 19, 2019

No problem. Thanks again for all your work on this project!

@sruggier

This comment has been minimized.

Copy link

commented Feb 26, 2019

I updated from 2.5.1 to 2.6.1 and found that Rekado started crashing on startup after that. I reproduced the issue with logcat running and found this:

02-25 22:41:58.184  2378  2399 I ActivityManager: Start proc 11441:com.pavelrekun.rekado/u0a168 for activity com.pavelrekun.rekado/.screens.main_activity.MainActivity
02-25 22:41:58.449 11441 11441 D AndroidRuntime: Shutting down VM
02-25 22:41:58.450 11441 11441 E AndroidRuntime: FATAL EXCEPTION: main
02-25 22:41:58.450 11441 11441 E AndroidRuntime: Process: com.pavelrekun.rekado, PID: 11441
02-25 22:41:58.450 11441 11441 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.pavelrekun.rekado.RekadoApplication: java.lang.IllegalArgumentException: Theme with 'Castro' does not exist!
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5743)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.app.ActivityThread.-wrap1(Unknown Source:0)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:164)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:6494)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Theme with 'Castro' does not exist!
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.pavelrekun.siga.data.Theme$Companion.findById(Theme.kt:28)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.pavelrekun.siga.services.Siga.initValues(Siga.kt:43)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.pavelrekun.siga.services.Siga.init(Siga.kt:32)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.pavelrekun.rekado.RekadoApplication.configureThemeEngine(RekadoApplication.kt:34)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at com.pavelrekun.rekado.RekadoApplication.onCreate(RekadoApplication.kt:29)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5740)
02-25 22:41:58.450 11441 11441 E AndroidRuntime: 	... 8 more

Clearing cache didn't resolve the issue, but it started working after I cleared all of the application's data.

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 27, 2019

@sruggier Wow, that will help me a lot! I was fixing the wrong side then :D

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 27, 2019

I have made some changes for intialisation process for 2.6.1 and its available now again, but crash will probably persist for pre-2.6.1 versions. Should not occur in future releases.

@kuroyukihime0

This comment has been minimized.

Copy link

commented Feb 28, 2019

2.6.1 also crash on my mi6 android 8.0.
Here is the log,thx

java.lang.RuntimeException: Unable to create application com.pavelrekun.rekado.RekadoApplication: kotlin.UninitializedPropertyAccessException: lateinit property defaultSetup has not been initialized at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5884) at android.app.ActivityThread.-wrap1(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1690) at android.os.Handler.dispatchMessage(Handler.java:105) at android.os.Looper.loop(Looper.java:176) at android.app.ActivityThread.main(ActivityThread.java:6701) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:249) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:783) Caused by: kotlin.UninitializedPropertyAccessException: lateinit property defaultSetup has not been initialized at com.pavelrekun.siga.services.Siga.defaults(Siga.kt:64) at com.pavelrekun.rekado.RekadoApplication.configureThemeEngine(RekadoApplication.kt:33) at com.pavelrekun.rekado.RekadoApplication.onCreate(RekadoApplication.kt:29) at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5881) ... 8 more

@kuroyukihime0

This comment has been minimized.

Copy link

commented Feb 28, 2019

it also appears on my og Pixel 9.0,but after downgrading to 2.6,it works
it seems that some changes on submodule 'siga' casue that

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Feb 28, 2019

Oh, new day - new crash. Will fix it now.

@MenosGrante MenosGrante reopened this Feb 28, 2019

@n0101

This comment has been minimized.

Copy link

commented Feb 28, 2019

Just to add, I experience the same crash and same logcat error that kuro does on my pixel 2 xl 9.0 stock ROM, latest build. I am using a custom kernel and magisk but I don't think either would contribute to this.

@Cuphat

This comment has been minimized.

Copy link

commented Feb 28, 2019

I have a Pixel 2 XL and just installed Rekado for the first time (2.6.1) and it immediately crashes for me as well. Stock, unrooted Android 9.

@mackybean

This comment has been minimized.

Copy link

commented Mar 1, 2019

I have a Samsung Galaxy S9+ stock, unrooted on Android 9.0, and every version past 2.5.2 crashes upon launch for me. I have uninstalled, cleared data and cache, manually removed folder, reinstalled, done the hokey pokey... etc. and no dice.

@RussKay

This comment has been minimized.

Copy link

commented Mar 1, 2019

I posted in the other thread. Just posting here so others can see. Verizon Pixel 3, Android 9 Feb 5 updates. All stock. No modifications. 2.6 runs great. 2.6.1 crashes on launch. I also always do a clean install. I had issues with an older release and since then, anytime I upgraded rekado, it crashed on launch. If I removed the older version and the rekado folder first, then the new version would work. However, 2.6.1 crashes on launch no matter if it's a clean install or an upgrade.

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Mar 1, 2019

Looking at the logs I assume it will crash on every device :)

@MenosGrante MenosGrante closed this Mar 1, 2019

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Mar 1, 2019

I have pushed one more 2.6.1 build, that should fix all of this crashes, but it will probably persist for pre-2.6.1 versions. Should not occur in future releases.

@MenosGrante MenosGrante reopened this Mar 1, 2019

@neogohan324

This comment has been minimized.

Copy link
Author

commented Mar 1, 2019

All fixed here! It now installs and loads without issue. :)

@MenosGrante

This comment has been minimized.

Copy link
Owner

commented Mar 1, 2019

Yeah, I was debugging this build for a while, so should be fully stable now :)

@MenosGrante MenosGrante closed this Mar 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.