-
Notifications
You must be signed in to change notification settings - Fork 99
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
Allow installation of ChromeOS builds if owned by the user's Google account #980
Comments
I actually have no idea how to download Chrome OS versions via the play api client used by the launcher. I didn't buy that version of the game and are not eligible to download it What playstore identifier is the chromeos version using?
If it's different I might be able to provide you something to test if you can download it, since other non chromeos android games download just fine with a search and replace There are almost zero info about the chromeos version if no chromeos device has ever been used. Playstore only writes "sold seperately" |
I do not currently have access to the ChromeOS version either, and was partially making this issue to prod on whether you had any knowledge of it either |
I assume chromeos trial is already different on chromeos. If the trial works then you can try it on the launcher before actually purchasing the upgrade. |
Me too, I'm just ignoring the bug and move on. Nothing easier than that. |
I will attempt to implement this feature at a later date as a pull request |
Is your feature request related to a problem? Please describe.
This request is related to the sprint strafing issue which has been present since 1.19.50
Describe the solution you'd like
As a workaround to MCPE-170810, would it be possible to add a setting which pulls the APK file for the ChromeOS build of the game if the currently signed in Google Play account owns it? The issue reportedly does not exist on ChromeOS, despite simply being a modified version of the Android port.
This would greatly help to overcome this incredibly annoying issue in the meantime while we wait for Mojang to (hopefully) fix it themselves, although I don't have my hopes up given that it has been present for about a year and a half.
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: