Package to Android stopped working on 4.7.6

Hi guys,

My game was packaging to Android fine (when Shipping selected) but now it just comes up with Packaging Failed.

Have made no major changes to the game, just a couple of minor tweaks, but I did update the latest hotfix yesterday, so it would seem like this has broken it somehow.

The game is basically finished and I already had to rebuild it 4.7 after packaging issues turned up when converting it from 4.6 so I will probably explode if another update has broken the game.

Any thoughts or ideas?

Cheers

Tom

By the way, launching onto the phone works just fine - something is obviously just going wrong during the packaging process. I think…

Tom

Right so this is kind of working now. Unticked FOR DISTRIBUTION and changed build config to DEVELOPMENT and the packaging was successful.

Going to try packaging for SHIPPING now.

Anyone aware of any issues like this or is it just me???

Hi obitomkenobi ,

We will need your failed build output logs to confirm, but if you are seeing something along the lines of:

C:\NVPACK\android-sdk-windows\tools\ant\build.xml:1151: C:\Users\UserName\Documents\Unreal
Projects\Test2\Intermediate\Android\APK\Sing.keystore
(The system cannot find the file
specified)

Then your problem is lack of Sing.keystore file. Please see this forums thread for a more thorough explanation.

If you’re seeing references to ‘proguard’ in your output logs, it may be related to this known issue (Scroll down to the third answer for the clearest details.)
However, that should have been fixed in the subsequent releases, so attaching your failed build output logs will help the most so we can re-open the issue if you’re still seeing it.

Thanks!

Hey,

Thanks for that, it actually helped a lot! Got it to package successfully now as I included my Google Play License Key, which was blank before.

Fingers crossed all is working now!

Thanks again

40266-google_play.jpg

Spoke to soon. Game now crashes on launch on mobile. So basically it works fine it Distribution is unticked, but I won’t ever be able to upload it to Google play. Or it crashes everytime with Distribution ticked.

This is getting stupid now. Spend ages building a game but can’t actually do anything with it.

Is this because I am trying to play the proper “shipped” version of the game on my phone but it wasn’t downloaded from Google play? Or is it actually a bug or something?

Cheers

Me again! So the installed version crashed even when I went back to normal Shipping mode with Distribution unticked, which was weird as that was working fine before.

Turns out that removing the Google Play License Key actually did the trick, so installing direct to your phone with that included seems to cause a crash.

Hi obitomkenobi,

Can you include logcat logs for your device crash to this thread? Also, what device are you using, and how are you deploying the project to your device?

Further, in order to rule out your project as a probable cause, can you package the Tappy Chicken sample project for development and ETC1, and deploy it to your device and see if you get a similar crash?

Thanks!

Hey,

How do I get those logs? I am using a Nexus 6.

Tried Tappy Chicken and that just fails to package so cannot even test it on my phone. Didn’t change a single setting after opening up the project. All going really well this!

Here is a screenshot of the log.

You get logs for your device from the Android Developer tool called ‘monitor’. Here’s the section about debugging, here’s how to read and write logs, and here is some command lines for logcat. You can use the command lines or if you want to shortcut monitor for later use it will be inside your NVPACK, somehere like this: C:\NVPACK\android-sdk-windows\tools

However, if you’re completely unable to package Tappy or anything, that means your SDK probably isn’t set up right. Please include the entirety of the failed build output logs for Tappy to this thread as a txt file so I can check the errors.

I can still package my game though so shouldn’t that fail too if there is a problem with the SDK?

Anyway, here is the failed Tappy log. I did try it again to be sure and it was the same result.link text

Hope you can help!

Tom

Hi,

You’re still getting this error:

C:\NVPACK\android-sdk-windows\tools\ant\build.xml:1151: C:\Users\me\Documents\Unreal
Projects\TappyChicken1\Intermediate\Android\APK\UE.keystore
(The system cannot find the file
specified)

Here is the specific part of the forums thread above that explains where to put your keystore file. Please have a look and see if that helps.

Oh right I didn’t realise I had to set that up for Tappy Chicken as well. Got that all set up on my game, it uploads to the Google Play store so everything is fine with that. But the game still crashes shortly after launching.

Will try and run Tappy with the keystore info included and let you know how it goes. Assume if it works then the issue will be something to do with the game itself.

Thanks

Tappy is deploying now. My game still totally not working at all. Next steps?

Ok, is it failing to build, or is it packaging and then crashing on the device? Can you link to this thread build fail output logs if it is the former, and logcat logs if it is the latter?

Just guessing, but when you moved from 4.6 to 4.7, did you make a copy of your project or did you choose the convert in place option? Sometimes it does strange things to blueprints, among other things. Nothing for it now, but when you update (which is coming, 4.8 is on its way), always just make a copy.

I did previously have that issue when converting but rebuilt the project from scratch in 4.7 so I don’t think it would be that.

It builds fine now, but when launching onto the device it crashes pretty much straight away.

If I just launch onto the device (rather than installing the game) then it works fine, so I can only assume something is happening during the packaging/installation process.

Which link did you want me to go to?

Thanks

I think I might have figured it out, have been going through the game removing things and trying to see if something like a texture was breaking the game and it turns out that it has been crashing because of a lighting error.

It is an error with overlapping light and I completely forgot about it and didn’t fix it, fixing that issue now has got the game working again when package for Development, just need to test Shipping now.

Strange that the lighting error only crashes the game when it is packaged and not when it just launches from UE4.

Hoping that this is all ok, will confirm once I have tested the shipping version.

Thanks for you help though!

Tom