Have you looked at the install log on the Mac? Does the package fail when manually installed? The jamf log is all well and good, but you probably want to have a physical test case that you can look at the local logs of to work out what is going on.
What version are the air's on, 10.13? Try using packagebuild (built-in) over composer to create the package, note I saw this returned;
productbuild --component /Applications/minecraftpe.app ~/Desktop/minecraftpe.pkg
productbuild: Adding component at /Applications/minecraftpe.app
productbuild: Inferred install-location of /Applications
productbuild: Wrote product to ~/Desktop/minecraftpe.pkg
productbuild: Supported OS versions: [Min: 10.13, Before: None]
defaults read /Applications/minecraftpe.app/Contents/Info.plist LSMinimumSystemVersion
10.13
Less likely;
- Jamf Admin can calc the checksum for you
- Check the package doesn't have OS restrictions.

All else fails, use quickpkg from the legend..
https://github.com/scriptingosx/quickpkg
quickpkg /Applications/minecraftpe.app
Removal Script
#!/bin/zsh
# Delete Core App
rm -rf "/Applications/minecraftpe.app"
exit 0
Instead of using composer to make a pkg file.
I install it to the machine, do not launch it, drag it in to composer.
Permissions - Set the owner to root / group to wheel, and the rights to Mode 775
Make a DMG instead of pkg.
Create a policy to run that script to remove the current version, and extract the version you wish to install.