AndroidX Tracking Bug: Support ArrayBuffers in WebMessage API [251152171]

Fixed

Feature Request

Status Update

No update yet.

Description

pb...@google.com

created issue #1

Oct 5, 2022 02:06PM

This is an AndroidX-side tracking bug for https://crbug.com/1023334

Design doc: https://docs.google.com/document/d/1nsQnwwY43OuA4PsSaMioiKA0c_M1eV1XX2q15YFA7cI/edit#heading=h.grah444pqbxl

Comments

li...@microsoft.com <li...@microsoft.com> #2Oct 6, 2022 01:46AM

Converting to an enhancement request.

ap...@google.com <ap...@google.com> #3Oct 6, 2022 01:15PM

Any update on the status of this enhancement?

na...@google.com <na...@google.com> #4Oct 24, 2022 01:37PM

Fails for UrlFetches to far-away places like China. Making it configurable would be useful -- or reporting it as an actual timeout would help as well.

pb...@google.com <pb...@google.com> Apr 26, 2023 02:12PM

Accepted by li...@microsoft.com.

ap...@google.com <ap...@google.com> #5May 17, 2023 01:28AM

I also need this feature, any update on the status ?

jo...@gmail.com <jo...@gmail.com> #6May 18, 2023 10:35PM

Any update?

ap...@google.com <ap...@google.com> #7May 26, 2023 04:38PM

Marked as fixed.

Any update on this feature request, Its really important for us to have this feature

pr...@google.com <pr...@google.com> #8Jun 8, 2023 01:30AM

I'm seeing the opposite issue lately. The UrlFetchApp.fetch call is taking far too long, the worst today is 257sec. I'd like to set a 10-30sec timeout and stop these calls from using up all of my time-based quotas. There must be an issue with this function as manually calling these urls is much faster, typically a second or less.