Should I be concerned about this or is it something on the game maker developers part? If so, sorry about the post and hopefully, we will have an update soon. Thank's!
Will it be awhile before it's included in the stable build (I have a time limit to fix my app. ) or should I download the early access game maker to patch my game up? Thank's for all the hard work btw! Sounds like it was a tough issue to work out.It's live on Early Access now (1.99.493)
Gotcha. If I may recommend, a new separate icon for the early access version of game maker would be very useful. The current icon appears to be identical with only a blue dot on the bottom left side (making shortcut icons on windows cover it with a shortcut arrow) and it may be better to just do a reverse icon or something of green and black instead of black and green. This would help prevent others from trying to open stable built games with the unstable version before backing up. Thank's again for all your work man! We appreciate you!Early Access is a separate install, so it should be fine (as long as you change the file paths etc). I would definitely recommend backing up your project before hand though just in case.
If you will, link me to the topic in which PlayLight mentions all these things and I'll give them a go. Like I said, stable version works fine. This only happens in the early access version.did you install all that playlight mentioned in the sdk manager, as that's important you have them all ticked, i have the google play services ext in my tree and can compile but i don't have the GooglePlayLicensingAsExt as i dont use anything of googles, much better using heyzap you get to use all ad providers and can set it up so you have lots of providers competing giving you much better returns on ads that way.
EDIT im also using jdk1.8.0_31 so check what yours is
Made sure I had everything downloaded and even adjusted the settings of my Game Maker. Same error during compile.https://forum.yoyogames.com/index.php?threads/android-apk-jarsigner-unable-to-sign-jar-java-util-zip-zipexception-invalid-entry-compressedsize.1776/#post-15486 its post number 5 think it cover everything apart from the bug with needing bluetooth ticked in global game settiing as i only reported that about a week ago and yoyo have been super busy putting more important stuff in this release.
**RESOLVED!...sort of**Yeh the EA uses 12b so you should be fine using that.
Can you try turning on Bluetooth a second?
We are getting a few users with projects failing because it is not enabled. Obviously this is not ideal and we are aware of the issue.
i got same problem. what can we do? i got 3 dev account and different licence keys.**RESOLVED!...sort of**
I created a test game from scratch and used the google play services ext. Everything checks out ok! I then added the license ext and it's always a no go. Deleting it from the extension didn't work until I cleared the cache and so on, but after that, everything worked fine. Bluetooth had nothing to do with the issue. Seems like you guys need to work on the compatibility with the new game maker and the GooglePlayLicensingAsExt. I can do without the license extension for now since my game is just a free game with ads, but it's pretty important to have once I start putting prices on some games in the future. Hope I've helped you guys out in your bug hunt, and thank you to everyone who's tried to help me here! I really appreciate it!
Look's like I'll need that license key thing to work after all. Just tried to upload my new APK over my existing one without using the extension. I got this error from the APK upload on Google Developer Console:
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ KEY REMOVED SO NOBODY CAN SEE IT ON HERE AT YOYO ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[KEY REMOVED SO NOBODY CAN SEE IT ON HERE AT YOYO ]
Hope a fix for the license stuff is put out soon. :-/
That appears to be exactly what it was. I didn't take in to consideration that Game Maker EA didn't use the same keystore file. Thank's bud! As for the license extension, hope to hear some news on a fix soon! I've got a 99 cent game just around the corner.When you went to the Early Access version, did you pass over your keystore and input the correct password etc that you used when you published it?
The error message right there is telling you that the keystore is not the same as the uploaded one.