PostprocessBuildPlayer not compatible with other plugins.

[Dgizusse]

The most common way to handle this is to include a PostprocessBuildPlayer_PlayGames file that handles the specific need of this plugin and include a generic PostprocessBuildPlayer that does this:

#!/usr/bin/perl


# Post Process Build Player -- Master 
# Searches for other PostprocessBuildPlayer scripts and executes them. Make sure the other script
# have a name suffix with an underscore "_" like "PostprocessBuildPlayer_AnotherBuild" or whatever.
#
# Based on script by Rob Terrell, rob@stinkbot.com

use File::Glob ':glob';

# Grab all the PostprocessBuildPlayer files
@files = bsd_glob( "Assets/Editor/postprocessbuildplayer_*", GLOB_NOCASE );

foreach $file( @files )
{
    if( !( $file =~ m/\./ ) )
    {
        system( "chmod", "755", $file );
        print "PostProcessBuildPlayer: calling " . $file . "\n";
        system( $file, $ARGV[0], $ARGV[1], $ARGV[2], $ARGV[3], $ARGV[4], $ARGV[5], $ARGV[6] );

        if ( $? == -1 )
        {
          print "command failed: $!\n";
        }
        else
        {
          printf "command exited with value %d", $? >> 8;
        }
    }
}

[btco]

Makes sense! I won't implement it exactly this way, but I'll make the plugin aware of other PostProcessBuildPlayer scripts that are in place. Thanks for reporting!

[kromenak]

I also ran into this issue - as @Dgizusse mentions, that script is generally considered the "right" or extendable way to make multiple PostprocessBuildPlayer scripts work together.

The documentation link for Unity is broken, but it's also possible to use the PostprocessBuild attribute in C# code to run code after a build, which I thought was pretty cool and also avoids any conflicts like this.

[tenpn]

My 2c is that even if your script does "something similar", because it's not exactly the same you're going to cause conflicts when new plugins are installed after you. This script line-for-line is pretty much standard now.

Kromenak's PostprocessBuild attribute is the way to go. The propeller sdk at http://developers.grantoo.com/ uses it if you want a reference.

[btco]

Ok, I'll do it this way then! I plan to fix this soon. Thanks for the feedback.

[internal tracking# 12836532]

[btco]

Fixed on 0.8.01.