Google Picker API Producing Different Requests

77 views
Skip to first unread message

Liam Monninger

unread,
Jan 14, 2022, 6:45:59 PM1/14/22
to google-c...@googlegroups.com
Hi, all!

The Google Picker API is producing requests of different shapes for different users in my web application. This prevents some of my users from using the Picker at all. I do not know why. I've mad a more detailed SO post about this here

Any help would be much appreciated!

Best,

Liam Monninger

he/him

Integration Engineer

concentric

 
 
 
4152693709
linkedin
Linkedin
concentric.io
5150 Carillon Point, Kirkland WA 98033

Resist Printing - Please consider the environment before printing this email. View our sustainability initiatives here.

Platinum Green Business Certified   Carbon Fund Carbon Free Partner   The Climate Pledge

CONFIDENTIALITY NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by replying to this message and then delete it from your system. Thank You.

goya

unread,
Jan 17, 2022, 12:10:01 PM1/17/22
to Google Cloud Developers
Hi,

To get help on technical issues regarding the Google Picker API, it is needed to create a SO case as you already did.

The link you attached seems to not be correct, but if you are referring to this question [1] there is a comment requesting information for further troubleshooting.

If that's not the question you are referring to, make sure it has the "[google-picker]" tag.

[1]: https://stackoverflow.com/q/70717675/8935548

Liam Monninger

unread,
Jan 18, 2022, 11:07:39 AM1/18/22
to goya, Google Cloud Developers
Yeah, it does look like I grabbed the wrong link. And, you are right, this is it: https://stackoverflow.com/q/70717675/8935548



--
You received this message because you are subscribed to the Google Groups "Google Cloud Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-dev/16842216-8254-4edd-8a26-1a03f0f79302n%40googlegroups.com.


--

Andrew (Google Cloud Platform Support)

unread,
Jan 18, 2022, 1:42:35 PM1/18/22
to Google Cloud Developers
Hi,

Maybe a quicker way to get the right attention for you issue is by submitting Public Issue on Issue Tracker [1]. As Goya mentioned, SO and Issue Tracker are the best places to get technical support on a specific issue. Google Groups is more for discussions around products, and use cases rather than a channel for peer to peer support. 

Liam Monninger

unread,
Jan 20, 2022, 12:34:59 PM1/20/22
to Andrew (Google Cloud Platform Support), Google Cloud Developers
Thanks for the advice! Unfortunately, I ended up getting stuck there as well.

I think I'm being sent in circles here. Is there someone who's perhaps a Google Picker expert with whom I can speak? Andrew, do you know anyone? I believe I've exhausted all options that I can think of at this point.

Best,
Liam

Bruno (Cloud Platform Support)

unread,
Jan 20, 2022, 2:42:16 PM1/20/22
to Google Cloud Developers
Hi, 

Could you elaborate on how you are stuck when flagging the issue via the Public Issue Tracker

The Issue Tracker is the next best route to take in this case as mentioned here since your issue will be flagged directly to the Picker API engineering team.

However, If you have a Google Workspace or Cloud Identity Premium account, you can also email Google Workspace developer support for additional help from a specialist.

Liam Monninger

unread,
Jan 20, 2022, 4:55:29 PM1/20/22
to Bruno (Cloud Platform Support), Google Cloud Developers
The issue I'm facing cannot reliably be reproduced, so they flagged it as won't fix. This is not a surprise. I can't even reproduce the issue outside of the context of my application.

They asked me to go through Workspace support, but I'm not a Workspace admin. In the past, I've tried to go through GCP support to see if this has to do with the way my keys are set up. They found nothing and sent me to Workspace Developer Support which eventually led me here.

I will try developer support again though, given that since the last time I went through the process I've gathered a little bit of new information.

Best,
Liam



Reply all
Reply to author
Forward
0 new messages