Status Update
Comments
sa...@google.com <sa...@google.com> #2
Hi. Could you attach the file C:\Program Files (x86)\Google\GoogleUpdater\updater.log
? Also, could you confirm that you used the installer at
mr...@googlemail.com <mr...@googlemail.com> #3
Thanks,
sa...@google.com <sa...@google.com> #4
261.3624)
On Mon, Apr 7, 2025 at 3:44 AM <buganizer-system@google.com> wrote:
nm...@emmawillard.org <nm...@emmawillard.org> #5
Thank you for providing more feedback. Adding the requester to the CC list.
le...@vedubox.com <le...@vedubox.com> #6
On Mon, Apr 7, 2025 at 7:45 AM <buganizer-system@google.com> wrote:
bb...@elkhart.k12.in.us <bb...@elkhart.k12.in.us> #7
Hi. Could you attach the file C:\Program Files (x86)\Google\GoogleUpdater\updater.log
? Also, could you confirm that you used the installer at
jd...@unal.edu.co <jd...@unal.edu.co> #8
On Tue, Apr 8, 2025 at 5:10 AM <buganizer-system@google.com> wrote:
am...@sirius.education <am...@sirius.education> #9
jd...@unal.edu.co <jd...@unal.edu.co> #10
On Tue, Apr 8, 2025 at 7:44 AM <buganizer-system@google.com> wrote:
mr...@googlemail.com <mr...@googlemail.com> #11
Hello; I see that you uploaded updater.log.old
; can you also check to see if there is an updater.log
file (without the .old) in the same directory, and upload that?
wi...@mie-solutions.com <wi...@mie-solutions.com> #12
On Tue, Apr 8, 2025 at 8:14 AM <buganizer-system@google.com> wrote:
cp...@twochairs.com <cp...@twochairs.com> #13
Thank you!
The issue that immediately jumps out at me is that the updater installation was in OEM mode; this is a 72-hour period after a device manufacturer installs Chrome where the updater is deliberately nonfunctional, to avoid disrupting factory operations. (I will follow-up to provide a better error code in this case, if possible.)
Based on the log, the device exited OEM mode 2025-04-07 22:22 UTC, and it looks normal after that. Since this bug was filed on 2025-04-06, can you double-check that the problem hasn't fixed itself?
Either way, it would be useful to know:
- Was the device factory reset or purchased recently?
- Was Chrome pre-installed or did you install it?
- If you installed Chrome, what installer did you use (where did you get the Chrome installer, and did you just run it normally)?
bi...@cordovacloud.com <bi...@cordovacloud.com> #14
came in pre installed at all I checked to see if it needs an update and
that occurred. Here is how I installed it I'll provide you a link. Here it
is: Google Chrome - The Fast & Secure Web Browser Built to be Yours
<
On Tue, Apr 8, 2025 at 8:53 AM <buganizer-system@google.com> wrote:
[Deleted User] <[Deleted User]> #15
reason. The browser for google chrome works just fine. But, won't update at
all. When I click about chrome.
On Tue, Apr 8, 2025 at 8:53 AM <buganizer-system@google.com> wrote:
va...@gmail.com <va...@gmail.com> #16
On Tue, Apr 8, 2025 at 8:53 AM <buganizer-system@google.com> wrote:
as...@saargo.com <as...@saargo.com> #17
Please add "Unconfirmed" if triage is needed for this issue
Thanks!!
dr...@gmail.com <dr...@gmail.com> #18
Please make this happen.
ge...@thebritishclass.com <ge...@thebritishclass.com> #19
mi...@eventful.se <mi...@eventful.se> #20
va...@gmail.com <va...@gmail.com> #21
Our Business is relayed on adding co-hosts programmatically, can someone provide a solution please
mr...@googlemail.com <mr...@googlemail.com> #22
Have you tried Zoom or MS Teams? Not checked the MS Graph API recently but I'm pretty sure the Zoom API enables you to add cohosts programmatically as long as they are users on your account. Without any of the back door fiddling of only being able to set meetings up via a calendar api.
Sorry Google, you really need to get ahead here and give us a proper Meet API!
an...@gmail.com <an...@gmail.com> #23
sa...@gmail.com <sa...@gmail.com> #24
mr...@googlemail.com <mr...@googlemail.com> #25
It's a year old. Conclusion: Google have no interest in investing in a proper API on Google Meet.
sr...@wework.co.in <sr...@wework.co.in> #26
wd...@gmail.com <wd...@gmail.com> #27
For that feature, you need to use 2 secret google GRPC apis.
mr...@googlemail.com <mr...@googlemail.com> #28
Hi @wd - are you saying you have acheived this by some secret / undocumented (supported?) means? If so please share more details.
ih...@philipps-byrne.com <ih...@philipps-byrne.com> #29
This feature request is more than a year old.
eg...@squareup.com <eg...@squareup.com> #30
Either that, or y'all need to support allowing entire google groups (presenters in our case) to become co-hosts and remove the attendance restriction on co-hosts.
da...@sasaustin.org <da...@sasaustin.org> #31
My school's Admissions Office coordinates all parent interviews through their office Google account. However, there are a set of 15 employees who might be tapped to conduct the parent interview during the admissions season. We need any of these 15 employees to be able to launch (ie Co-host) the Google Meet parent interview.
Additionally, the scheduling and the recordings/transcripts must be consolidated in the Google account of the Admissions Office itself and not reside within the 15 individual users' accounts. Thus, the Admissions Office account must be the primary host of these meetings.
Moreover, when there has to be a switch of an Admissions representative for the parent interview, having to change the co-host manually (hidden behind several clicks throughs) is far from ideal. It's ripe for error that is really bad optics for
We have automated the RSVP system for this office to run through the Admission Office Google Calendar. We currently do this with Zoom because Zoom allows static meeting IDs. Meet does not provide static ids, and thus, migrating to Meet from Zoom is currently not worth it.
mp...@shcgeelong.catholic.edu.au <mp...@shcgeelong.catholic.edu.au> #32
ko...@gabinetsamorozwoju.pl <ko...@gabinetsamorozwoju.pl> #33
ys...@gmail.com <ys...@gmail.com> #34
jp...@google.com <jp...@google.com>
st...@freepressunlimited.org <st...@freepressunlimited.org> #35
hu...@gmail.com <hu...@gmail.com> #36
mi...@gmail.com <mi...@gmail.com> #37
[Deleted User] <[Deleted User]> #38
el...@gmail.com <el...@gmail.com> #39
jo...@gmteststud.uhasselt.be <jo...@gmteststud.uhasselt.be> #40
ma...@tryonce.com <ma...@tryonce.com> #41
di...@gmail.com <di...@gmail.com> #42
vo...@nobelcoaching.com <vo...@nobelcoaching.com> #43
jf...@block.xyz <jf...@block.xyz> #44
so...@riverlearningtrust.org <so...@riverlearningtrust.org> #45
ne...@gmail.com <ne...@gmail.com> #46
ro...@gmail.com <ro...@gmail.com> #47
[Deleted User] <[Deleted User]> #48
ne...@gmail.com <ne...@gmail.com> #49
ti...@gmail.com <ti...@gmail.com> #50
ra...@gmail.com <ra...@gmail.com> #51
bu...@gmail.com <bu...@gmail.com> #52
ai...@gmail.com <ai...@gmail.com> #53
br...@nytimes.com <br...@nytimes.com> #54
he...@vasla.org <he...@vasla.org> #55
mr...@googlemail.com <mr...@googlemail.com> #56
I don't think Google can be bothered. That's fine - we're willing to pay Zoom in the mean time.
ma...@tryonce.com <ma...@tryonce.com> #57
pa...@aedl.pt <pa...@aedl.pt> #58
ja...@gmail.com <ja...@gmail.com> #59
ja...@gmail.com <ja...@gmail.com> #60
ja...@gmail.com <ja...@gmail.com> #61 Restricted+
ja...@gmail.com <ja...@gmail.com> #62
ja...@gmail.com <ja...@gmail.com> #63
ja...@gmail.com <ja...@gmail.com> #64
ja...@gmail.com <ja...@gmail.com> #65
In this way, i confirmed that anyone can access the room when creating it using SpaceConfig.
I tried to post example code, but my comment was deleted.
ch...@gmail.com <ch...@gmail.com> #66
But from the looks of it this functionality does not even exist in the Meet API from what I can see here:
Other meeting platforms offer this functionality. It is becoming very tedious for us to have to go in and add co-hosts manually after creating the meeting via the API.
Eventually we will likely need to switch from Google to another provider if there is no interest in adding this feature.
ah...@athareg.com <ah...@athareg.com> #67
da...@szkolawchmurze.org <da...@szkolawchmurze.org> #68
ep...@viewpointlearn.com <ep...@viewpointlearn.com> #69
ep...@gmail.com <ep...@gmail.com> #70
mr...@googlemail.com <mr...@googlemail.com> #71
This request was raised in response to a post on stackoverflow over 3 years ago now.
I can see the issue is assigned to
Any chance of an update? What is
Any time in the next 3 years would be very welcome
er...@mercadolivre.com <er...@mercadolivre.com> #72
ra...@gmail.com <ra...@gmail.com> #73
and , does the "Manage Space Members" feature work as expected for co-host?
Description
A short description of the request: When creating a new event we should be able to do the following in the Calendar API:
What is the purpose of this new feature? The latest host controls and the ability to add co-hosts on Google Meet are really handy and start to bring the service on a par with Zoom, Teams and other platforms. Other platforms expose these features in their APIs, Google should also do the same.
What existing APIs would this affect? Calendar Events (https://developers.google.com/calendar/api/v3/reference/events/insert )
What existing data does this use? N/A
Please provide any additional information below. In response tohttps://stackoverflow.com/questions/68813169/host-controls-update-using-calendar-api