K7 Total Security 歷史版本列表
更新時間：2022-07-22
更新細節：
更新時間：2022-07-22
更新細節：
What's new in this version:
Added:
- use translated button captions in message-boxes, both internal and API
- wiki page https://wiki.freepascal.org/CudaText_VS_other_editors
- option "renderer_tweaks" has new sub-option "l"
Fixed:
- sometimes, bookmarks-section in the history file was purged by mistake
- click on the folded-block-rectangle hides caret
- in e.g. Python lexer, new typed text may be 'catched' by the upper _folded_ block
- on some Linux systems, with dots_per_inch=91, minimap is empty
- lexers XML/XML^: highlight quoted string only after '='
- lexer Markdown: rule for italics
更新時間：2022-07-18
更新細節：
What's new in this version:
Added:
- API to speedup ExTerminal plugin- dialog 'Go to': handle also leading '+' like the trailing one
- list "File / Open recent" stores also pictures/binaries
- TRegExpr engine: update "uppercase/lowercase tables" for some unicode ranges
Fixed:
- fix/optimization: rendering with 'markers' on 100k+ lines was very slow
- fix/optimization: command "Inverse bookmarks" was very-very slow in 100k+ lines documents
- fix/optimization: plugin Git Status was very-very slow if Git changes had 10k+ lines
- fix/optimization: during mass replacement, pair-bracket-finder must not activate
- fix: sometimes, 'markers' were painted with artifact lines
- fix: on Windows, startup with 2+ groups did not restore "maximized" state- fix: on Windows, picture viewer: dragging of small picture was not disabled
- fix: on tab switching, window caption must be updated without pause
- fix: file must appear in "File / Open recent" if default-session is active
- fix: couple of issues with Up/Down/PageUp/PageDown with "caret_after_end" on/off- fix: 'floating' panels feature is now disabled in GTK2 version, because of the IDE (or GTK2) bug- fix: could not continue selection by mouse when cursor goes over minimap
更新時間：2022-07-16
更新細節：
What's new in this version:
- Android: Setup logic to publish the Godot Android library to MavenCentral (GH-59146)
- Animation: Fix cubic interpolate when looping (GH-58651)
- Audio: Revert "PitchShift effect quality and performance tweaks for different pitch scale values" (GH-58668) [regression fix]
- This fixed a valid issue while introducing a new one, so it was reverted for the time being until a better fix can be found
- Core: Print every file exported with PCKPacker.flush()'s verbose parameter (GH-58520)
- Core: Fix UndoRedo::create_action() invalid memory usage (GH-58652)
- Core: Revert "Fix ProjectSettings has_setting() when used on a overriden setting with feature tags" (GH-58859)
- Core: Fix crash on Input.get_joy_button_index_from_string and Input.get_joy_axis_index_from_string for non-existing key (GH-59195)
- CSG: Fix visible seam on smoothed sphere, cylinder, and torus shapes (GH-58208, GH-59002)
- CSG: Fix mixed smoothed and non-smoothed face normals computation for CSG shapes (GH-59039)
- Editor: Fix showing Extend Script option without script attached to the node (GH-58821)
- HTML5: Revert "[HTML5] Fetch API now passes credentials." (GH-58862) [regression fix]
- This turned out not to be a good option with the current state of the web standard
- iOS: Fix multitouch not working correctly (GH-58586) [regression fix]
- Physics: Fix premature return in GodotPhysics Area call_queries (GH-58531)
- Physics: Update joints on NOTIFICATION_POST_ENTER_TREE (GH-58642)
- Portals: Fix duplication of instanced scenes during conversion (GH-58650)
- Rendering: GLES2: Fix compression on blend shapes (GH-58838)
- Rendering: GLES2: Fix VersionKey comparison in shader binding (GH-58855)
- Rendering: GLES2: Fix incorrect buffer upload size in draw_gui_primitive (GH-58150)
- Rendering: GLES3: Fix shader state caching when blend shapes used (GH-58808) [regression fix]
- Rendering: GLES3: Fix broken normals in meshes with blend shapes (GH-59159) [regression fix]
- Rendering: Fix alpha scissor support with depth_draw_opaque (GH-58959)
- RichTextLabel: Fix shadow color when text has transparency (GH-59054)
- Windows: Fix reporting of DST in OS.get_datetime() (GH-59223)
- API documentation updates
更新時間：2022-07-15
更新細節：
What's new in this version:
Support for Java 18:
- Gradle now supports running on and building with Java 18
Support for Groovy 4:
- Gradle now supports building software using Groovy 4.0. Note that Groovy DSL buildscripts still use Groovy 3
Scala Zinc has been updated:
- The default Scala Zinc version was updated to 1.6.1
- Zinc is the Scala incremental compiler that allows Gradle to always compile the minimal set of files needed by the current file changes. It takes into account which methods are being used and which have changed, which means it’s much more granular than just interfile dependencies.
Continuous Build is much more responsive on Windows and macOS with Java 9+:
- Continuous Build automatically re-executes the build with the same requested tasks when inputs change. This allows for continuous feedback during development.
- Because of the internal changes in the JDK, Continuous Build did not work well on Windows and macOS on Java 9 and higher. It could take up to 10 seconds to detect a change and trigger a build.
- Now Gradle picks up changes nearly instantly on Windows and macOS for all Java versions as well, making Continuous Build respond quickly on all major operating systems. This is because Gradle now uses its own robust and natively implemented file system watching system instead of relying on the generic API in the JDK.
Improved diagnostic reports for dependency resolution:
Outgoing Variants:
- The outgoingVariants report now provides additional information that allows further insight into variant aware dependency resolution results
- This report is useful when determining why a particular variant of this producer project was selected by another consumer project when the producer depends upon the consumer. Run the report from the producer project, to list every variant built by it (including secondary variants only visible to other local projects). The output contains the capabilities and attributes present on each variant of the producer, along with other information detailed below. This output can be compared against the output of the new resolvableConfigurations report run in the consumer.
- Descriptions are now printed for secondary variants, if present
- Configurations using @Incubating attributes are marked with an (i)
- The legend at the bottom of the report clarifies the usage of secondary variants
- The formatting (and coloring for rich console) of the output is now clearer and more consistent with other reports
- Capabilities, Attributes and Artifact lists are alphabetically sorted
- (not shown) Classifiers are now printed next to artifacts if present
- (not shown) New messages when using --all and --variant options to better describe results (or the lack thereof)
Description available on secondary variants:
- When defining secondary variants, which are variants available only to other local Gradle projects, there is a new ConfigurationVariant method available to supply a note or description for the variant. These descriptions will be printed by the outgoingVariants report and defaults have been added for existing secondary variants produced by the Java plugin.
Resolvable Configurations:
- There is a new resolvableConfigurations report available which will display information about all the configurations in a project that can be resolved
- This report compliments the outgoingVariants report and is meant to be run from the consumer side of a dependency to determine why a particular variant of a producer project was selected by this consumer project when the consumer depends upon the producer. It includes the following information:
- Description, Attributes and (directly) extended Configurations
- A --recursive option flag can be set to display all configurations which are extended transitively
- Attributes affected by Compatibility or Disambiguation rules during resolution listed
- A --configuration option can limit this report to a single configuration
- A --all option flag can be set to include legacy configurations which are both resolvable and consumable; these will be hidden by default
- See the ResolvableConfigurationsReportTask DSL reference for more details
Dependency Insights:
- The dependencyInsight report provides information about a specific dependency, including what variant was selected, and the attributes used during resolution.
- The report now uses a table to display variants, which makes it easier to tell where attribute values are from, and see why a particular variant was selected
- The variant name is listed at the top, after the word "Variant"
- The variant output is now in table format.
- Attributes only present in the variant's metadata only contain text in the "Provided" column
- Attributes present in both the variant's metadata and requested by the configuration contain text in both columns
- Attributes only requested by the configuration only contain text in the "Requested" column
- As seen in (3) and (5), items are colored orange if they are not present in one column. The table is sorted first by groups (3), (4), and (5); then alphabetically inside each group.
Dependency resolution results can be used as task inputs:
- Tasks may need to access dependency resolution results. For example, built-in tasks like dependencies and dependencyInsight do so in order to provide reporting about resolved artifacts and dependency graphs. Other tasks may produce file outputs based on dependency resolution results. Previously, it was only possible by performing dependency resolution in a task action. However, this resulted in suboptimal performance.
- Starting with Gradle 7.5 it is now possible to declare dependency resolution results as task inputs.
- This allows writing tasks which consume dependency resolution results. Declaring such inputs instead of doing undeclared dependency resolution in task actions allows Gradle to optimise for build incrementality. Additionally, these new types of task inputs are fully supported by the configuration cache.
- You can learn more in the Authoring Tasks user manual chapter and with the dedicated sample
Configuration cache improvements:
- The configuration cache improves build time by caching the result of the configuration phase and reusing this for subsequent builds
- Running external processes at configuration time:hg
- Previously, external processes started with exec or javaexec APIs were ignored by configuration cache, and it could be a potential correctness issue if the output of the external process affects the configuration.
- A new Provider-based API is now available to obtain the output of the external process in the configuration-cache-compatible way. The exec and javaexec APIs are now disallowed if the configuration cache is enabled in order to prevent potential issues.
- If a more complex interaction with the external process is necessary, then a custom ValueSource implementation can be used. The injected ExecOperations service should be used to run the external process.
Files read at configuration time become build configuration inputs:
- Files read at configuration time with FileInputStream or some Kotlin APIs now automatically become build configuration inputs. The configuration cache is invalidated if the contents of such file(s) change between builds.
- Previously, file reads were ignored, and it could be a potential correctness issue if the contents of the file(s) affected the configuration
New ways to access environment without unnecessary invalidations of the configuration cache:
- Since the automatic build configuration inputs detection was introduced in Gradle 7.4, some common patterns of reading subsets of environment variables or system properties were causing excessive invalidations of the configuration cache, leading to suboptimal performance. For example, iterating over all environment variables to find the ones with names starting with some prefix caused all available variables, even the unrelated ones, to become configuration inputs.
- Two new options are now available to mitigate that. For simpler use cases, there are the Provider-based APIs to access system properties or environment variables with names starting with some prefix. Advanced processing, like filtering names with regular expression, can be done inside a custom ValueSource implementation. Reading a file, an environment variable, or a system property no longer adds a build configuration input inside the implementation of the ValueSource. The value of the ValueSource is recomputed each time the build runs, and the configuration cache entry is only invalidated if the value changes.
New compatible plugins and tasks:
- The kotlin-dsl plugin is now compatible with the configuration cache
- The dependencyInsight, outgoingVariants and resolvableConfigurations tasks are now compatible with the configuration cache
New STABLE_CONFIGURATION_CACHE feature flag:
- Configuration caching introduces a number of requirements regarding the build logic. Many problems are already reported in the HTML report. At the moment, adjusting the build logic to be fully compatible with configuration cache can be a significant effort for complex builds.
- This release introduces the STABLE_CONFIGURATION_CACHE flag allowing gradual rollout of the most potentially disruptive requirements. This flag currently enables validations like detecting undeclared shared build service usage and external processes used at configuration time.
- It is recommended to enable this flag as soon as possible in order to be ready for when the flag is removed and make the linked features enabled by default
JVM toolchains improvements:
- Java toolchains provide an easy way to declare which Java version your project should be built with. By default, Gradle will detect installed JDKs or automatically download new toolchain versions.
- Java toolchains can download any JDK by automatically selecting between Adoptium and AdoptOpenJDK
- Gradle now checks the Adoptium API first when downloading JDKs, rather than only using the legacy AdoptOpenJDK API. This allows downloading the new JDK 18 releases, which are not available via AdoptOpenJDK, while still maintaining the ability to download versions that are no longer supported by Adoptium, such as JDK 9-10 and 12-16.
- In case you are using an internal mirror to download JDKs, there is a new Gradle property org.gradle.jvm.toolchain.install.adoptium.baseUri to control the Adoptium base URI. This is in addition to theorg.gradle.jvm.toolchain.install.adoptopenjdk.baseUri property, which is still used if a JDK is not found in the Adoptium API.
IDE integration improvements:
Improved test sources separation in Eclipse:
- This release provides improved support for test sources in Eclipse.
- The Eclipse classpath file generated by the eclipse plugin has the following changes:
- Project dependencies defined in test configurations get the test=true classpath attribute
- All source sets and dependencies defined by the JVM Test Suite plugin are also marked as test code by default
- The eclipse plugin DSL exposes properties to configure test sources
Query a single property with the properties task:
- The built-in properties task prints all project properties to the console. Now, the task takes an optional --property argument which configures it to display the selected property only.This is useful for keeping track of specific properties on CI systems, and requires much less parsing and filtering than before.
Groovydoc exposes more options:
The Groovydoc task now exposes more options:
- access: for controlling the access levels included in the documentation, defaults to PROTECTED
- includeAuthor: for controlling whether the author is displayed in the documentation, defaults to false
- processScripts: for controlling whether scripts are included in the documentation, defaults to true
- includeMainForScripts: for controlling whether a script's main method is included in the documentation, defaults to true
- These defaults are the same as what was previously used, so there should be no changes to the default behavior
show-version (-V) flag:
- The -V flag (long form --show-version) instructs Gradle to first print version information and then continue executing any requested tasks. This is in contrast to the pre-existing -v (long form --version) flag which prints version information and then immediately exits.
- This flag may be useful in CI environments to record Gradle version information in the log as part of a single Gradle execution
Performance Improvements:
- Checkstyle tasks use toolchains and execute in parallel by default
- The Checkstyle plugin now uses the Gradle worker API to run Checkstyle as an external worker process, so that multiple Checkstyle tasks may now run in parallel within a project. This can greatly increase overall build performance when several of these tasks exist within a single project. You can adjust the memory used by the Checkstyle process via the minHeapSize and maxHeapSize properties on the Checkstyle task. In case of out of memory errors please see the Gradle 7.x upgrade guide.
- Checkstyle now uses JVM toolchains in order to minimize JDK installation requirements. In Java projects, Checkstyle will use the same version of Java required by the project. In other types of projects, Checkstyle will use the version of Java that is used by the Gradle daemon.
Run a single PMD task on multiple threads:
- PMD is a quality analysis tool that runs on the Java source files of your project
- With this version of Gradle, the thread parameter PMD offers is now exposed through the PMD extension and tasks. This allows configuration of PMD to run its analysis on more than one thread.
- See the documentation for more information
Better test compatibility with Java 9+:
- When running on Java 9+, Gradle no longer opens the java.base/java.util and java.base/java.lang JDK modules for all Test tasks. In some cases, this would cause code to pass during testing but fail at runtime.
- This change may cause new test failures and warnings. When running on Java 16+, code performing reflection on JDK internals will now fail tests. When running on Java 9-15, illegal access warnings will appear in logs. While this change may break some existing builds, most failures are likely to uncover suppressed issues which would have only been detected at runtime.
- For a detailed description on how to mitigate this change, please see the upgrade guide for details
Fixed:
- 88 issues have been fixed in Gradle 7.5
- "Unable to make progress running work" using 7.5-rc-3
- StackOverflowError thrown from internal Gradle code
- Broken links for 7.5-rc-2 release notes
- Fix implicit command-line ordering test in AbstractIdeLifecycleIntegrationTest
- `mustRunAfter` constraint is violated by `finalizedBy` dependency
- Incorrect task ordering in Gradle 7.5-rc-1 (and possibly earlier versions)
- Build fails with "Task was never scheduled for execution" exception when configuration cache is enabled
- Misdetected cycle on combination of `finalizedBy` and `mustRunAfter` constraints
- `ResolvedArtifactResult` cannot be fingerprinted when there are outputs in 7.5-rc-1
- Remember to double check the releases.xml update after RC2 is built
- `ArtifactCollection.getResolvedArtifacts()` is not compatible with configuration cache if combined with artifact views
- Misdetected cycle issue after upgrading to 7.5-rc-2
- Gradle refresh in IntelliJ IDEA fails with IllegalStateException: Unexpected parent dependency id error with spring-boot 2.6.7
- Gradle worker should not open any packages during tests
- 7.5 nightly slows down or hangs when many tasks are requested on the command-line
- Wrong inputs detected when using large filtered file trees
- Regression in ArtifactTransforms for transforming artifactType from jar to directory
- Creator-destroyer relationship for tasks from different projects not upheld during parallel execution
- Possible unexpected state in scheduler causing deadlock
- Clarify docs re: CLI task ordering
- Toolchain not downloading Java18 for specific vendor
- Failing to fingerprint the class API should not fail the entire zip/jar
- Support latest JDK features while inspecting classes
- Task outputs are wrongly detected in conjunction with filtered file trees
- Using `rename { ... }` in `Copy` task silently breaks configuration cache
- configureondemand causes build failure in multi module project with different group name
- Adjust documentation in Jacoco Report Agreggation plugin and Test Report Aggregation
- Configuration cache failure in 7.4.2 caused by kapt
- Toolchain cannot download JDK 18
- Dependency resolution depends on existence of external POMs
- Build with included builds fails with "Unable to make progress running work"
- gradle depends on an insecure third-party JAR package that contains the CVE vulnerability
- Imported BOM parsing fails if published with Gradle Module Metadata
- Add "threads" configuration option to PmdExtension
- Support annotationProcessor in Test Suites' dependencies block
- Dependency verification fails for signed klib artifacts
- Build cache miss with TYPESAFE_PROJECT_ACCESSORS
- Plugin Development plugin declares inputs with custom equals()
- notCompatibleWithConfigurationCache failed to force errors into warnings
- Tests should run after `jar` task
- Dependency constraint on project with newer version does not upgrade dependency on Maven artifact
- Setting bootClasspath can cause build failure with obscure message on Windows only after upgrade to 7.3.x
- Support xfs for file watching. Report file system type when found to be unsupported
- Pattern `fileCollection.filter(predicate).getAsFileTree().matching(patternSet)` is not supported by the configuration cache
- Fix DefaultMutableAttributeContainer behavior when updating attributes using both eager and lazy values
- Default checkstyle version does not support sealed modifier
- Unix start script doesn't respect JAVA_OPTS when xargs isn't installed
- Document limitations of continuous build
- Remove https://keys.fedoraproject.org from key servers
- Add new ResolvableVariants Report
- Extend `PropertyReportTask` to allow specifying which property to query
- Allow Gradle Enterprise plugin to read access key files during configuration phase
- Relative paths for detected file inputs are wrong in the configuration cache report
- Take filename into account for caching artifact transform results
- Upgrade embedded Kotlin to 1.6.10
- Support JDK 18
- Make obscure "no signature of method" error message useful
- Strange JVM target warning from Kotlin DSL in buildSrc
- Wrong Gradle 7.2 documentation for version conflict resolution when only ranges involved
- Generalize `TaskInputsListeners`
- Kotlin DSL "classpath mode" leniency doesn't capture after evaluation exceptions
- Incorrect result when TestNG 7.x test times out
- Be able to skip implicit adding of gradlePluginPortal repo
- Properly analyze jar files without directory entries during test scanning
- Configuration cache doesn't capture system property updates during configuration
- `project.sync` is not allowing to specify `preserve` even though the `Sync` task does and the documentation explicitly mentions it
- Eclipse classpath should be able to use test fixtures in implementation dependencies
- dependencyInsight task is not configuration cache compatible
- Review types excluded from annotation analysis
- Confusing error message when build cache can't clean output directory
- Deadlock when task outputs are calculated from input configuration
- IterationOrderRetainingSetElementSource#add takes time linear in the collection size
- NullPointerException during isolation of artifact transform parameters and shared build service configuration
- Scala 2.13 with Zinc 1.4.3 fails with NoSuchMethodError
- Gradle Windows scripts don't propagate exit codes correctly
- DirectoryProperty.files() resolves incorrectly
- Invalid closure configuration methods lead to cryptic error messages
- Custom Remote Build Cache does not work with configuration cache enabled
- Provide a configuration cache friendly way of looking up a subset of system properties and environment variables
- Task dependency is silently dropped with mismatching setter.
- Project properties not accessible from settingsEvaluated
- Introduce APIs to represent a resolved dependency graph in a lazy manner
- Add flag to hide welcome message
- Use same infrastructure for VFS retention and continuous build
- Gradle 5.6.2 and TestNG 7.0.0 incompatibility
- Deprecate `IncrementalTaskInputs`
- Javadoc does not take into account custom options
- Continuous build responsiveness is too slow on mac
更新時間：2022-07-12
更新細節：
更新時間：2022-07-12
更新細節：
What's new in this version:
- New Shape Customize module
- Now, the user can directly change shapes when adding new shapes
- All-new materials lib for video creation
- Stable version, fixed reported bugs
更新時間：2022-07-12
更新細節：
更新時間：2022-07-12
更新細節：
更新時間：2022-07-12
更新細節：
What's new in this version:
Cisco Webex Teams 42.7.0.22904 (64-bit)
Fixed:
- Spellcheck didn't work on Linux
- Webex App causing high power usage
- CPU is high when Webex App displays Join button/timer (Green button)
- Unable to sign out of Webex App on iPhone or iPad
- CustomURL E911 pop up doesn't load during sign in.
- Calls are sent to voicemail for Webex App on iPhone and iPad
- Webex App prompted for share permission, but setting already checked for screen recording in OS security settings
Cisco Webex Teams 42.6.0.22645 (64-bit)
- Change log not available for this version
Cisco Webex Teams 42.6.0.22565 (64-bit)
Fixed:
- Webex App gives an error message for certificate now being valid randomly
- Unable to change the space name
- Meetings tab in the app doesn't scroll to today's meeting list
- Cannot call an on-premise device from the app
- Team space conversation doesn't updated automatically with new sent message
- Unable to start a meeting in the app as the Now button wasn't available if the meeting was scheduled from the Webex site
Cisco Webex Teams 42.5.0.22259 (64-bit)
- Fixed: Some users were unable to sign in to the app
Cisco Webex Teams 42.5.0.22254 (64-bit)
Fixed:
- Some users were unable to sign in to the app
Cisco Webex Teams 42.5.0.22221 (64-bit)
Fixed:
- Jabra headset remote control not working
Cisco Webex Teams 42.5.0.22187 (64-bit)
Fixed:
- Intermittent messages send failures on iOS
- Calls using Unified CM create multiple spaces on Webex App when forwarded to extensions on a hunt group
- Webex App landing page doesn't appear correctly
- When clicking on the Join button in Webex App meeting reminder, the call starts as a Webex call instead of using the softphone capability.
- Not possible to forward a message to a person if on a call with them in Webex App
- Open an attachment in Webex App, only the bottom right quadrant is visible on primary device.
- Video calls in Webex still happening when disabled
- In Softphone only Windows desktop users are unable to listen to voicemail.
- Callback icon not shown on visual voicemail
- Call history not updated on mobile app
Cisco Webex Teams 42.4.1.22032 (64-bit)
Fixed:
- Webex for Government customers unable to sign in
- Calling party details not showing in call-pickup notification
- After disabling Calling, Messaging, and personal insights, users see chats when they start a meeting and share their screen
Cisco Webex Teams 42.4.0.21893 (64-bit)
- Webex App unable to reconnect after stand by, sleep or power saving mode on Windows
- Webex call overrides the do not disturb system setting
- Windows 10 users unable to upload a problem report
- When you try to transfer a call to somebody in a meeting, you're added to the meeting and can't transfer the call
- Edit People Insights option missing from the app
- The call window is overlapped with the Windows OS taskbar
- Meeting attendees showed as Unknown in spaces
- Webex doesn't launch a full featured meeting when the personal meeting room link contains multiple periods
- Unable to share content on second device
- When you create a space in French, the button is unreadable
Cisco Webex Teams 42.3.0.21576 (64-bit)
Fixed:
- Add button missing when trying to add new users on Webex App
- Incorrect total recording time in chat message when recording is announced
- Personal room link displays in Webex App in profile tab, even when personal room links are disabled at site level
- Video call is launched by default when going through the URL scheme
Cisco Webex Teams 42.2.0.21338 (64-bit)
Fixed:
- Fixed an issue where the conference icon flickered when you hovered over people's profile pictures
- Some text was truncated in German
Cisco Webex Teams 42.1.0.21190 (64-bit)
We resolved the following issues:
- Some Portuguese translations were shown incorrectly
- Sometimes you couldn't connect to your local calendar
- When you joined meetings, sometimes you saw performance issues in the app
We resolved the following issue when you use Webex Calling or Calling Hosted by a Service Provider:
- When you called a phone number, you heard double ringing
We resolved the following issue when you use Calling in Webex (Unified CM):
- When you received an incoming call, sometimes the output level for ringers and alerts was at the maximum setting and when you opened the Audio settings the app reset the volume
Cisco Webex Teams 42.12.0.20899 (64-bit)
We resolved the following issues:
- When your administrator preconfigured your email for sign in, sometimes you could overwrite it
- Sometimes when you navigated through your spaces and messages, the app started to show alignment issues
- Some people noticed a delay with messages you sent
- In the health checker, some co-branding fields weren't displayed properly
- After you ended a call with somebody, in your direct space with them you got an error retrieving messages
- In some spaces, you couldn't scroll back through older messages
We resolved the following issues when you use Meetings in Webex App:
- When full-featured meetings was turned off, you couldn't start a meeting from a web browser
- When you entered a Call me phone number in Settings > Join options > Meeting join options, there was no way to delete that phone number
- Sometimes it took longer than normal to join a meeting
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- Sometimes the app quit unexpectedly when you used a Sennheiser headset
- You couldn't complete an internal call transfer
- When you tried to update your location for emergency services, the Cancel button in the Add Address dialog box wouldn't work. You had to click the X in the top right corner of the dialog box instead.
- When you'd change your call forward settings on your mobile app, the changes weren't reflected on your desktop app
- Caller ID would sometimes display the wrong name and number
- When you answered a call from a Call Queue, the phone number wouldn't display in the active call screen
- You were prompted to update your location every time you opened your laptop
We resolved the following issue when you use Calling in Webex (Unified CM):
- You weren't able to select a device under the dial pad in the Calling tab (German interface only)
- You weren't able to call someone with Call on Webex when your desk phone was connected to Webex App
Cisco Webex Teams 41.11.0.20717 (64-bit)
Fixed:
- The CPU usage increased when you opened one of your favorite spaces
- When you clicked Cancel on the Edit profile window, your cover image was removed
- You were prompted to enter a password when you used Webex App to join a meeting
Cisco Webex Teams 41.11.0.20606 (64-bit)
We resolved the following issues:
- When you created a new account, you couldn't copy and paste the six-digit activation code
- Some Russian translations were shown incorrectly
We resolved the following issue when you use Meetings in Webex App:
- When you joined a meeting by entering the video address, you weren't able to see video
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- Text wasn't visible when you signed in to the User Activation Portal
- When you'd restart your app, it would take several minutes for your voice messages to show up
- When you'd change your call forward settings on your mobile app, the changes weren't reflected on your desktop app
We resolved the following issues when you use Calling in Webex (Unified CM):
- When you answered a call on your mobile app, the related space on your desktop app moved to your hidden spaces list until the call ended
- The resolution of your app would change randomly
- When you tried to answer a call on one of your multiple lines, the call was disconnected
Cisco Webex Teams 41.10.0.20371 (64-bit)
Fixed:
- Sometimes you received an error when you connected wirelessly to a device, and you tried to share a screen
- When your administrator disabled uploading local files, sometimes you still had the option in the app to Upload from computer
Cisco Webex Teams 41.10.0.20280 (64-bit)
We resolved the following issues:
- Sometimes when you tried to join a Webex Event from the app, you were prompted to sign in and then received a notification that the event hadn't started
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- Sometimes when you answered a call, you couldn't transfer the call to someone else
- Sometimes when you received a call and the multitasking notification appeared, when the call ended the app was unresponsive
Cisco Webex Teams 41.10.0.20213 (64-bit)
We've resolved the following issues:
- When you added a website link to a space, sometimes you incorrectly got a warning that the site wasn't safe
- For some people, the app restarted when you tried to reply to a thread or when you signed in
We resolved the following issues when you use Meetings in Webex:
- When you clicked the Join button, you saw multiple, "Can't join this meeting" messages
- When you joined a meeting, the call me numbers were overlapped
- You didn't see a meeting notification when you chose to be notified 5 minutes before the meeting started
- For some time zones, you couldn't schedule a meeting in the app
We resolved the following issues when you use Calling in Webex (Unified CM):
- If you had multitasking enabled, the Webex app would quit unexpectedly when you were in the middle of a call
- Certain Hungarian and Polish keyboard shortcuts weren't working correctly
Cisco Webex Teams 41.9.0.19961 (64-bit)
We've resolved the following issues:
- You couldn't open the context menu using the shortcut keys in some places in the app
- In the calendar tab, the font for the meeting information icon wasn't the correct size
- Some tooltips weren't localized
- Some focus areas in the settings window were inconsistent
- You couldn't paste some formatted text that included links
- When you used your keyboard to navigate the app, you couldn't access some context menus
- When you used Webex for Government, Microsoft Outlook meetings didn't appear in the app
We resolved the following issues when you use Meetings in Webex:
- When you joined a meeting by clicking on a link from outside of Webex, your audio, video, join options, and virtual background setting in the Webex app didn't persist
- If you were signed in to Webex and you joined a meeting from Outlook, you were asked to sign in
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- When you called into a meeting using a paired multiplatform phone, you'd get disconnected during the meeting
- When you called someone using a phone number and then transferred that call to another person, the title of the call window was incorrect
- Call duration incorrectly included ring time
- You couldn't merge a call to make it a conference call
We resolved the following issue when you use Calling in Webex (Unified CM):
- UcLogin crash was registering Log Provider
- The emergency services disclaimer was incorrectly formatted in French
Cisco Webex Teams 41.8.0.19868 (64-bit)
- Change log not available for this version
Cisco Webex Teams 41.8.0.19732 (64-bit)
We resolved the following issues:
- We’ve improved how we set focus on content for each tab in the app
- The font size on the calling screens was to small
- Some German translations were truncated
- You couldn’t use the keyboard to navigate all elements in the audio settings window
- In the audio settings window, the i icon font was too small
- In a meeting, you couldn’t navigate to the meeting information icon
- You couldn’t use keyboard navigation to close the Space Information window
- Some Polish translations were truncated
- Sometimes you saw a connectivity issue when you opened the Health checker
- If you had a bypass proxy list, sometimes you couldn’t connect to Webex services outside of your network
- When you were formatting text to send a message, you couldn’t add a link
- When you opened a space in a new window, you saw the incorrect icon for the app
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- When you were in a call on your mobile app or your connected desk phone, the green call notification wouldn't appear on your desktop app
- You weren't able to answer the second call to a Call Queue
- The wrong number displayed in the caller ID when you received a call
- German translation was cropped when you clicked your profile picture and went to Settings > Calls > Call Queues
- The color of the text for Call Queues and Call Settings made it difficult to read in your Web app
We resolved the following issues when you use Calling in Webex (Unified CM):
- After receiving an update with a ring state, Webex didn't play the ringtone
- Your phone service wouldn't connect after you switched networks or your computer came out of sleep mode
Cisco Webex Teams 41.7.0.19440 (64-bit)
We resolved the following issues:
- When you were in the Profile tab of a direct message space and created a new space from search results, you incorrectly saw the profile information from the first space
- Some German translations were truncated
- When you pasted a link that had a dash, you received an error message as the app's Clickbait link detection didn't allow the dash in unicode format
- The app appeared to have a blank line at the top of the app
- When you disabled the Connect Webex to Microsoft Outlook setting and then restarted the app, the setting was enabled
- When you used a VPN connection, the app took several minutes to connect
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- When you're not active in Webex for a period of time, you may need to restart the application to restore your connection
- When you receive an incoming call, your call notification doesn't display the caller ID correctly
- When your desk phone is connected to Webex and you use your desk phone to put a call on hold, you're unable to resume the call from your desktop app
Cisco Webex Teams 41.6.1.19162 (64-bit)
- We’ve paused the desktop automatic update until June 15
Cisco Webex Teams 41.6.0.19119 (64-bit)
We resolved the following issues:
- We've updated the font sizes in the spaces settings, space list, message area, filters and in the Messaging and Teams tabs
If you were using the app in German:
- Some translations were truncated
- Some context menus were shown incorrectly in English
- Flag a message was incorrect
- When you were using Webex for Government and you had a HDD drive, sometimes the app used 100% of your computer's disk
- There was an issue with cobranding in the About window
We resolved the following issues when you use Calling in Webex (Unified CM):
- If you were using the app in German and you tried to add a new contact, the dialog box was cut off
- If you were using the app in Polish during a call or meeting, the Mirror my video option was translated incorrectly
- When you went to your profile picture, selected Settings, and clicked Phone Service, there were accessibility issues with the font
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- When you were in an active call, you were disconnected after 15 minutes
- When you started a conference call and a fourth person was added, everyone could hear you but you weren't able to here others
- Video would disappear when you'd put a call on hold while someone was sharing their screen
- You weren't able to use the DTMF pause function (",") of your dial pad when making a call
- You weren't able to share your screen after a call was transferred
- You couldn't stop sharing your screen when the person on the other end of the call was using a device that didn't support screen share (for example, a desk phone)
Cisco Webex Teams 41.5.0.18911 (64-bit)
- Change log not available for this version
Cisco Webex Teams 41.5.0.18815 (64-bit)
- We've updated the app version for May, this version of the app will begin rolling out to existing customers today
Cisco Webex Teams 41.5.0.18787 (64-bit)
We resolved the following issues:
- Some German translations didn't appear correctly
- When your company's retention policy was set to 24 hours, you sometimes had errors loading messages in spaces
- When you copied a message that included a link, you incorrectly received an error when you tried to paste the copied text into a space
- Sometimes you didn't have the Messaging tab in the app to send messages
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- When you started a conference call, you'd see a Recording stopped message pop up. The call recording wasn't affected
- When you'd retrieve a call that was parked on a Cisco IP Phone 8800 Series Multiplatform Phone, there would only be one-way video
- When you parked a call and clicked More next to the Retrieve button, you were presented with an empty list
We resolved the following issues when you use Calling in Webex (Unified CM):
- The keyboard shortcut Ctrl+Alt+D displays Webex diagnostics even when the Webex app isn't in the foreground
- Screenreaders weren't able to read all of the settings available from your profile picture > Settings > Calling
- Your in-call timer was incorrect if the time displayed on your PC wasn't set properly
- When you tried to check or uncheck the Only mute notifications when I'm in a meeting or on a call check box (profile picture > Settings > Notifications > Direct calls), the radio button wouldn't reflect the change
- The number you set up for Extend and Connect wasn't remembered if you used the same number for Single Number Reach
- Your phone service wouldn't connect when you disconnected from your VPN
Cisco Webex Teams 41.4.0.18629 (64-bit)
We resolved the following issue when you use Webex Calling or Calling Hosted by a Service Provider:
- When you put a call on hold and then resumed the call, the other party couldn't hear you
Cisco Webex Teams 41.4.0.18595 (64-bit)
- Change log not available for this version
Cisco Webex Teams 41.4.0.18516 (64-bit)
We resolved the following issues:
- Sometimes you didn't see the personal room link on contact cards
We resolved the following issues when you use Webex Calling or Calling Hosted by a Service Provider:
- When someone called you and hung up before you answered, you'd continue to hear it ring
- You were unable to close the Retrieve window after a call was parked
- When you used your dial pad to call a number with more than 20 digits, you got an error message that said "Sorry, calling phone numbers is not possible."
- Your in-call timer reset when you started sharing your screen
- The call would drop if you and the person you were on a call with put the call on hold
We resolved the following issues when you use Calling in Webex (Unified CM):
- Migrating your contacts from Jabber to Webex failed because of case sensitivity in email addresses
- When you clicked Snooze before a meeting started, you wouldn't receive a reminder when the meeting started
- You'd see a Bad network message in your app header even if you weren't experiencing any noticeable audio or video issues during a call
- You wouldn't see your desk phone in the Connect to a device list in your app header
- You weren't able to share your screen or application during a call