This issue only occurs with macOS Ventura, it does not happen with any older versions of macOS. Freezing and/or crashing occurs while typing with macOS Ventura.We're actively looking into this issue and your ticket/bug report will greatly help us in our investigation. If those steps do not help, try the steps here and contact us here.
If you don't see this option, please update to the newest version of Notability. Go to your Notability Settings > Subscription tab > Restore Plan. App is unable to recognize the correct subscription type that I purchased (Plus, Classic, etc) OR I'm not able to use in-app purchases that I bought in the past.For further assistance, please reach out to us! However, if these are not managed macs, then we would suggest option (1) and waiting for an official fix to be pushed to the Appstore (likely after the new year).If we hear about an issue from multiple users, we will post here along with any workarounds to get you up and running again as soon as possible while we work on a fix.ĭon't see your issue on here? Check out our FAQ. Note: Performance-wise WebSocket is expected to be faster than https channels.For deployment en-masse, if you can push policies to the managed macs, we would suggest this option (after verifying it works on your mac). The setting bypasses the WebSocket connection attempt and simply connect with plain https channels. If you want to stick with 10.8.0 from the Appstore, type this in the Terminal:ĭefaults write ClientSettings.DisableOnPremWebSocketGateway true.As previously mentioned, download the last stable beta Version 10.7.9 (2011) from here: aka.ms/rdmacbeta (As the app store doesn’t allow you to downgrade).Based on logs from users experiencing these error codes on 10.8.0, the issue seems to be happening during WebSocket connection where the client did not fallback properly to https channel and instead thows the error. If the gateway doesn’t support WebSocket then the client will fall back to using plain https channel. We have triaged an issue and working on a fix! When connecting to an on-prem deployment gateway, the client by default will try to connect via WebSocket first.
0 kommentar(er)
