使用API​​将OBB扩展文件上传到Google Play草案工件 [英] Upload OBB expansion file to Google Play draft artifact using API

问题描述

我正在尝试使用Google Play API将主要的OBB扩展文件上传到Google Play商店( https://developers.google.com/android-publisher/).我目前正在使用此处所述的edits.apks.upload功能成功上传正确的APK文件( https://developers.google.com/android-publisher/api-ref/edits/apks/upload ).

I am trying to upload an main OBB expansion file to the google play store using the Google play API (https://developers.google.com/android-publisher/). I am currently successfully uploading the correct APK file using the edits.apks.upload functionality described here (https://developers.google.com/android-publisher/api-ref/edits/apks/upload).

文件最终上传到商店后，它会在发行管理/工件库"下的草案工件部分中结束:

When the file is finally uploaded to the store, it ends up in the Draft Artifacts section under Release management/Artifact Library: Artifact Library

不幸的是，当我尝试使用edits.expansionfiles.upload HTTP请求将扩展文件上传到此文件时，返回以下错误:{找不到以下APK版本代码:480.令人困惑，因为我可以看到APK在草稿中，但似乎没有在可修改的APK中列出.

Unfortunately, when I try to upload the expansion file to this using the edits.expansionfiles.upload HTTP request, the following error is returned: { The following APK version codes could not be found: 480 }. This is confusing as I can see that the APK is in draft artifacts, but it doesn't seem to be listed in the APKs available to be modified.

有人对我如何将OBB上传到Google Play商店上的工件文件草案有任何建议吗?我可以只将OBB上传到发布轨道中使用的APK吗?

Does anyone have any suggestion for how I might upload an OBB to a draft artifact file on the Google Play Store? Can I only upload OBBs to APKs being used in a release track?

推荐答案

这是当前版本的Google Publisher API中的错误.已经向Google的相关人员报告了此消息，但修复可能需要一段时间.

This is a bug in the current version of the Google Publisher API. It has been reported to the right people at Google, but a fix could take a while.

目前，您无法使用API​​将OBB添加到草稿工件中.抱歉.

At the moment you cannot add OBBs to draft artifacts using the API. Sorry about that.

这篇关于使用API​​将OBB扩展文件上传到Google Play草案工件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！