Status Update
Comments
bl...@google.com <bl...@google.com> #2
The issue is reproducible with core-ktx 1.2.0 and 1.3.0-rc01.
sh...@fieldking.com <sh...@fieldking.com> #3
The Typeface.weight is not a weight of the underlying font file. It is a display style. On older APIs, the display style is adjusted if the Typeface is created from single font. However, after moving to CustomFallbackBuilder, that adjustment is removed since it can crate Typeface from multiple style font files.
Looks like it is good to set display style by ResourcesCompat.getFont for backward compatibility.
sb...@google.com <sb...@google.com> #4
Hi Nona,
Can you please schedule a release after you merge the fix?
sh...@fieldking.com <sh...@fieldking.com> #5
Branch: androidx-master-dev
commit 3d6aa2e9b3243dcc4de1f54bd8d40339bd69cb05
Author: Seigo Nonaka <nona@google.com>
Date: Wed May 27 17:38:05 2020
Adjust the Typeface display style with the style of given font
This behavir is implicitly done by Typeface.Builder and
Typeface.createXXX function but not to be done by
Typeface.CustomFallbackBuilder since it is designed to be working
with multiple font files which has different style.
Looks like the style argument is ignored on older API implementation.
Bug: 156853883
Bug: 152023266
Test: ResourcesCompatTest#testGetFont_adjustDisplayStyle passes on 29
Test: ./gradlew core:core:connectedAndroidTest on API 29, 28, 23
Change-Id: I3a377c339a7aed50973cf11df86ddf0069f4ec25
A core/core/src/androidTest/assets/fonts/thin_italic.ttf
A core/core/src/androidTest/assets/fonts/thin_italic.ttx
M core/core/src/androidTest/java/androidx/core/content/res/ResourcesCompatTest.java
A core/core/src/androidTest/res/font/thin_italic.ttf
M core/core/src/main/java/androidx/core/graphics/TypefaceCompatApi29Impl.java
sh...@fieldking.com <sh...@fieldking.com> #6
sh...@fieldking.com <sh...@fieldking.com> #7
sh...@fieldking.com <sh...@fieldking.com> #9
sh...@fieldking.com <sh...@fieldking.com> #10
sb...@google.com <sb...@google.com> #11
curl --request PATCH \
'https://meet.googleapis.com/v2/spaces/xxxxxxx?key=[YOUR_API_KEY]' \
--header 'Authorization: Bearer [YOUR_ACCESS_TOKEN]' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{"config":{"accessType":"OPEN"}}' \
--compressed
jp...@google.com <jp...@google.com> #12
I wrote up an example in NodeJs at
// get the meeting code from the calendar event
const conferenceId = event.conferenceData.conferenceId;
const meetClient = new meetV2.SpacesServiceClient({ authClient: auth });
const space = (
await meetClient.getSpace({
name: `spaces/${conferenceId}`,
})
)[0];
const updatedSpace = (
await meetClient.updateSpace({
space: { name: space.name, config: { accessType: "OPEN" } },
updateMask: {
paths: ["config.access_type"], // must be in snake_case
},
})
)[0];
sh...@fieldking.com <sh...@fieldking.com> #13
sh...@fieldking.com <sh...@fieldking.com> #14
sh...@fieldking.com <sh...@fieldking.com> #15
sh...@fieldking.com <sh...@fieldking.com> #16
sh...@fieldking.com <sh...@fieldking.com> #17
sh...@fieldking.com <sh...@fieldking.com> #18
jp...@google.com <jp...@google.com> #19
The sample code I shared will need to be modified to work with the oauth pattern used in your code. Additionally, you may need to add some scopes.
sh...@fieldking.com <sh...@fieldking.com> #20
sh...@fieldking.com <sh...@fieldking.com> #22
sh...@fieldking.com <sh...@fieldking.com> #23
sh...@fieldking.com <sh...@fieldking.com> #24
sb...@google.com <sb...@google.com> #25
This issue is closed and no further responses on this issue will be given. Please see the above resources for details on how to implement oauth.
Description
Hey team,
I'm using the Google Meet API to schedule meetings, but I'm encountering an issue when inviting participants with non-Gmail accounts. For instance, if I invite two people—one with a Gmail account and the other without—the non-Gmail user is unable to join the meeting directly. Instead, they are prompted to request permission to join, which can be inconvenient. While I'm aware of the option to manually adjust host controls to allow all users, doing this for each meeting is impractical and tedious. Is there a way to configure the API so that host controls are automatically open for all users, regardless of their email domain?