Does something prevent the G. Play version to be updated?

[mredfield]

I was just wondering why it isn't. It is very convenient to have it over there.

I know it's a quite bunch of apps to keep it over there, but I guess it wouldn't hurt to keep the stable releases updated. Now that 1.7.0 is around the corner I believe it's a good chance to catch up.

If it's one of those things that developers don't have time, if you wanna do it, do it yourself, I wouldn't find it a problem at all to do it, I just thought there was a stronger reason behind that.

Thank you!

[digitall]

See http://forums.scummvm.org/viewtopic.php?t=12624

tl;dr: You should talk to our Android porters, but Google Play store was rejecting the newer version for some reason which was very unclear.

[icanntspell]

As far is I can find, the current status is

This has been due to Google Play (The new name for the Marketplace) giving very cryptic error messages when we
try to submit the upgraded build... and a lack of time for the porter to fight with the app store.

What is the preferred way to contact the Android porters? I too thought that posting in this subforum is a nice start.

What exactly is that cryptic message?

But the real question is, what is required to get some progress in this. With all the people wanting to help, and all the knowledge in the ScummVM user base it must be possible to get some movement in this issue.

Perhaps it is a good idea to make a sticky post about this problem in this subforum?

[digitall]

> What is the preferred way to contact the Android porters? I too thought that posting in this subforum is a nice start.

Not really. Most of the Android porters are very busy IRL and thus don't really have time, hence why this had not been fixed. fuzzie was looking at this.

The note about the cryptic message came from her. I have no idea of the exact message.

What is required is for one of the Android porters to have the time to sort this out. There are lots of people wanting to help, but few have the capability to help ie. lack of coding expertise / devices.

If you want to help, the following would be useful:
1. a Pull Request to replace the usage of aaptbuilder would be useful as that blocks the newest SDK usage
2. an implementation of Action Intents:
http://sourceforge.net/p/scummvm/feature-requests/686/
3. some debug work on the various bugs on OUYA:
http://sourceforge.net/p/scummvm/bugs/6522/

I suggest talking to fuzzie and the team in general on IRC at #scummvm on freenode:
http://wiki.scummvm.org/index.php/Proje ... RC_channel

[icanntspell]

If you want to help, the following would be useful:
1. a Pull Request to replace the usage of aaptbuilder would be useful as that blocks the newest SDK usage
2. an implementation of Action Intents:
http://sourceforge.net/p/scummvm/feature-requests/686/
3. some debug work on the various bugs on OUYA:
http://sourceforge.net/p/scummvm/bugs/6522/

How are these things related to getting updated Android packages to Google Playstore? If I understand correctly the problem is somewhere at uploading the packages to the store, not something with bugs/new features. It helps focusing on the task at hand.

[digitall]

icanntspell: You are right.. but fixing those things would be of help, and frankly your attitude just pissed me off quite badly.

To be clear, I am NOT the Android porter and personally, I do not particularly care about uploading packages to Google Play as I am quite happy to install or compile my own builds.

If you care about this issue for the release builds, go and talk to the porters on IRC as I indicated earlier.

[icanntspell]

I am just trying to shed some more light in one of the issues a lot of people are having trouble with. I will leave it at rest again, I have no intention to piss people off.