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

unable to upload to google play #459

Open
ghost opened this issue Oct 3, 2024 · 4 comments
Open

unable to upload to google play #459

ghost opened this issue Oct 3, 2024 · 4 comments

Comments

@ghost
Copy link

ghost commented Oct 3, 2024

Using the current toolchain ist's not possible to upload an app to goole play any more.

It is possible to compie a working app for ANDROIDAPI=34 when you use
./sdkmanager "platform-tools"
./sdkmanager "build-tools;28.0.2"
./sdkmanager "ndk;26.1.10909125"
./sdkmanager "extras;android;m2repository"
./sdkmanager "platforms;android-34"

You need to convert the APK to an AAB to upload the app to goole play.

The created app (any demo app will do) works in the emulator and on real devices, but after uploading to google play the app is rejected after some days due to being not responsive.

I'm feeling like this is the end of line for the current build system :(

@ghost ghost changed the title unamle to upload to google play unable to upload to google play Oct 3, 2024
@mgorges
Copy link
Contributor

mgorges commented Oct 4, 2024

Maybe it is time to retire LambdaNative, which is sad, but all good things must end eventually. Was it a good idea: yes, did some valuable things come from it: also yes, but was it ever sustainable: no - the language is too niche, it was almost entirely built and maintained by our research team, and we never reached a critical mass of community members contributing to it.

Unless @ddunsmuir has the capacity and resources to work on replacing the Android toolchain, I don't see a way forward. I don't use Android in my research program, so I can't justify dedicating time to it as this is not academically productive for me. Other parts of LambdaNative may continue (desktop-OS and iOS to some degree), but as you wrote, maybe this is the end of the line for Android and soon other pieces, too. Sorry!

@ddunsmuir
Copy link
Contributor

Yes, unfortunately I don't have the resources to focus on that either at this time. As a research team we are using apps installed manually outside the app store and are not focused on publicly available apps at this time so it's unfortunately not a priority to fix this to be able to upload to the Google play store. Possibly in the future - but it might also make sense to rebuild some of our apps on a more modern platform.

@karliwalti
Copy link
Contributor

I was surprised to read this sad news on an unrelated issue :-(
You can be proud that this has been running successfully for over 10 years and supported so many research projects!

@ghost
Copy link
Author

ghost commented Oct 7, 2024

Sad as it is, this is not the first project giving up on Android due to Googles hostility. https://github.com/jasonelle/jasonelle/ is the other project I was looking into, but it also dropped Android. Flutter may be a way to go, but I wonder if it is possible to make a Lambdanative_to_Flutter converter and let others handle the OS specific part? For Racket 6.2 there was Walesong, a Racket to JS compiler which worked quite well (but is unmaintained since ages)

IMO Lamdanative was and still is a great tool and way easier to handle than all the other platform independent options.

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

No branches or pull requests

3 participants