-
Notifications
You must be signed in to change notification settings - Fork 78
Cannot be run after compiling using gradle #51
Comments
Unfortunately, I haven't the time to keep it up to date, through an eventual rewrite is planned. To fix your current issue, just go into settings and give it the storage permission. It should work then |
Thanks for the quick answer, but you got me wrong. The storage permission is granted. It doesn't work though. FCs on launch. I'm not using your build which still works. I'm using my build of the latest commit in the indev branch which doesn't run at all. I wanted to check out what happened to the app after hundreds of commits since the latest release. |
@nico151999 Oh ok. I haven't touched the project in years, so I don't remember if the latest commit hat issues. Could you send a stack trace? |
How did you even get it to compile in the first place? App-theme-engine has since been discontinued and removed from repositories, and GEM depends on it. |
Sorry for not responding that quickly. I haven't had a deep look at the code so I didn't know how the build process works. I just thought it'd be enough to run envsetup.sh and gradlew build right after that. As I got a gradle error telling me there's an outdated plugin and I should export an environment variable, I just did so and it worked. What I also did was ignoring untranslated strings for the release build. But the build ran fine besides from that. The host runs Debian btw. |
@nico151999 Odd. The other issue open here is about why it can't build. What error are you getting on running? |
I can't debug right now, I'm not at home. Will be back next Saturday presumably. I'll create an adb logcat as soon as possible. |
Hi, I'm back :D I couldn't get my hands to a Linux machine so I tried creating a log using windows. Should be satisfying though ;) Seems like the Theme engine you wrote about is the actual problem why the app cannot launch. I'd really appreciate further development of the project as this player's got an absolutely awesome philosophy aiming to match the Google IO player's design. Here's the log:
|
@nico151999 Actually it looks like it is crashing due to loading. It tries to load in your music twice, causing the first crash. There seems to be another crash, where it tries to convert an album into a playlist In short, it's really broken. I might revive the project, as I really do miss that design |
I've just installed your version from the PlayStore. In case you're willing to continue the Project I'd have a recommendation: every time you click an album art to open an album specific activity there's a shared elements transition. However, there are some graphical glitches. I've faced such issues already and I could solve them by removing the padding from the view element. In your case this would be the transitioning text. Adjusting text appearance settings may also cause such glitches... |
@nico151999 Alright, that's good to know. Thanks! |
I love the design of the player, so it's a real pitty it seems to have stopped being developed. Anyway, I've just tried compiling it. However, after installing it on the phone I get FCs even though storage permissions were granted. I guess that's a common issue so maybe someone can help :D
Thanks a lot in advance!
The text was updated successfully, but these errors were encountered: