Closed jimmymjing closed 2 years ago
I'm not sure whether it's possible to do debugging with an asset pack that's not "install-time" .. it's most likely hanging because it's trying to get the asset pack status from the play services and if you're local-debugging, this won't be present. We can probably change this to detect the issue and return control to ActionScript but I don't think you'll ever find the status of 'completed' for this..
Hi, I find that we need to add local-testing -- java -jar bundletool-all.jar build-apks --bundle=path/to/your/bundle.aab \ --output=output.apks --local-testing
. This param is not available with adt -installApp
.
Hi @jimmymjing - just to check, when you manually create the APKs file like this, then it works again? I'm wondering whether we should update the installation of AAB files to always use the local-testing option, I'm not sure there's any adverse affects for people who don't want to use this..
Hi, with this Param set, I'm able to do local testing for the debug version aab with PAD. Maybe we could add it also as a param for adb?
Yes I think it looks like it's best for us to just always enable this .. will update the bundletool jar as well of course.. thanks
@marchbold @ajwfrost Hello, I'm debugging the aab with Asset Delivery and find that my program stops when I call any functions on the
PlayAssetDelivery
instance. (getAssetPackStatus
,getTotalBytesToDownLoad
...). Here's the code:(FYI)
fetchAssetPack
first, and it also stops my program.distriqt|AndroidRuntime|System.err
, and I'm not seeing any error outputs.Thanks in advance!