Twitxy
Saved
@interopio's profile picture
View on X

interop.io

Verified account This account is verified. Learn more

@interopio

Simplify #UX, reduce integration/migration costs & speed up time-to-market with the most intelligent #desktop #integration #platform. #FinTech #interoperability
Sofia, Bulgaria interop.io Joined August 2016
1.4K Following 2.1K Followers 1.9K Posts

Latest posts 5

interop.io Verified account @interopio
Workspace slow to open? Button click takes too long? A workflow failing somewhere across several apps?

Our io.Insights traces recording works through each one from symptom to root cause, then shows how to add your own business context to traces.

community.interop.io/t/from-symptom…
community.interop.io From Symptom to Root Cause: io.Insights traces recording and Q&A This is the recording of yesterday’s webinar From Symptom to Root Cause: Tracking Issues with io.Insights Traces. In this session, Velko Nikolov, lead for io.Insights, shows how traces help you...
interop.io Verified account @interopio
bridge.log in io.Connect Desktop isn't about io.Bridge. It logs the .NET component behind window logic.

SW-JumpListManager ShellException (0x80070578) errors there come from the OS, not the platform, and are logged on purpose for diagnostics.

community.interop.io/t/faq-os-error…
community.interop.io [FAQ] OS errors in bridge.log Question The bridge.log file contains repeated errors of this shape: [JumpListManagerDispatcher] [ERROR] SW-JumpListManager - Error in dispatcher: System.Action Microsoft.WindowsAPICodePack.Shell.S...
interop.io Verified account @interopio
Julianna Mealin, Rob Moffat, Chris Watson and Peter Smulovics will talk about FDC3 3.0 at OSFF NY this week. The FDC3 3.0 pre-releases add FDC3 Metadata, intent listener context-type filters and fdc3.close(), plus experimental FDC3 Security, and remove deprecated APIs. github.com/finos/FDC3/rel…
github.com Releases · finos/FDC3 An open standard for the financial desktop. Contribute to finos/FDC3 development by creating an account on GitHub.
interop.io Verified account @interopio
io.Connect Desktop npm run setup failing behind a corporate proxy? Two stages:

1. iocd-cli downloads via Node's fetch, which ignores OS proxy settings. Export the proxy vars + NODE_EXTRA_CA_CERTS.
2. npm install per app. Child processes inherit them.

community.interop.io/t/troubleshoot…
community.interop.io Troubleshoot npm run setup SELF_SIGNED_CERT_IN_CHAIN, npm SSL, and E400 Errors in io.Connect... Authors: Borislav Shopov, Bogomil Valev This guide explains how to troubleshoot and resolve network, proxy, and certificate errors (SELF_SIGNED_CERT_IN_CHAIN, UNABLE_TO_VERIFY_LEAF_SIGNATURE,...