New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet. #21126
Comments
Any update with this issue? I have the same problem :) |
This issue seems to be happening on new version of fastlane |
We hit the same problem almost a month ago (16th February 2023) on fastlane 2.210.1 |
Someone found a solution? I'm having this issue with fastlane 2.206.2. |
Same issue on 2.211.0 |
Can confirm, I have the same issue on version 2.212.1 |
It seems like a pretty recent issue because I got the same issue minutes ago on version 2.210.1 |
I get the same issue and I suspect the Google Play API to be running a bit slow these days when uploading files and thus we hit the timeout set for the |
Same issue with version |
Can confirm that increasing the timeout solved the issue for me! Even with |
Could you share the timeout that fixed this issue? 👀 |
I tried 600s, but it actually ran in just 52s |
600s fixed this, but it finished in 29s 🤔 |
How can I change the timeout? |
You can add a |
Facing this issue too, does the fix need to be made on the library side and we should wait for a PR ? I'm not sure I understand what needs to be done here ! |
I think this is a temporary problem on the Google Play API and not in Fastlane |
I agree with you. For now, it is possible to increase the timeout to work around this issue. For those using the
|
Facing the same problem. Any workarounds? |
If anyone is facing this issue, this solution worked for me. I'm using Fastlane 2.210.1. |
Hi, im still facing this issue, and increasing timeout seems to not change anything.. Also, the "summary for supply" table is not taking count of timeout change does in fact. My lane :
Fastlane v: 2.212.1 |
Hey, I'm now consistently getting a timeout failure after 10 minutes. You can change the timeout to 100000 seconds if you want. It's either a timeout error or an auth error. I think Google is maybe hurting with the roll-out of Bard? ;) |
@LaurieScheepers same here, yesterday all was good, since few hours can't make any deployments |
It's definitely Bard. I bet you 1 trillion dollars the Google outages are going to come to light soon |
Well, I tried to take my aab and upload it directly in my track through play console and it's also stuck there. Well, i will retry later |
We have also increased the timeout to 600 and from today started getting this
|
I think it's hit and miss. I've just had 3 failed attempts, raised the timeout to |
I agree with the above statement. Gosh this is so annoying. I am now on my 10th attempt. :/ |
16 attempts and two hours later it succeeded |
Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet. |
My QA app 6 attempts passed |
Fixed too, but it finished in 56s |
[!] Google Api Error: Invalid request - APK has been signed in debug mode. |
New Issue Checklist
Issue Description
We're using the
supply
Fastlane action as part of a lane which is executed from our GitHub Actions CI workflow.supply
started failing with the error:Google Api Error: Invalid request - Some of the Android App Bundle uploads are not completed yet.
just today, seemingly only whenrelease_status
is set tocompleted
. I repeatedly tried to re-run the workflow, but had no success. Oncerelease_status
was changed to draft, the lane ran successfully. Perhaps this is just a momentary server blip, or a more significant error?Our Fastfile has otherwise run successfully every week for months with no modification.
Command executed
bundle exec fastlane distribute_play_internal
, which executesgrade
andsupply
(see Fastfile below).Complete output when running fastlane, including the stack trace and command used
I've omitted anything sensitive from this output and trimmed out a few repeated Gradle build log lines.
Environment
The text was updated successfully, but these errors were encountered: