Fixed
Status Update
No update yet.
Comments
oz...@google.com
oz...@google.com
Thank you very much for reporting the issue; Is this issue still surfacing with the latest iOS SDK build?
Please note:
4.5.2 was released 11/4/20, found here:https://developers.google.com/cast/docs/release-notes#november-4,-2020
4.5.1 was released 10/13/20, found here:https://developers.google.com/cast/docs/release-notes#october-13,-2020
Please note:
4.5.2 was released 11/4/20, found here:
4.5.1 was released 10/13/20, found here:
ja...@gmail.com
4.5.2 didn't resolve the issue
oz...@google.com
Thank you very much for confirming the issue is still surfacing. Can you check with the latest iOS SDK build?
4.5.3 was released 12/3/20, found here:https://developers.google.com/cast/docs/release-notes#december-3,-2020
4.5.3 was released 12/3/20, found here:
bi...@google.com
This looks to still be an issue with the latest SDK build.
bi...@google.com
We're targeting a fix for this in the next release (4.7.0).
bi...@google.com
oz...@google.com
This issue will be fixed in the next release (4.7.0). We will post here with an update on delivery once it becomes available.
bi...@google.com
This has been addressed in iOS sender SDK 4.7.0, which just released.
vi...@gmail.com
Portabilidad
Description
1. They say "Cast" instead of "Chromecast". "Cast" is too generic.
2. The label is constructed out of two strings (CAST_BUTTON_ACCESSIBILITY_LABEL and a per-state one such as CAST_BUTTON_CONNECTED_ACCESSIBILITY_LABEL), but there's no space in between, so the actual label I see right now is "CastNot connected state" (note the lack of space). Also, cramming two values together like this isn't necessarily valid for all languages.
3. The language "Not connected state" isn't very user-friendly.
What I'd expect is for it to say something like "Chromecast is not connected".
I reproduced this with SDK version 4.4.4 on iOS 13.4, though I downloaded SDK 4.4.7 and verified that the UILocalizable.strings file contains the same strings.