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

Some issues with building rebol-server apk #11

Open
noncom opened this issue Jan 18, 2023 · 0 comments
Open

Some issues with building rebol-server apk #11

noncom opened this issue Jan 18, 2023 · 0 comments

Comments

@noncom
Copy link

noncom commented Jan 18, 2023

I have followed the instructions outlined in the https://github.com/metaeducation/rebol-server readme to get some Rebol on my phone, but I have encountered a number of issues. I was able to resolve some of them, and according to my experience, the build-apk.bash script needs to be updated. But in the end rebol-server still doesn't work.

Here is the list of changes I had to make to be able to build the apk:

  1. Though the script kind of checks for dx vs dalvik-exchange, it still just hardcodedly calls for dalvik-exchange on line https://github.com/metaeducation/rebol-server/blob/master/build-apk.bash#L130. I had to change that to calling dx instead.
  2. The signer that Termux currently installs with pkg install apksigner is likely the standard one, not the old one. So the script tries calling the https://github.com/metaeducation/rebol-server/blob/master/build-apk.bash#L58 command, but fails because there's no PASSWORD in the environment. Instead it looks like it should take it from the variable defined in the script. So I had to change this line to: APKSIGNER_CMD="apksigner sign --ks-pass pass:$PASSWORD --ks $KEYSTORE bin/$NAME" to make it work.

So it feels like the script should be updated with these changes (but I'm not sure, it's not the toolset that I work with usually).

After that I've got the apk and was able to install and run it. But at this point I'm getting another error which I don't know how to solve, see the screenshot below. My Android version is 12, and I have given the app the full storage permission.

Is there anything I can do to solve this?

photo_2023-01-18_04-48-48

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

1 participant