Support
Support
A question, a bug, an invoice?
Write to support@novair.app, in English or French. FIX Protocol Log Analyzer is published and maintained by one person. Ideas and remarks are welcome too: send feedback (also in VS Code: FIX Log: Send feedback).
Activate Pro
Gumroad e-mails your licence key right after the purchase, and it is on your receipt. In VS Code, open the Command Palette (Ctrl+Shift+P, Cmd+Shift+P on a Mac), type “licence key” and choose FIX Log: Enter my Pro licence key, then paste the key. “Pro unlocked on this machine.” confirms it. Activation needs one connection to api.gumroad.com, through your VS Code proxy settings; after that, Pro works offline.
No key in your inbox? Check your spam folder, then find your Gumroad receipt; otherwise write to us with the e-mail address used for the purchase.
Machines
One key for one person, on up to 5 machines. A machine is counted the first time the key is activated in a VS Code installation: a new computer, VS Code reinstalled with its data erased, or a non-persistent virtual desktop whose identifier changes. Entering the key again, trying again after a network error, removing and re-entering it on the same installation, or updating the extension uses nothing. New computer or VS Code reinstalled? Write to support@novair.app with your purchase e-mail and we reset the count.
Invoice
Need an invoice? Use the “Generate” link at the bottom of your Gumroad receipt: enter your name and business address, add what your accounts need under “Additional notes”, and download the PDF. An EU business that paid VAT can enter its VAT number there: Gumroad refunds the VAT and the invoice shows no VAT. Gumroad cannot change an invoice afterwards.
Refund
Within 14 days of the purchase: write to support@novair.app or go through Gumroad, which handles payment as merchant of record. The same applies if your network blocks api.gumroad.com and Pro cannot be activated.
Report a bug
Say what you did, what you expected and what happened, with the version of the extension. If the problem comes from a log, send a few lines that reproduce it after making an anonymized copy (FIX Log: Save an anonymized copy… (Pro)) or removing account, party and client values yourself. The anonymized copy replaces the values of the tags you choose, and the same values elsewhere in the lines. Check the copy before sending it.